This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

"SWL Initialize : Automation error"

"SWL Initialize  :  Automation error"

  • When and where are you seeing this error?

  • On the Kiwi Syslog errorlog.txt

  • 2016-06-16 13:30:28 SWL Initialize : -2146233088 : Automation error

    2016-06-16 13:30:29 SWL Initialize : -2146233088 : Automation error

    2016-06-16 14:30:29 SWL Initialize : -2146233088 : Automation error

    2016-06-16 14:30:30 SWL Initialize : -2146233088 : Automation error

    2016-06-16 15:30:30 SWL Initialize : -2146233088 : Automation error

    2016-06-16 16:30:32 SWL Initialize : -2146233088 : Automation error

    2016-06-16 17:30:33 SWL Initialize : -2146233088 : Automation error

    2016-06-16 18:30:33 SWL Initialize : -2146233088 : Automation error

    2016-06-16 19:30:34 SWL Initialize : -2146233088 : Automation error

  • This error is usually caused by one of our dll or ocx file getting unregistered.  This can happen after an Microsoft update.  Please try reinstalling Kiwi Syslog over the top of your current install.  Please run the install as the local administrator (not a domain account), and make sure both the Windows UAC and any antivirus software is disabled.

  • Running Syslog 9.6.7.1 and originally installed .NET 3.5 framework on a Windows 2016 server...So down the road a security scan shows vulnerabilities with .NET 3.5. I was asked to remove this role.  Syslog v9.6 shows it works with .NET 4, so it made since that 3.5 can be removed.  After removing 3.5, and 4 was previously installed and then a reboot...

    The Errorlog.txt had the following error

    2019-04-30 12:30:37    SWL Initialize : -2146232576 : Automation error

    2 things 'broke' removing .NET Framework 3.5

        the License change from fully licensed to "Free"
       The LicenseManager won't run...warning message states it needs .Net 3.5

    No updates available in the Syslog Manager console...

    will check with support...

  • I would recommend opening a case with support so that we can look over your logs.