on 2024 Feb 27 3:32 AM
We have several database servers in AWS cloud in ap-southeast-2 region. On each server we have several SAP ASA 17 databases (17.0.10.5963), running as Windows services.
Each service is configured as delayed auto start. On 24.02 24 and 26.02.24 we had the following problem. After server reboot several (1-5) database services didn’t started on all servers.
There are no messages in database logs saying that database was started. No errors (-oe file). In Windows system log we have messages like this:
“A timeout was reached (30000 milliseconds) while waiting for the SQLANYs...DB service to connect.”
“The SQL Anywhere - ...DB service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.”
No messages about dbsrv17.exe crash.
DB service parameters are like this:
-n AU1409_CMS -x tcpip(ServerPort=40415) D:\\XXX.db -o D:\\YYY.txt -on 2M -oe D:\\ZZZ.txt -gnl 20 -sb 0 -xd
Is it possible to avoid this error?
ps There is a SAP note, but for ASE:
2599552 - Error 1053:The service did not respond to the start or control request in a timely fashion - SAP ASE
Is it worth trying to use the solution (set ServicesPipeTimeout = «180000») from it?
Request clarification before answering.
ServicesPipeTimeout is a general setting for the Windows service control manager, so you can provide more time for all services to start.
What you observe might be just a slow VM environment. It might even be that the SC manager has not even called the main routine for dbsrv17 to start before the timeout killed it already again (therefore you don't see any logs from dbsrv17).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
52 | |
10 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.