Unknown Error during 2.0 setup at: Setup User Registry
I am upgrading a 1.0 server on Linux to 2.0. At the step where I setup the registry, it says:
An unknown error occurred. View the Admin Server Status Summary for more information.
When I check the server status, it has the exception information below and the following for Server License: Error fetching server status information.
I don't know if this is a problem but I had initially gone down the Express path but backed out after doing the first two steps and went down the Custom path.
Any help is appreciated. TIA
Error fetching server status information.Hide Details
java.lang.Exception
com.ibm.team.repository.common.transport.ServerHttpUtil.serializeError(ServerHttpUtil.java:1093)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleException(AbstractTeamServerServlet.java:1159)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:1699)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:1623)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1536)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:121)
com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:54)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
java.lang.Thread.run(Thread.java:811) :(
An unknown error occurred. View the Admin Server Status Summary for more information.
When I check the server status, it has the exception information below and the following for Server License: Error fetching server status information.
I don't know if this is a problem but I had initially gone down the Express path but backed out after doing the first two steps and went down the Custom path.
Any help is appreciated. TIA
Error fetching server status information.Hide Details
java.lang.Exception
com.ibm.team.repository.common.transport.ServerHttpUtil.serializeError(ServerHttpUtil.java:1093)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleException(AbstractTeamServerServlet.java:1159)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:1699)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:1623)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1536)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:121)
com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:54)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
java.lang.Thread.run(Thread.java:811) :(
8 answers
Hi,
Sometimes we will see this "Error fetching server status information." message on the Jazz team server Admin UI because it's usually one of the first things to fail if there is a configuration problem with the server. Could you provide a few more details about the migration?
1) Are you using WAS or tomcat?
2) What database are you running?
3) On the 2nd step of the Setup wizard custom path (Configure Database), are you able to Test Connection successfully?
Thanks!
Sometimes we will see this "Error fetching server status information." message on the Jazz team server Admin UI because it's usually one of the first things to fail if there is a configuration problem with the server. Could you provide a few more details about the migration?
1) Are you using WAS or tomcat?
2) What database are you running?
3) On the 2nd step of the Setup wizard custom path (Configure Database), are you able to Test Connection successfully?
Thanks!
Hi,
1) Are you using WAS or tomcat?
2) What database are you running?
3) On the 2nd step of the Setup wizard custom path (Configure Database), are you able to Test Connection successfully?
1) Using Tomcat on SUSE Linux box
2) DB2 with JDBC connection
3) Yes. The Configure Database Test Connection is successful
TIA
Just to confirm, you are migrating to 2.0 and not 2.0.0.1, correct?
Have you tried following the steps described here: http://www-01.ibm.com/support/docview.wss?rs=3499&uid=swg27017035 ?
It sounds to me like the server (or maybe the database) is in a bad state. I'm not sure exactly what might have caused this.. but it might help to know how far along with the migration process you are and if you ran into any other issues along the way.
Have you tried following the steps described here: http://www-01.ibm.com/support/docview.wss?rs=3499&uid=swg27017035 ?
It sounds to me like the server (or maybe the database) is in a bad state. I'm not sure exactly what might have caused this.. but it might help to know how far along with the migration process you are and if you ran into any other issues along the way.
I am migrating to 2.0.0.1 and so was not doing the hotfix. I have not been able to get to the Migrate step.
My install has not gone smoothly so I probably did something that caused this. At first, I went down the Express Install path not realizing that was not for DB2 based servers. So I backed out of that path after doing the first couple steps. The other thing that happened was that the passwords I had for db2admin and jrsuser had to be reset. This also resulted in a backout. And at some point in all that, the VM running the server had to be restarted.
These are all things that I suppose may have created the problem. What I need is a way to clean up anything from the prior attempts or a way to get past this error.
TIA
My install has not gone smoothly so I probably did something that caused this. At first, I went down the Express Install path not realizing that was not for DB2 based servers. So I backed out of that path after doing the first couple steps. The other thing that happened was that the passwords I had for db2admin and jrsuser had to be reset. This also resulted in a backout. And at some point in all that, the VM running the server had to be restarted.
These are all things that I suppose may have created the problem. What I need is a way to clean up anything from the prior attempts or a way to get past this error.
TIA