none
SCOM 2016 Operations Manager failed to connect to server. Data Access Service is either not running or not yet initialized. RRS feed

  • Question

  • Hi, I'm currently facing issues connecting to the Operations Manager Console on SCOM 2016, been reading and trying out all methods and suggestions from people who faced this issue but I'm still unable to resolve it. It seems that the Data Access Service crashes after a short period of time.

    Below are the logs I have collected from the console and event logs from the system.

    Operations Manager Error Log

    Date: 7/30/2019 4:57:59 PM
    Application: Operations Manager
    Application Version: 7.2.12066.0
    Severity: Error
    Message: Failed to connect to server 'SCOM.CONTOSO.COM'

    Microsoft.EnterpriseManagement.Common.ServiceNotRunningException: The Data Access service is either not running or not yet initialized. Check the event log for more information. ---> System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://scom.contoso.com:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:02.0045240. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.1.20:5724.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.1.20:5724
       at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
       at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       --- End of inner exception stack trace ---

    Server stack trace: 
       at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
       at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Channels.LayeredChannel`1.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
       at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.EnterpriseManagement.Common.Internal.IDispatcherService.Connect(SdkClientConnectionOptions connectionOptions)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Initialize(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
       --- End of inner exception stack trace ---
       at Microsoft.EnterpriseManagement.Common.Internal.ExceptionHandlers.HandleChannelExceptions(Exception ex)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.ConstructEnterpriseManagementGroupInternal[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore clientCallback)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.RetrieveEnterpriseManagementGroupInternal[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Connect[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
       at Microsoft.EnterpriseManagement.ManagementGroup.InternalInitialize(EnterpriseManagementConnectionSettings connectionSettings, ManagementGroupInternal internals)
       at Microsoft.EnterpriseManagement.Mom.Internal.UI.Common.ManagementGroupSessionManager.Connect(String server)
       at Microsoft.EnterpriseManagement.Monitoring.Console.Internal.ConsoleWindowBase.TryConnectToManagementGroupJob(Object sender, ConsoleJobEventArgs args)
    System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://scom.contoso.com:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:02.0045240. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.1.20:5724.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.1.20:5724
       at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
       at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       --- End of inner exception stack trace ---

    Server stack trace: 
       at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
       at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Channels.LayeredChannel`1.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
       at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.EnterpriseManagement.Common.Internal.IDispatcherService.Connect(SdkClientConnectionOptions connectionOptions)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Initialize(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
    System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 192.168.1.20:5724
       at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
       at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)

    Event Log - OpsMgr SDK Service

    The System Center Data Access service failed due to an unhandled exception.  
    The service will attempt to restart. 
    Exception: 

    Microsoft.EnterpriseManagement.Common.SdkServiceNotInitializedException: The Data Access service has not yet initialized. Please try again.
       at Microsoft.EnterpriseManagement.ServiceDataLayer.DispatcherService.get_Container()
       at Microsoft.EnterpriseManagement.Mom.Sdk.Service.SdkSubService.SdkChannel.Start()
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()

    Event Log - OpsMgr Management Configuration

    OpsMgr Management Configuration Service failed to communicate with System Center Data Access Service due to the following exception

    System.Runtime.Remoting.RemotingException: Unable to get ISdkService interface. Please make sure local Sdk Service is running.
       at Microsoft.EnterpriseManagement.ManagementConfiguration.Communication.CredentialDataProvider.CreateSdkConnector()
       at Microsoft.EnterpriseManagement.ManagementConfiguration.Communication.CredentialDataProvider.GetSecureData(Guid agentId, ICollection`1 addedReferenceList, ICollection`1 deletedReferenceList, ICollection`1 addedCredentialList, ICollection`1 deletedCredentialList, Byte[]& hashValue)
       at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.TracingCredentialDataProvider.GetSecureData(Guid agentId, ICollection`1 addedReferenceList, ICollection`1 deletedReferenceList, ICollection`1 addedCredentialList, ICollection`1 deletedCredentialList, Byte[]& hashValue)
       at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.AgentConfigurationFormatter.WriteSecureData(AgentConfigurationStream stream, XmlWriter writer, Guid agentId, Hashtable credentialAssociationList, Hashtable credentialList)

    Event Log (Application) - .NET Runtime Error Log

    Application: Microsoft.Mom.Sdk.ServiceHost.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: Microsoft.EnterpriseManagement.Common.SdkServiceNotInitializedException
       at Microsoft.EnterpriseManagement.ServiceDataLayer.DispatcherService.get_Container()
       at Microsoft.EnterpriseManagement.Mom.Sdk.Service.SdkSubService+SdkChannel.Start()
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()

    Event Log (Application) - Application Error Log

    Faulting application name: Microsoft.Mom.Sdk.ServiceHost.exe, version: 7.2.12150.0, time stamp: 0x5c9cd835
    Faulting module name: KERNELBASE.dll, version: 10.0.14393.2848, time stamp: 0x5c7f626e
    Exception code: 0xe0434352
    Fault offset: 0x0000000000034078
    Faulting process id: 0x154c
    Faulting application start time: 0x01d546b1f30ae0d1
    Faulting application path: C:\Program Files\Microsoft System Center 2016\Operations Manager\Server\Microsoft.Mom.Sdk.ServiceHost.exe
    Faulting module path: C:\Windows\System32\KERNELBASE.dll
    Report Id: ff3db2d7-97dd-4d5e-8255-bd205da286bd
    Faulting package full name: 
    Faulting package-relative application ID: 

    ------------------------------------ End of Logs ------------------------------------ 

    SCOM 2016 have been installed on to a Windows Server 2016 virtual machine. No Update Rollups have been installed on the SCOM 2016.

    I have Microsoft SQL Server 2016 installed on another set of Windows Server 2016 host machines configured in Active/Passive failover configuration which is handled by Failover cluster. This serves as my database for the SCOM 2016.

    Below are the steps I took trying to resolve the issue.

    - All firewalls have been turned off

    - Operations databases and warehouse databases are no where nearing their disk capacity(healthy)

    - Configured the Data Access Service and Management Configuration Service to use a Domain Account as their service account

    - Configured MSOMSdkSvc SPNs on the designated Service Account and the MSOMHSvc on the computer account that the SCOM is installed on. (According to this article https://kevinholman.com/2011/08/08/opsmgr-2012-what-should-the-spns-look-like/)

    - The Service Account used by the database is the same service account used by both the Data Access Service and Management Configuration Service.

    - The Service Account have been granted the following rights:

    • apm_datareader, apm_datawriter
    • ConfigService
    • ConfigServiceMonitoringUsers
    • configsvc_users
    • db_accessadmin
    • db_datareader, db_datawriter
    • db_ddladmin
    • db_owner,
    • db_securityadmin,
    • dbmodule_users
    • public,
    • sdk_users
    • sql_dependency_subscriber

    - Ensured that both SCOM VM and Database machines are using TLS 1.0 (TLS 1.1 and 1.2 keys have been removed entirely from the registry)

    - Ensured that the Service Account used is added into the local policy for "Logon Locally", "Logon as a service"

    - Added the Service Account to the Local Administrators of the SCOM VM and Database machines

    - Tested the connection on port 5724 of the SCOM VM but failed as the service is not listening on port 5724

    Been trying to resolve this issue for weeks but it seems like I'm back at where I started.


    • Edited by Clyde Joe Tuesday, July 30, 2019 11:31 AM
    Tuesday, July 30, 2019 11:29 AM

All replies

  • The root cause on which we need to focus is the SDK service/process crashing, the other events are consequences of this.

    However there is very little info here, as the events only return us an "unhandled exception"... That could be related to some sort of antivirus or hardened system, but I'm only guessing here.

    What you could try to get more  info is to run a diagnostic trace : http://blog.scomskills.com/scom-verbose-tracing/

     
    Tuesday, July 30, 2019 11:59 AM
  • Please confirm if the UDL test is successful from SCOM management server to SQL server.

    How to do a UDL test:

    1. Create a text file and save it with .udl extension

    2. Now provide the SQL server instance name which is hosting your SCOM OperationsManager database

    3. Now select windows authentication and test the connection.

    4. If it fails, please share the error message here.

    5. Also, please look at the system event logs if there is any failure related to Schannel errors.

    Regards,

    Sourav

    Tuesday, July 30, 2019 8:12 PM
  • Hi Sourav, The UDL test failed with the error “Test connection failed because of an error in initializing provider. [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.” when using the "Microsoft OLE DB Provider" for SQL Server as the Provider.

    However, the UDL test passed when "SQL Server Native Client 11.0" is used as the Provider.

    • Edited by Clyde Joe Thursday, August 1, 2019 11:52 AM updates
    Wednesday, July 31, 2019 6:45 AM
  • Hi CyrAz,

    I have obtain the diagnostic trace logs from the SCOM VM. Which log files should I look out for? So far from the errors in the logs, it did not say much about why the local sdk is not initialized.

    I have attached my logs to google drive via this link: https://drive.google.com/open?id=15w5tiz_gyXNhFqiDkya7ucDidv-SmyPp

    Regards,

    Clyde

    Thursday, August 1, 2019 11:59 AM
  • Hi Clyde, 

    Did you try restarting the SDK service while the debug trace was running? Because the TracingGuidsDAS.log is empty (DAS=Data Access Service=SDK, if I'm not mistaken), and as you said all the other files are just reporting errors because the SDK is not running...



    • Edited by CyrAz Thursday, August 1, 2019 12:14 PM
    Thursday, August 1, 2019 12:13 PM
  • Hi,

    It's seems to be an issue with TLS.

    Please check the following registry key on management server and SQL server and check if you are using any TLS protocol.

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols

    If TLS 1.2 is enabled and TLS 1.0 is disabled, please follow the below article and it should resolve your problem.

    https://souravmahato.co.in/scom/f/how-to-enable-tls-12-in-scom

    Thanks,

    Sourav


    Saturday, August 3, 2019 5:08 AM
  • >>The connection attempt lasted for a time span of 00:00:02.0045240. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.1.20:5724.  


    Please check whether management server can connect to 192.168.1.20 through the port 5724

    Roger
    Monday, August 5, 2019 4:40 AM
  • Hi CyrAz, I performed the Diagnostic trace again and made sure this time I restarted the SDK service while the debug trace was running. After 20 minutes, I stopped the trace but the TracingGuidsDAS.log is still empty.
    Thursday, August 8, 2019 2:38 AM
  • Hi Roger, the management server cannot be connected on 192.168.1.20 through port 5724 as there was no service listening on that port, despite already having the Data Access Service started in services.msc
    • Edited by Clyde Joe Thursday, August 8, 2019 2:41 AM
    Thursday, August 8, 2019 2:40 AM
  • Hi Sourav, TLS 1.2 is disabled and it’s subkeys were removed from the registry. Only TLS 1.0 and it’s subkeys exists in the registry now and is enabled.
    Thursday, August 8, 2019 2:43 AM
  • What is the role of server 192.168.1.20? Error message state that connection to 192.168.1.20 through port 5724 is block.

    Roger

    Friday, August 9, 2019 4:57 AM
  • Hi Roger,

    The server 192.168.1.20 is the windows server with SCOM installed and it is experiencing problem while opening the Operations Manager Console. It can't connect to itself on port 5724 is because the management server unable to start and I believe the reason for it being unable to start is due to the Data Access Service problem.

    Clyde

    • Edited by Clyde Joe Saturday, August 10, 2019 3:27 PM
    Saturday, August 10, 2019 3:27 PM
  • the Data Access Service is actually the service that listens on port 5724, which explains the connection failed error
    Saturday, August 10, 2019 11:09 PM
  • Repair the operations manager installation on MS which Data Access service has not yet initialized

    Roger
    Monday, August 12, 2019 7:30 AM
  • Hi Roger,

    After repairing the Operations Manager installation, the same problem still persists. I tried repairing the installation multiple times but the same problem still persists.

    The TracingGuidsDAS.log still turns up empty, which I have no idea why.

    Monday, August 12, 2019 8:25 AM
  • Hi,

    Have you made sure that you have no GPO that restricts membership of the local administrators group?

    Are all the DNS configured and resolving correctly of all servers?

    You mentioned that your firewalls were all turned off, which ones are you using?

    Check that the domain account used by the services has not had it's password expired or account locked.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, August 12, 2019 8:40 AM
  • Hi Leon,

    The DNS is configured and resolving correctly for the servers. As for the firewalls, only windows firewalls are in used and have been disabled for the time being. The domain account password has been set to never expire and account is not locked.

    That leaves the GPO as the main suspect, will re-look into the other GPO settings in the meantime.

    Monday, August 12, 2019 12:25 PM
  • Hi,

    As an update on the current situation, I managed to update the SCOM 2016 with UR7.

    • Ran the SQL Scripts that comes with UR7 on the SCOM Databases.
    • Enabled TLS 1.2 on the SCOM VM since it is able to support TLS 1.2 with UR7 update. Also included the SchUseStrongCrypto registry in the .NET Framework registry key. 
    • Enabled TLS 1.2 on the servers which are hosting the SCOM Databases. Also included the SchUseStrongCrypto registry in the .NET Framework registry key.

    However, after doing all that, the same problem still exists. Failed to connect to server 'SCOM.CONTOSO.COM'.

    I checked the GPO, the service account is included in the Logon Locally, Logon as a service entries. Which other entries in the GPO should I be looking at which may possibly be a contributing factor to this issue?

    Tuesday, August 13, 2019 12:15 PM
  • Has this configuration ever worked? Is this a new installation of SCOM 2016?

    Is the service account local administrator on both SQL Server cluster nodes?


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, August 13, 2019 1:13 PM
  • Hi Leon, Previously the SCOM was running fine but it stopped working one day and I could not get it back up since then. I tried the steps documented in other threads where users faced a similar issue, but I still could not get it to work. I thought it might be a TLS 1.2 issue as I updated the windows server but did not update the SCOM. From what I found out, the SCOM does not support TLS 1.2 out of the box, not until UR4 onwards. So I decided to update it with the latest UR7 in hopes of resolving what I thought could be a TLS 1.2 issue. But it turns out not to be the case.
    The service account is local administrator on both sql nodes.
    • Edited by Clyde Joe Tuesday, August 13, 2019 3:55 PM
    Tuesday, August 13, 2019 3:30 PM
  • Ok so this started happening one day all of sudden, do you remember which day?

    You also mentioned that the SCOM management server been patched, which Windows updates were installed? Could any of these be related?

    Do your event logs go back to the day it stopped working?

    Any "Schannel" related errors in the System event log? Or any new events in the Operations Manager event log?


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, August 13, 2019 8:44 PM
  • Hi Leon,

    Unfortunately I am unable to retrieve the logs back to the day it stopped working. It has been months since it stopped working.

    As for the windows updates, the following where installed:

    • KB2565063
    • KB4346087
    • KB4493470
    • KB4485447
    • KB4132216
    • KB4054590
    • KB4013418
    • KB3176936
    • KB3192137

    All the updates, I did a search online and did not find any conflicts with SCOM 2016.

    As for the Schannel errors, I have encountered one.

    "A fatal error occurred while creating a TLS client credential. The internal error state is 10013."

    However, I don't think its related to SCOM as from the Operations Manager Logs, the System Center Data Access service is reporting that it has reestablished database connectivity whenever it is being started.

    Friday, August 16, 2019 3:24 PM
  • Please check the following article if you have missed anything.

    https://souravmahato.co.in/scom/f/how-to-enable-tls-12-in-scom

    Regards,

    Sourav

    Sunday, August 18, 2019 8:18 AM
  • Hi Leon,

    Unfortunately I am unable to retrieve the logs back to the day it stopped working. It has been months since it stopped working.

    As for the windows updates, the following where installed:

    • KB2565063
    • KB4346087
    • KB4493470
    • KB4485447
    • KB4132216
    • KB4054590
    • KB4013418
    • KB3176936
    • KB3192137

    All the updates, I did a search online and did not find any conflicts with SCOM 2016.

    As for the Schannel errors, I have encountered one.

    "A fatal error occurred while creating a TLS client credential. The internal error state is 10013."

    However, I don't think its related to SCOM as from the Operations Manager Logs, the System Center Data Access service is reporting that it has reestablished database connectivity whenever it is being started.

    Have a look at Sourav's blog post, see if there's anything you've missed.

    As for the Schannel event error that you received, you can read some more about it over this blog post here:
    SCHANNEL event logging


    Blog: https://thesystemcenterblog.com LinkedIn:

    Sunday, August 18, 2019 9:26 PM