search

crazytroy / eventlog-to-syslog

Automatically exported from code.google.com/p/eventlog-to-syslog
0 stars 0 forks source link

Cannot start service dispatcher #80

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. evtsys.exe -i -h ip.of.elsa
2. net start evtsys
3. evtsys.exe -n

What is the expected output? What do you see instead?
I want to be able to change the level so all of the event logs are sent to my 
syslog server. 
If I try to only use the config file or if I try to change the level, I get the 
error message

 "Cannot start service dispatcher: The service process could not connect to the  service controller.

Command did not complete due to failure"

What version of the product are you using? On what operating system?
4.4. On Windows 7. Setting up a test environment.

Please provide any additional information below.

StartServiceCtrlDispatcher(ServiceDispatchTable) == FALSE in service.c

causes it to print that it cannot start service dispatcher, I do not know what 
causes this error. There have been instances where I have reinstalled 
eventlog-to-syslog and manually deleted the existing registry file folders.

Original issue reported on code.google.com by andrew.w...@gmail.com on 17 Apr 2013 at 11:52

GoogleCodeExporter commented 8 years ago 
Propably same situation with me on 2008 R2 64 Bit server.

Even if I use standart installation, it says this:
System error 2 has occurred.

The system cannot find the file specified.

Config file of course exist and is at same folder as the exe file...

Any ideas what to do?

Thank you!

Original comment by ji...@ehm.cz on 9 Sep 2013 at 4:39

GoogleCodeExporter commented 8 years ago 
Solved....

Windows UAC (even if disabled) again.. :-)

I had to manualy run cmd.exe as administrator, then manualy in cmd copy files 
to system32 at windows folder, and then install it.

After that I was able to sucesfully run a service!

Original comment by ji...@ehm.cz on 10 Sep 2013 at 11:59