Windchill not accessible from UI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Windchill not accessible from UI
Hi,
I performed a rehost on dev server from production. This is the second time in last 15 days, I have rehosted server. First time, all went good , server was up and running.
But the second time, I can see message in the MS-log. (MethodServer ready (in xxxx secs).) and then trying to access it from UI, it is authenticating the user and cannot access, it keeps rotating.
Can someone please help me where to check ?
Solved! Go to Solution.
- Labels:
-
Other
-
Upgrade_Migration
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi,
I fixed it, and now the server is up and running.
In WindchillDS, i could see after rehost, entries were correct, but in the access log, i saw they were still pointing to the source system,
thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi @K_Patil
The best and the fastest help is to do the rehost again. You would spend more time with searching for the error then repeat the hole rehost process.
In your case you should share what is rotating again and again? What version of Windchill do you use.
You should check if your LDAP is correctly set in the Apache and also if the Apache configuration is correctly updated.
PetrH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi,
I fixed it, and now the server is up and running.
In WindchillDS, i could see after rehost, entries were correct, but in the access log, i saw they were still pointing to the source system,
thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
I would add as part of your steps on your non-production systems to prevent cross talk. This could be potentially disastrous having servers interact with production inadvertently. You can modify your hosts file to prevent dev and test from ever communicating with any host that running production servers, LDAPs or databases. Ensure that you alter passwords, ports and usernames if possible to further prevent issues.