Link copied. Please paste this link to share this article on your social media post.
SmartConnector failed to start after restarting the computer - "Class not registered"
We are using SmartConnector 2.4.17. After restarting our server we got the following error:
2020-10-28 08:27:24.5174,Error,Service,<no principal>,Class not registered
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.Management.ManagementScope.InitializeGuts(Object o) at System.Management.ManagementScope.Initialize() at System.Management.ManagementObject.Initialize(Boolean getObject) at System.Management.ManagementClass.GetInstances(EnumerationOptions options) at SxL.Licensing.MachineThumbprinter.GetActiveMacAddresses() at SxL.Licensing.MachineThumbprinter.AllPossibleThumbprints() at Mongoose.Service.Licensing.LicenseEnforcer.ValidateLicense() at Mongoose.Service.Mongoose.HasValidFrameworkLicense()
2020-10-28 08:28:01.5316,Error,Service,<no principal>,Error while building type Mongoose.Service.LoggerFilterProvider. See the inner exception for details 1.) new LoggerFilterProvider() 2.) Mongoose.Service.LoggerFilterProvider 3.) Instance of SxL.Common.ILoggerFilterProvider (Mongoose.Service.LoggerFilterProvider) 4.) Container.GetInstance(SxL.Common.ILoggerFilterProvider)
An exception occurred while initializing the database. See the InnerException for details. An exception has been raised that is likely due to a transient failure. If you are connecting to a SQL Azure database consider using SqlAzureExecutionStrategy. The underlying provider failed on Open. An exception has been raised that is likely due to a transient failure. If you are connecting to a SQL Azure database consider using SqlAzureExecutionStrategy. The client was unable to establish a connection because of an error during connection initialization process before login. Possible causes include the following: the client tried to connect to an unsupported version of SQL Server; the server was too busy to accept new connections; or there was a resource limitation (insufficient memory or maximum allowed connections) on the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
After starting the SmartConnector service manually, it started with no problems.