Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

problem with rm setup

Hi, i was trying to run the setup of jts when i have the following problem with rm:
 CRRRS3008E There was an unexpected error, see the log file for possible causes. The error response labels is '500 '

I have ccm and qm configured fine, but i can't make rm work.

Then, when i open the instruments panel, rm has the message: "Failed to reach the application".

Another thing, i have license to RTC 4.0 , can i use them to 4.0.2? can i use them more than once?


0 votes

Comments

Can you post the stack trace here?

Information about which app server would also be useful.

1 vote

 Can you post the stack trace here? 

Are you asking me about the rm log file?

which app server?
Requeriments Manager has the problem. I have jazz team server, quality manager and change and configuration manager configured.

I'm sory i'm not so experience with this stuff... Ask me again if i don't answer okay.

Are you using Tomcat or WAS as app server? All installed on the same machine?

 I'm using tomcat on the same machine that has jts applications. The db2 database is in another machine.

rm.log will help, but jts.log might have the error recorded since the error is seen during setup

Look at the rm.log and jts.log files around the time you tried the finalize step for the RM application. That should give a clue of what goes on. Post any error messages and stack traces here, and we can work with that.

I will explain everything. Maybe that way i make myself clear. I have to migrate from 3.0.1 to 4.0.2, but in order to make some test first, i copy those machines in virtual machines to practice there first so i can't crash anything. The issue is, that i have a lot of environment problems. I change the ip address (virtual machines) and the DB an jts are pointing correctly. When i run the setups, i can finalize any of them (qm says something that can't replace a key and ccm something with a report). I add friends to jts, qm and ccm manually to configure them and they seem to work!!!, but i have the problem with rm.


Now, i try what Ralph said about tomcat, but it is still with the same problem... I accept any question and suggests ^^.

If you do upgrade tests, you don't have to run setup on the test system. But you have to isolate the test system from the other by making sure the host names used point to the right machines. Best is to totally isolate the test system. Make sure you can reach the servers in the test system and run the applications. Once everything works, you can test the upgrade.

Dependent if you use VMWare or backup/restore you might want to check what you have to backup/restore to the test system here: BackupCLM < Deployment < TWiki

I think i have the correct configuration, i have followed up this guide http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m1/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Fc_upgrade_staging_env.html

I configure the hosts files and if i ping to the public URI i have my test virtual machine in response. I change the teamserver.properties so i can reach my DB. The state in the summary status in the applications is okay. I have that prepared. The backup in database is ready.
I just need rm to proceed or that's what i believe. What would you need to help me solve this? any configuration i can show let me know.

showing 5 of 10 show 5 more comments


2 answers

Permanent link
If you use Tomact, look into <InstallDir>/server/logs to locate the logs. There is probably more information available.

can you reach https://<server>:<port>/rm/rootservices ?

Maybe RM did not get deployed correctly the first time. Try the following:
  1.  Shutdown Tomcat.
  2. Goto <InstallDir>/server/tomcat/webapps
  3. Delete all the sub folders and keep the .war files untouched
  4. Restart Tomcat and monitor the deployment process.
  5. In the browser try to reach https://<server>:<port>/rm/rootservices
  6. If successful rerun setup.


0 votes

Comments

 I forgot to mention that i can reach https://<server>:<port>/rm/rootservices .


Permanent link
 I made it. I could run my setups and configure them. I isolate my virtual machines to another network. For now that is perfect, but just when i was going to migrate, i have seen this error:

In https://[name]:port/ccm/web/projects
An error has ocurred while recovering the instruments panel
Unable to load /ccm/proxy?uri?https%3A%2F%2F172.16.81.38%3A8292%2Fjts%2Fdashboards%2F6%3FcontentType%3Dapplication%252Frdf%2525xml status:403

Note: my public URI is configured like ej:[name] is the ip address 172.16.81.38

My properties are with the [name]. 

0 votes

Your answer

Register or log in to post 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Jun 19 '13, 9:45 a.m.

Question was seen: 3,860 times

Last updated: Jun 26 '13, 10:42 a.m.

Confirmation Cancel Confirm