WCC login fails "E150005: Login timed out"

Document ID : KB000028842
Last Modified Date : 14/02/2018
Show Technical Document Details

Environment: WCC 11.3.5 

We can find the version from the output of %CA_WCC_INSTALL_LOCATION%/uejmver.bat


Product Name: CA Workload Control Center 

Copyright: Copyright (c) 2012 CA Inc. All rights reserved. 

Level: 11.3.5 

Service Pack: 0 

Patch Number: 0 

Build Number: 20121218-b506 

Volume Label: CA-WCC11.3.5-Win 

Platform: windows 



When we login into WCC we get this error "E150005 Login timed out. The server is not responding. Please try again later."


Log snippets

There are three logs available for a basic troubleshooting with WCC in %CA_WCC_INSTALL_LOCATION%/log folder





In our case we found out that WCC was unable to connect to database from the CA-wcc.log.


INFO   | jvm 1    | 2014/11/28 09:22:06 | @tomcat-resource <autosys-external-refs-updater> [] ERROR #datasource  # Cannot get database connection

INFO   | jvm 1    | 2014/11/28 09:22:06 | java.sql.SQLNonTransientConnectionException: java.net.ConnectException :

Error connecting to server localhost on port 1527 with message Connection refused: connect.


And from the CA-wcc-services.log shows we understand  there was some problem with the derby transaction log


NFO   | jvm 1    | 2014/11/28 09:40:54 | org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ040, SQLERRMC: Failed to start database 'WCC_MAIN' with class loader sun.misc.Launcher$AppClassLoader@4830c221, see the next exception for

details.::SQLSTATE: XSLAORecovery failed unexpected problem log record is Not first but transaction is not in transaction table : 188744360.)


The transaction log could have got corrupted dues many reasons. There could have been a power outage or improper shutdown of Db service or even a Disk full condition.


The solution is to recreate the transaction log as follwos


Rename the transaction log folder

<WCC_INSTALL_DIR>/derby/DB_FILES/WCC_MAIN//log and create a new log folder

in the same location.


Once the WCC services are restarted it recreates the transaction log. This will solve the WCC login issue.