Unable to login using ADMIN/ADMIN during Express setup for 502
I just downloaded and attempted to install RTC 502 (JTS and RTC only) on a Windows virtual machine. The install completed and then I started the server. There were some errors on the start about files that were not able to be found (I assumed because it was the first start).
However, when I try to login with ADMIN/ADMIN for the jts/setup step, it says "invalid userid/password.
If I pull the jts.log, I see a failure in starting the database (which I assume is the issue). Any ideas how to correct? I have uninstalled and reinstalled twice:
2015-06-28 16:43:32,871 [ http-bio-9443-exec-9] INFO .repository.service.internal.rdb.ConnectionFactory - CRJAZ1365I The server is attempting to connect to the following database: "conf/jts/derby/repositoryDB"
2015-06-28 16:43:32,983 [ http-bio-9443-exec-9] ERROR com.ibm.team.repository - CRJAZ2654E The server was unable to connect to the database because the database connection settings are invalid or because database is unreachable (SQLSTATE: XJ040, SQLCODE: 40000). Verify the connection settings in your teamserver.properties file. See the Jazz Team Server log for more information.
java.sql.SQLException: Failed to start database 'C:/RTC502/JAZZTE~1/server/conf/jts/derby/repositoryDB' with class loader org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader@71b271b2, see the next exception for details.
at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)
at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
at org.apache.derby.jdbc.Driver20.connect(Unknown Source)
at org.apache.derby.jdbc.EmbeddedDriver.connect(Unknown Source)
at com.ibm.team.repository.service.db.provider.AbstractDbProvider.getConnection(AbstractDbProvider.java:205)
at com.ibm.team.repository.jdbcdriver.internal.derby.DerbyProvider.getConnection(DerbyProvider.java:108)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at com.sun.proxy.$Proxy44.getConnection(Unknown Source)
at com.ibm.team.repository.service.internal.rdb.ConnectionFactory.createConnection(ConnectionFactory.java:90)
at com.ibm.team.repository.service.internal.rdb.ConnectionFactory.createConnection(ConnectionFactory.java:1)
at com.ibm.team.repository.service.internal.rdb.JDBCConnectionPool.createEntry_aroundBody0(JDBCConnectionPool.java:82)
at com.ibm.team.repository.service.internal.rdb.JDBCConnectionPool.createEntry(JDBCConnectionPool.java:82)
at com.ibm.team.repository.service.internal.rdb.JDBCConnectionPool.createEntry(JDBCConnectionPool.java:1)
at com.ibm.team.repository.service.internal.rdb.AbstractPool.getEntry(AbstractPool.java:124)
at com.ibm.team.repository.service.internal.rdb.JDBCConnectionPool.getConnection(JDBCConnectionPool.java:139)
at com.ibm.team.repository.service.internal.schemagen.PersistentMappingService.reset(PersistentMappingService.java:106)
at com.ibm.team.repository.service.internal.schemagen.PersistentMappingService.activate(PersistentMappingService.java:91)
at com.ibm.team.repository.service.AbstractService.bindRequiredServices(AbstractService.java:195)
at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.bindRequiredServices(AbstractActivationManagerOwner.java:284)
at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.performActivation(AbstractActivationManagerOwner.java:687)
at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.doActivate(AbstractActivationManagerOwner.java:749)
at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.activate(AbstractActivationManagerOwner.java:211)
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.activate(BundleActivationManager.java:290)
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.performActivation(BundleActivationManager.java:1589)
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.access$2(BundleActivationManager.java:1574)
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager$3.acquired(BundleActivationManager.java:573)
at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer.serviceAcquired(ImportServiceRecordContainer.java:582)
at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer.access$1(ImportServiceRecordContainer.java:566)
at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer$5.serviceAcquired(ImportServiceRecordContainer.java:352)
at org.eclipse.soda.sat.core.internal.record.ImportServiceRecord.acquire(ImportServiceRecord.java:116)
at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer$1.execute(ImportServiceRecordContainer.java:64)
at org.eclipse.soda.sat.core.internal.record.container.ServiceRecordContainer.doForService(ServiceRecordContainer.java:181)
at org.eclipse.soda.sat.core.internal.record.container.ServiceRecordContainer.doForEach(ServiceRecordContainer.java:150)
at org.eclipse.soda.sat.core.internal.record.container.ServiceRecordContainer.doForEach(ServiceRecordContainer.java:365)
at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer.acquire(ImportServiceRecordContainer.java:303)
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.acquireImportedServices(BundleActivationManager.java:234)
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.acquireImportServiceRecords(BundleActivationManager.java:250)
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.startSync(BundleActivationManager.java:2054)
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.start(BundleActivationManager.java:2023)
at com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.startServiceProvider(OsgiServicesManager.java:531)
at com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.register(OsgiServicesManager.java:470)
at com.ibm.team.repository.common.transport.services.TeamServiceRegistry.registerServices(TeamServiceRegistry.java:329)
at com.ibm.team.repository.common.transport.services.TeamServiceRegistry.initialize(TeamServiceRegistry.java:290)
at com.ibm.team.repository.common.transport.services.TeamServiceRegistry.start(TeamServiceRegistry.java:371)
at com.ibm.team.repository.common.transport.services.TeamServiceRegistry.getService(TeamServiceRegistry.java:224)
at com.ibm.team.repository.service.internal.LogFeedAppender.<init>(LogFeedAppender.java:97)
at com.ibm.team.repository.service.internal.LogFeedAppender.getInstance(LogFeedAppender.java:105)
at com.ibm.team.repository.servlet.internal.TeamLogger.init(TeamLogger.java:30)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.init(AbstractTeamServerServlet.java:1470)
at com.ibm.team.repository.servlet.TeamServerServlet.init(TeamServerServlet.java:209)
at javax.servlet.GenericServlet.init(GenericServlet.java:158)
at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.initializeDelegate(ServletManager.java:195)
at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:179)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:74)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.initialize(BridgeFilter.java:303)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.jav
|
Accepted answer
|
Sorry, stupid user error :-)
Using Windows Server 2012 and the start command and my command prompt neither were configured to Run As Administrator. It dawned on me this morning ... did that, works fine now. Ralph Schoon selected this answer as the correct answer
|
One other answer
There is not much you can do except for replacing the Derby database with a good copy, as the installed one appears to be corrupted.
You can find a copy of the Derby database backup as follows. server/conf/jts/derby/repositoryDB.zipJust move the existing repositoryDB folder to somewhere else and extract the zip files, and make sure the file structure is correct (as in you don't have something like repositoryDB/repositoryDB). If the zip file does not help (or is corrupted as well, you can find the original files from the installation media as native/com.ibm.team.install.jfs.base.db.derby_1.0.0.v20141028_2019.zip (JTS) Given that it's new installation and you already get something corrupted, I am a bit worried about the Windows file system integrity though. You may want to give it a check up. |
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.