jts setup error
alex ioan (33●7●10)
| asked Oct 02 '13, 3:12 a.m.
retagged Oct 07 '13, 9:50 a.m. by Ralph Earle (257●3●9)
Hello,
I'm installing CLM 4.0, on AIX, deployment in WAS, Oracle 11 db. When pointing my browser to jts/setup in order to run a custom setup wizard, in the Configure the public URI page i get the followin error: The configuration test resulted in errors. Resolve the errors to continue. For more details, open the help system and search for CRJAZ1579E.ID CRJAZ1579E hide details The method getPrerequisiteServices() was called on the AbstractActivationManagerOwner for com.ibm.team.repository.service.internal.BaseServerDescriptionService when the service not activated. The method should only be called when the service is activated. If you see this error please report the problem to the Jazz Application Frameworks team, because there is a bug in the Jazz server. Can anyone help me with this? Thanks L.E.: a refresh solved the problem |
3 answers
Hi Alex, This looks like JTS starts up with some problem. Please check in the jts.log and look for errors after the server startup. The error looks like the one in this jazz.net question: |
The three things I would validate are 1) WebSphere Security settings have been configured correctly: 2) CLM application roles have been mapped to a group/user in the application security settings and 3) ensure the jazz-home has been set correctly on the server instances where the applications are running
|
Hi
I had same issue and it resulted from the wrong databases configured in teamserver.properites
Once corrected database entries and restarted the server , it worked for me
Hope it will help you too
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
You can always check the server logs to see if there is more useful information there. See http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m4/index.jsp?re=1&topic=/com.ibm.rational.clm.doc/topics/c_logfiles_loc.html&scope=null for help locating the logs.