Hi Stephen,
Hmmm - I would have expected that diagnostic to be more useful. Let's keep going...
ps : when i try to start the service from a cmd box, i get the same problem in procmon :
- Can you start just a regular "dbsrv9 -n demo demo.db -n demo" command on the desktop? (Don't use the service command line at all).
- Can you start any other third-party (non-system) services, not related to SQL Anywhere?
- Are you using "Interact with Desktop" (dbsvc -i) at all with these SQL Anywhere services? I would expect the answer is "no" but if you are, you should disable the feature.
---
One reason you might not be able to start a service is because you have too many processes using (desktop) heap memory in session 0 (See: https://support.microsoft.com/en-ca/kb/947246 ). This is not related to how much RAM is available on the system.
To determine this, this is best diagnosed with dheapmon from Microsoft, although I would say from a quick local test with the utility, it is not the easiest to install (see here, and here). I would try the approach from the first thread to use the Windows 2003 compatibility mode on the dheapmon utility/DLL and see if you can install it that way.
Once you get the utility going, you can check for the amount of heap space is left in the Service (s0) heaps:
================================
>dheapmon
Desktop Heap Information Monitor Tool (Version 8.1.2925.0)
Copyright (c) Microsoft Corporation. All rights reserved.
-------------------------------------------------------------
Session ID: 1 Total Desktop: ( 65088 KB - 11 desktops)
WinStation\Desktop Heap Size(KB) Used Rate(%)
-------------------------------------------------------------
WinSta0\Winlogon (s1) 192 7.4
WinSta0\Disconnect (s1) 96 6.5
WinSta0\Default (s1) 20480 5.4
WinSta0\DummyDesktopForInstantResume (s1) 20480 0.0
msswindowstation\mssrestricteddesk (s0) 768 0.8
Service-0x0-3e5$\Default (s0) 768 2.2
Service-0x0-3e4$\Default (s0) 768 1.9
Service-0x0-3e7$\Default (s0) 768 12.8
WinSta0\Winlogon (s0) 192 10.5
WinSta0\Disconnect (s0) 96 6.5
WinSta0\Default (s0) 20480 0.1
-------------------------------------------------------------
================================
If you are running out of heap memory in the service area, you can adjust this a number of ways - the overall heap for the system is controlled by:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\SessionViewSize
which is 48M by default:
You can also configure the size of the individual desktop session via the instructions on the Microsoft KB: https://support.microsoft.com/en-ca/kb/947246 by editing HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems\Windows
Mine is already at the prescribed maximum (20480KB) for Windows Vista and up, but if you are running out of heap in just your session 0, maybe this value needs to be bumped up:
Do you remember if you had to do something similar for your previous Windows 2003 server installation also?
Regards,
Jeff Albion
SAP Active Global Support