syslog_manager.exe 9.4.0.1 will not open correctly on windows 8.1. The process starts and can be seen in task manager, but closes a few second later. No GUI is seen at all not even the splash screen or the notification area icon.
there are no logs inside:
C:\Program Files (x86)\Syslogd\Dated logs
C:\Program Files (x86)\Syslogd\Logs
i tried calling (Service – Debug start-up: www.kiwisyslog.com/help/syslogd7/index.html?adv_reg_servicedebugstart_up.htm):
syslog_manager.exe DEBUGSTART
syslog_manager.exe /DEBUGSTART
syslog_manager.exe -DEBUGSTART
syslog_manager.exe --DEBUGSTART
but still no log or debug log files are created in the C:\Program Files (x86)\Syslogd directory or any of its sub directories.
i checked the window event log and found the same four error reoccurring every time the syslog_manager.exe is started up
==============================
Error 1
==============================
Fault bucket -339880763, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Syslogd_Manager.exe
P2: 9.4.0.1
P3: 5256d7ac
P4: StackHash_4527
P5: 0.0.0.0
P6: 00000000
P7: c000041d
P8: PCH_1C_FROM_actskn43+0x00014197
P9:
P10:
Attached files:
C:\Users\user\AppData\Local\Temp\WER7A1F.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Syslogd_Manager._1c26be14be8bc7e884ee84c763454f0becaea_d6be21d2_0a3f7cfe
Analysis symbol:
Rechecking for solution: 0
Report ID: 89cea6aa-4b23-11e3-befa-001b63a57b6a
Report Status: 0
Hashed bucket: ee82e4cf87c028d8fde4d29d457939f8
==============================
Error 2
==============================
Faulting application name: Syslogd_Manager.exe, version: 9.4.0.1, time stamp: 0x5256d7ac
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000041d
Fault offset: 0x040705b8
Faulting process ID: 0xbe0
Faulting application start time: 0x01cedf304b48bb7b
Faulting application path: C:\Program Files (x86)\Syslogd\Syslogd_Manager.exe
Faulting module path: unknown
Report ID: 89cea6aa-4b23-11e3-befa-001b63a57b6a
Faulting package full name:
Faulting package-relative application ID:
==============================
Error 3
==============================
Fault bucket 50, type 5
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: Syslogd_Manager.exe
P2: 9.4.0.1
P3: 5256d7ac
P4: StackHash_f2c9
P5: 0.0.0.0
P6: 00000000
P7: PCH_3D_FROM_ntdll+0x0003C1AC
P8: c0000005
P9: 00000008
P10:
Attached files:
C:\Users\user\AppData\Local\Temp\WER7676.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Syslogd_Manager._4bac366436d77f4150a9f635e3ff4264d568c57d_d6be21d2_070f7973
Analysis symbol:
Rechecking for solution: 0
Report ID: 893e635c-4b23-11e3-befa-001b63a57b6a
Report Status: 0
Hashed bucket: 18c71da6583848b95798fbf0fc6b19c1
==============================
Error 4
==============================
Faulting application name: Syslogd_Manager.exe, version: 9.4.0.1, time stamp: 0x5256d7ac
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x040705b8
Faulting process ID: 0xbe0
Faulting application start time: 0x01cedf304b48bb7b
Faulting application path: C:\Program Files (x86)\Syslogd\Syslogd_Manager.exe
Faulting module path: unknown
Report ID: 893e635c-4b23-11e3-befa-001b63a57b6a
Faulting package full name:
Faulting package-relative application ID: