Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Kiwi Syslog Server > Kiwi Sys - Knowledgebase Articles > Kiwi Syslog Server service startup failure in versions 9.3.3 and 9.3.4

Kiwi Syslog Server service startup failure in versions 9.3.3 and 9.3.4

Overview

When attempting to start the Kiwi Syslog Server (KSS) service, one of the following error messages displays:

  • Error 1053: The service did not respond to the start or control request in a timely fashion.
  • Error 7000: The Kiwi Syslog Server failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
  • Error 7009: Timeout (30000 milliseconds) waiting for the Kiwi Syslog Server service to connect.
  • Component 'ipdaems81.ocx' or one of its dependencies not correctly registered: a file is missing or invalid

Environment

  • Kiwi Syslog 9.3.3
  • Kiwi Syslog 9.3.4
  • Kiwi Syslog 9.4.1

Cause 

Kiwi Syslog Server uses Microsoft .Net Framework 2.0-managed assembly with an Authenticode signature that is taking longer than usual to load. 

Resolution

  1. Go to C:\Windows\Microsft.NET\Framework\v.2.0.50727\CONFIG\
  2. Open the Machine.config file in a text editor.
  3. Replace <runtime/> with the following:
    <runtime>
    <generatePublisherEvidence enable="false"/>
    </runtime>
  4. Reboot the Host Server.

 

Last modified

Tags

Classifications

Public