Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

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
/*]]>*/