Skip to Content
Former Member
Feb 02, 2006 at 04:12 PM

The saposcol service failed to start.


Hi everyone:

- We have detected that in our production database system there are two error messages:

1. The saposcol service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion.

For more information, see Help and Support Center at

EVENT ID: 7000


2. Timeout (30000 milliseconds) waiting for the saposcol service to connect.

For more information, see Help and Support Center at

EVENT ID: 7009

- Both of them have as source the Service Control Manager.

The database system is a Windows cluster where the portal SCS are running with Oracle The OS is a Microsoft Windows Server 2003 Enterprise Edition.

The path to the executable saposcol.exe is:

C:\WINNT\SapCluster\saposcol service

We have tried to uninstall and install the service as in note 82751 (through the windows services window), and the service saposcol is started, but these two errors steel appear.

We have the same structure at Test system and saposcol works properly. We thought if it could be possible that the overloading of the production system was causing a delay in the start of the saposcol service, and then the timeout is reached. Is it possible to increase this timeout, and in this case, will this solve the problem? (if so, how do we do increase it, and in which manner will affect our system?)

Thanks and regards,

Jose Sorli Esteve