Sybase Unified Agent Windows Service Fails to Start

Problem: When starting the Sybase Unified Agent service, it takes a long time before failing, and the service manager displays a message that the service startup has timed out.

The <UnwiredPlatform_InstallDir>\SCC_3-0\log\agent.log shows the following message:

2009-11-10 13:35:50,752 [INFO ] [main] com.sybase.ua.util.process.ProcessHandler.startProcess(395) - 
Starting process SQLAnywhere-scc_repository: C:\Sybase\SCC-3_0\services\SccSADataserver\sa\bin_windows32\dbsrv11.exe 
-n scc_repository -o C:\Sybase\SCC-3_0\services\Repository\scc_repository.slg -m -qi -qw -sb 0 -gn 100 -gm 500 -zl 
-zp -x TCPIP{port=3638} C:\Sybase\SCC-3_0\services\Repository\scc_repository.db 
2009-11-10 13:36:57,037 [ERROR] [main] com.sybase.ua.services.asa.ASAEngine.startEngine(135) - Failed to connect to 
dataserver engine. ASAEngine: Unable to open a new connection to the engine.

Explanation: This problem usually occurs when the Sybase Control Center repository database log file is out of sync with the repository database. A related symptom is the message SQL Login Failure in the Sybase Control Center repository log file.

Solution: Delete the <UnwiredPlatform_InstallDir>\SCC-3_0\services\Repository\scc_repository.log file and restart the service.

Related reference
Launching SCC Results in Rounded Rectangle Box or Empty Console Screen
Sybase Control Center Fails to Start
Second Sybase Control Center Fails to Start
Login Invalid in Sybase Control Center
Cannot Access Unwired Platform Administration Nodes
Previous Administrator Credentials Used
Browser Refresh (F5) Causes Logout
Security Error Triggered When Connecting to SCC from Remote Browser
Administrator Login Passes When Provider Is Not Available
Host Name of Registered Resource Changed But Is Not Updated