Setup stuck at "Loading configuration settings..."

For me, the culprit was not configuring WAS to Use available authentication data when an unprotected URI is accessed.    Step 3 at the top of:  http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Ft_s_server_installation_setup_WAS.html

Hello, I am facing the exact same problem.
Any help on this topic would be greatly appreciated :)

-Nicolas

Hi
Same symptom running RTCz (on z/OS) with Tomcat (no WAS) and Derby (no DB2) & JAVA 6.0
Any hint on this issue ? Many thanks in advance
Pierre

OK, we managed to solve the issue by:

- stopping everything and clearing the WAS temp directory
- adding this entry to every teamserver.property file:"com.ibm.team.repository.server.jts.url=https\://<SERVER_NAME>\:9443/jts"
- running again jts/setup

-Nicolas

OK, we managed to solve the issue by:

- stopping everything and clearing the WAS temp directory
- adding this entry to every teamserver.property file:"com.ibm.team.repository.server.jts.url=https\://<SERVER_NAME>\:9443/jts"
- running again jts/setup

-Nicolas

Im having same problem. I did tried adding above property, But no luck.

Any suggestions on this to solve this issue?

Thanks,
Kiran

Hi buddies,
Found a typo in the JTS batch JCL script, where I had typed "export JAZZ_HOME=:etc/jazz" rather than "export JAZZ_HOME=/etc/jazz/"

Strange enough, the server did not complain about that mistake.

Fixing the typo, then restarting the server allowed to resume setup OK.

Bye

Hi.
I had the same problem. I've update WAS to 7.0.0.13 and installed the latest Java fix pack. Also, I use Nicolas instruction and restarted all servers. The problem was solved.

I just want to note, for the benefit of those who may find this topic when searching for similar problems, that it appears fairly common that when upgrading applications deployed in WAS, the undeploy process does not clean up all the old bits of the application. Then when the new applications are deployed, you end up with a mix of old and new bits, and that causes problems.

We have a tech note on this issue at

http://www-01.ibm.com/support/docview.wss?uid=swg21455119

The manual cleanup recommendation is also mentioned in the "upgrading" section of the documentation at

http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0/topic/com.ibm.jazz.install.doc/topics/t_update_post-mig_setup.html

I am installing a new instance of RTC 3.0 on WebSphere 7 and db2 on RH Linux 5 and have run into this same problem. I have tried installing it according to a variety of instructions and attempted the workarounds mentioned above. I am still stuck. Any other ideas?

i was having the same problem on windows server 2008 r2. Once i disabled the firewall it started working.

Hope this helps someone...