ASE 16.1 didn't start as a windows service

[robert_kratschmann]

Hi!
I did an manual update from 16.0 SP04 PL06 to 16.1 SP00 PL00 on Windows 11 with German local settings. (An automatic update was not offered.) ASE run fine if I start it with %SYBASE&\%SYBASE_ASE%\RUN_<Servername>.bat script!

But starting it as a Windows service leads into error 1067 (The process ended unexpectedly). There is only one entry in the errorlog:
00:0000:00000:00000:2025/03/17 09:01:01.70 kernel SySAM: Using licenses from: C:\SAP\\SYSAM-2_0\licenses\HP450RK_20250314_083327.lic;C:\SAP\\SYSAM-2_0\licenses\PD_EA.lic;C:\SAP\\SYSAM-2_0\licenses\SySAMLicenseServer.lic
The SySAM Service seems to work fine because the SySAM Server will be used to start PowerDesigner - and it is  running OK.

I checked the path entries in the registry all are changed from 16_0 into 16_1. Backupserver is running as a service. And also the XP-Server has no problems if it will be called by xp_cmdshell.

Test: If I remove the -C in the registry definition ASE starts fine
C:\SAP\ASE-16_1\bin\sqlsrvr.exe -sHP450RK -C into C:\SAP\ASE-16_1\bin\sqlsrvr.exe -sHP450RK
Normal starting entries in the errorlog exists but finally the process ended with error 1053 (correct if -C is missing).

Many thanks

Robert

[ChrisBaker]

Use a different account than LocalSystem to start the ASE service.

[robert_kratschmann]

I tried it with both existing and new customers, but it didn’t help. Is there a way to drop and recreate the ASE Windows service only without dropping and recreating the ASE server itself?