HTTP 404 error after upgrading from v2.0.0.1 to v2.0.0.2
We are setting up a test server so that we can use it for testing RTC and for RTC training (and therefore will not interfere with our production RTC server). So, we built a Windows server with RTC v2.0. Then we upgraded this RTC server from v2.0 to v2.0.0.1. No errors were seen during the upgrade process. After restarting RTC, we get this error when launching the web site:
"HTTP Status 404 - Servlet equinoxbridgeservlet is not available" The above is seen with trying these URLs (server and company name have been changed to something generic): https://<server>.<company>.net:9443/jazz https://<server>.<company>.net:9443/jazz/web https://<server>.<company>.net:9443/jazz/web/console I saw a similar post for this issue, but that was for Linux. Any help with this is greatly appreciated, -Walter |
One answer
We have had the same problem.
Problem was in "web.xml". We have taken new one and made configuration changes again. David Csikkel We are setting up a test server so that we can use it for testing RTC and for RTC training (and therefore will not interfere with our production RTC server). So, we built a Windows server with RTC v2.0. Then we upgraded this RTC server from v2.0 to v2.0.0.1. No errors were seen during the upgrade process. After restarting RTC, we get this error when launching the web site: |
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.