I having a problem with my syslog server now after a quite while running it successfully ! I just finished adding both "Rules" and "Actions" and I was confirming my config I noticed that the email addesses I entered for the action entry I added only included one of the five emails I added. I opened the action and removed the only address that was visible and added one of the prevously added email addresses and when I clicked ok and apply the snap-in stopped responding and the service crached and it wont start up again.
When I use the snap-in and select start it displayed "not responing" for a while and finally returns the error "The service on computer "COMP" could not be started. Win32 Error: 1053 - The service did not respond to the start or control request in a timely fashion" which is a general service error. When I go to the services and try to start the service there I get a similar error.
When trying properties in the snap-in on the server it returns the error "Access to the configuration data is currently not possible because it is locked by another instance"
Viewing the application event log gives the following reson : An error occurred in loading the service configuration from the registry.
I have also checked "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SL4NT\Parameters" both actions and rules and I dont seem to find anything error worthy there.
Also I downloaded "Process Monitor" http://technet.microsoft...us/sysinternals/bb896645 and tried to monitor registry reads and I noticed quiet amount of NAME NOT FOUND errors for registry keys that I have verifyied and do not exist. I also saw few BUFFER OVERFLOW messages that where followed by a SUCCESS fow example when reading
I really need to get this server up as quickly as possible so help would be apreciated. If there is more info that I need to provide then please ask. Any ideas what I can try ?
please check if there's a registry value 'Lock' below the registry key 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SL4NT\Parameters'. If this registry value exists, delete it and then try again.
This worked like a charm !!!! Thank you for a quick reply and thanks for a good software !
This solution helped me as well.
Any details on what causes the Lock key to be generated?
Hi eiki,please check if there's a registry value 'Lock' below the registry key 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SL4NT\Parameters'. If this registry value exists, delete it and then try again.-Franz
The 'Lock' key is created before the configuration is read/written from/to the registry and deleted afterwards to prevent inconsistencies when multiple SL4NT Manager instances target the same SL4NT service instance.