Knowledge Base Article

Overview:

The SeeUnity Service does not start after an update to the server patches. Rules will not run.

Description:

The license may appear invalid, or the server log may report a startup error.  
The server log may also report a “fatal error starting kernal” and a missing SQL provider.

Impact:

Core Integration Server will not start, and no rules can run.

Steps to Reproduce:

After a server update, launch SeeUnity Server Management Studio and check if the license appears invalid, even though it should be.

Launch Echo Management Studio and a startup error appears.

Root Cause:

A recent server update has modified the available SQL providers. For example, Microsoft OLE DB Driver 19 for SQL Server may have been installed as part of the update.

Resolution:

Go to Program Files / SeeUnity Inc / Core Integration Services and view the adapters.xml, where the connection string is defined. Look for a reference to the Provider in the connection string, which may now be outdated.

Try "Provider=SQLNCLI11" or "Provider=MSOLEDBC", restart the SeeUnity Service and see if it runs again.