It's all about the answers!

Ask a question

Setup error with RRDI 5.0


Harry Koehnemann (30125238) | asked Jul 11 '14, 7:36 p.m.
I am trying to install RRDI 5.0 and getting an error on setup.  I am following the instructions below.

https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.rational.rrdi.admin.doc/topics/t_postinstall_start_setup_app.html&scope=null

On the setup page (https://<server>:10443/rrdi/setup) I enter the url "https://<server>:10443/jts", username/password, click Initialize and the following dialog appears:  Fail to register, please check url and user account.

It appears to have worked one time as the repotools-jts_setup.log file says success and my user/pass was adde dto tomcat-users.xml.  Those file's timestamps do not change when I rerun this setup though.

Ideas??

Accepted answer


permanent link
Francesco Chiossi (5.7k11119) | answered Jul 15 '14, 9:18 a.m.
edited Jul 15 '14, 9:19 a.m.
Hello Harry,

could it be a Windows permissions issue?
Is the Windows user running the setup application able to read and write to the RRDI installation folder?

If you installed under the default Program Files location, it might be worth giving a try to a new installation outside that folder (for example C:\IBM\RRDI).

Best Regards,

Francesco Chiossi
Harry Koehnemann selected this answer as the correct answer

Comments
Harry Koehnemann commented Jul 15 '14, 6:38 p.m.

That might have fixed the problem.  I started a cmd shell as Administrator and used it to run server.starup.bat.  I also used IE (instead of Chrome) as I recalled Insight and Chrome didn't get along too well.  So I am not sure which solved this issue.


Many thanks for the help 


Francesco Chiossi commented Jul 16 '14, 4:22 a.m.

Glad to hear it's fixed.
In version 5 Chrome should be supported, so I'm more inclined to think that running as Administrator did the trick.

2 other answers



permanent link
Francesco Chiossi (5.7k11119) | answered Jul 14 '14, 3:33 a.m.
Hello Harry,

if the setup application seems to be left in an inconsistent state after a previous initialization attempt, you can try the following:
  1. Stop the RRDI setup application, if it's running
  2. Backup the directory: [RRDI Install]\setup\tool\JazzTeamServer
  3. Delete the directory: [RRDI Install]\setup\tool\JazzTeamServer\server\conf\rrdi\repository
  4. Start the RRDI Setup Wizard again
  5. Re-enter values for all the steps and fields in the RRDI setup wizard.

This should allow you to redo the configuration from scratch.

Best Regards,

Francesco Chiossi


Comments
Harry Koehnemann commented Jul 14 '14, 12:07 p.m. | edited Jul 14 '14, 12:07 p.m.

 Thanks for the quick reply Francesco. I did the above, restarted the server (RRDI\setup\tool\JazzTeamServer\server\server.startup.bat), and re-entered the values.  I get the same problem.  The repository directory is not recreated.  And it was empty before - not sure if that is an issue.  The tomcat output is below.


From the docs, it sounds like I am creating the account.  I assume I don't need to already have the account created prior to the setup page.  And nothing interesting in any of the log files - only an exception about dashboard sockets not connecting.

INFO: Server startup in 5848 ms
08:24:01,667 [http-bio-10443-exec-3]  INFO om.ibm.rational.rrdi.setup.internal.AppInitializer  - C:\IBM\RRDI\setup\tool\JAZZTE~1\server\conf\rrdi
08:24:01,667 [http-bio-10443-exec-3]  INFO om.ibm.rational.rrdi.setup.internal.AppInitializer  - C:\IBM\RRDI\setup\tool\JAZZTE~1\server\conf\rrdi
08:24:01,934 [http-bio-10443-exec-2]  INFO bm.rational.rrdi.setup.service.SelfRegisterService  - CRRRA0179I: Begin setup of Jazz Team Server
08:24:01,934 [http-bio-10443-exec-2]  INFO bm.rational.rrdi.setup.service.SelfRegisterService  - CRRRA0179I: Begin setup of Jazz Team Server
08:24:10,116 [http-bio-10443-exec-2]  INFO bm.rational.rrdi.setup.service.SelfRegisterService  - CRRRA0171I: status:302
08:24:10,116 [http-bio-10443-exec-2]  INFO bm.rational.rrdi.setup.service.SelfRegisterService  - CRRRA0171I: status:302
08:24:10,142 [http-bio-10443-exec-2]  INFO bm.rational.rrdi.setup.service.SelfRegisterService  - CRRRA0171I: status:200
08:24:10,142 [http-bio-10443-exec-2]  INFO bm.rational.rrdi.setup.service.SelfRegisterService  - CRRRA0171I: status:200
08:24:10,144 [http-bio-10443-exec-2]  INFO bm.rational.rrdi.setup.service.SelfRegisterService  - CRRRA0174I: root service is:https://myjazz-server:10443/rrdi/scr
08:24:10,144 [http-bio-10443-exec-2]  INFO bm.rational.rrdi.setup.service.SelfRegisterService  - CRRRA0174I: root service is:https://myjazz-server:10443/rrdi/scr
08:24:10,146 [http-bio-10443-exec-2]  INFO bm.rational.rrdi.setup.service.SelfRegisterService  - RRDI Setup (https://myjazz-server:10443/rrdi)CRRRA0175I:  is registered with the Ja
zz Team Server.
08:24:10,146 [http-bio-10443-exec-2]  INFO bm.rational.rrdi.setup.service.SelfRegisterService  - RRDI Setup (https://myjazz-server:10443/rrdi)CRRRA0175I:  is registered with the Ja
zz Team Server.
08:24:10,880 [http-bio-10443-exec-2]  INFO bm.rational.rrdi.setup.service.SelfRegisterService  - CRRRA0171I: status:500
08:24:10,880 [http-bio-10443-exec-2]  INFO bm.rational.rrdi.setup.service.SelfRegisterService  - CRRRA0171I: status:500


permanent link
Saheed Oseni (61) | answered Feb 18 '15, 11:00 a.m.
I experienced the same issue as I upgraded RRDI from version 2.0 to 5.0.2. I got the same logs @Harry Koehnemann
posted above, In addition I saw the below in the application log [.../setup/tool/JazzTeamServer/server/logs/jts.log ]

Caused by: java.lang.RuntimeException: CRJAZ0911E Error initializing content service. The content temporary directory "/tmp/contentservice" is read-only.
        at com.ibm.team.repository.service.internal.ContentService.canWriteInDirectory(ContentService.java:646)
        at com.ibm.team.repository.service.internal.ContentService.initialize(ContentService.java:287)
        at com.ibm.team.repository.service.internal.ContentService.activate(ContentService.java:242)
        at com.ibm.team.repository.service.AbstractService.bindRequiredServices(AbstractService.java:191)

In my case making "/tmp/contentservice" writable resolved the issue.

Thank you
Saheed A. Oseni

Your answer


Register or 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.