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. No messages about dbsrv17.exe crash. DB service parameters are like this: Is it possible to avoid this error? ps There is a SAP note, but for ASE: asked 27 Feb, 03:32 Ilia63 |
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). answered 28 Feb, 08:55 Martin |