Hello All,

My SCOM 2012 console all of sudden stopped working when I changed the size of the SQL database for the SCOM server.

The setup is all on a virtual machine running windows 2012, with SQL 2012 running SCOM 2012 SP1. Everything was working until I made the SQL server database size change.

Now I am getting an error when I try to open the SCOM 2012 console. It just says Failed to connect to server servername.internaldomain.com The Data Access service is either not running or not yet initialized. Check the event log for more information.

here is the logs from the console app (the application logs are below this)

Date: 2/11/2013 12:16:45 PM
Application: Operations Manager
Application Version: 7.0.9538.0
Severity: Error
Message: Failed to connect to server 'servername.internaldomain.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://servername.internaldomain.com:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:02.0956135. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.X.X:5724.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.X.X: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.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.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.ManagementGroup.Connect(ManagementGroupConnectionSettings connectionSettings)
   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://servername.internaldomain.com:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:02.0956135. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.X.X:5724.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.X.X: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.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.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.X.X: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)

Application Error: Event ID:1000

Faulting application name: Microsoft.Mom.Sdk.ServiceHost.exe, version: 7.5.2808.0, time stamp: 0x5082b3a5
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16451, time stamp: 0x50988aa6
Exception code: 0xe0434352
Fault offset: 0x000000000003811c
Faulting process id: 0xb28
Faulting application start time: 0x01ce088d19221739
Faulting application path: C:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.Sdk.ServiceHost.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 5a80a27e-7480-11e2-93fc-00155d01651b
Faulting package full name:
Faulting package-relative application ID

.NET Runtime Error Event ID: 1026

First of all make sure that

DB size: SQL server, SQL agent is up and running or you can restart the above service

Management server: make sure that SDK service is up and running or restart the SDK service

Roger 

Hi

This Statement here " No connection could be made because the target machine actively refused it 192.168.X.X:5724." is either due to Connection issues Firewall, certificates etc. or I think it could well be that the database is to small.

Check the size of the database see here http://blog.scomfaq.ch/2012/06/26/scom-check-size-of-databases-sql-standard-reports/

Does SCOM itself work? Could you send screenshots of your db changes/size?

Cheers,

Stefan

Hello Stefan, I took a shot of the disk space here

The firewall is off and the certificates i'm not sure were ever an issue as I am pretty sure I did not set any up during the install. (cant remember) but it was all working fine for days just before I started getting errors that maybe the DB was too small so I followed another post to expand the space for the DB and I still cannot get the console to connect. (I get the error in my first post)

Not sure how to test if SCOM is working now without the console.  

Hello MS Hopeless guy,

It all worked fine two days ago, I have been using it for days. I was getting an error that said the db was full and needed to be expanded so I made it larger now and the console has not connected since. The SQL server and SQL server agent look like they are fine but the SDK service looks like it will not stay running. Every time I restart it or start it, it looks likes it running then I refresh and its no longer running. The errors in my first post state that its crashing for some reason now. I am feeling like its a DB size issue but I am not sure how to fix it. I am feeling like its just a configuration that I missed but I need assistance.

Thanks in advance for your help on this.

Hi

Check this post here http://thoughtsonopsmgr.blogspot.ch/2011/01/scom-r2-am-i-healthy-part-iii-are-dbs.html .

Can you send a screenshot of OperationsManagerDB -> Properties->Files where it Shows MOM_DATA and MOM_LOG files?

Cheers,

Stefan

Thanks Stefan,

I am reading the post now, here is the screen shot.

Hi

Turn off Autogrowth (take off the Enable Autogrowth checkmark) on Data and Log.

Set the MOM_DATA to 5000 MB and the MOM_LOG to 2500 MB, this should be big enough for the Moment. Next restart the SDK Services on each Management Server and see if it helps. It may take a Moment and you Need to restart the SDK Service 2-3 times until it "works"...

The try to connect with SCOM console...

Cheers,

Stefa

I have completed the tasks,

It seems that the SDK service will not stay running for some reason. I start it then refresh the services screen and its stopped again. Its just not staying running. Weird.

I tried that this but to the same results.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

ServicesPipeTimeout (DWORD (decimal)) = 60000

so it looks like the SCOM is still running as I am getting new events in the ops manager event log but the console is still failing to start due to the

Ok, the OperationsManager DB we configured correctly, you also tried to restart the SDK service several times. On the Management server, what are the latest errors in the operations Manager Event log after you startet the SDK Service?

Cann you make a screenshot of the OpsMgr Event log on the MS?

What did you Change right before your trouble started?

Cheers,

Stefan

The SQL server and SCOM MS are all on the same virtual machine. Its a one system show here :). We only have about 300 devices in our company that we wanting to track. I got SCCM 2012 all working (just an FYI in case you need to know).

The three errors I am getting in the operations manager event logs now seem to have changed when I just tried to restart the OMSDK service (see below) these are what popped up when I tried to restart the OMSDK service now.

these are the two errors I get in the application even log when I try to restart OMSDK

Hi

Just wondering, could you please check if the SDK service account is local administrator on each management server and also OperationsManager Administrator?

Cheers,

Stefan

I was using SCOMDAS account for OMSDK and it was not local admin on the management server (its all one box the MS the SQL and Console). I am using an account called SCOMAA as the admin account and it is within a group called SCOMAdmins and it is in the local administrators group.

I restarted the OMSDK and it took and I started the console and it looks like its working now. I wonder why it was working before and not after I made a change to SQL DB size? that is very odd. Maybe the account changed it self somehow? What are your thoughts on this? I would like to learn the reason.

Also, thank you so much for helping me with this. :)

Hi Robert

Well, strange why the account lost the permission and it has been working before. It is even harder to tell from far away :). I just saw on the Errors you posted that the account did not have enough permission to Access the registry therfore I was pretty sure it has to be something like this.

Just leave the database at 5 GB as you configured. It is best practice to set the db size at a reasonable size and not to set to autogrowth.

Please mark, it as answer and if you like vote as helpful :). Thank you...

Great I could help!

Cheers,

Stefan

• Proposed as answer by ANEESH BALU Tuesday, June 03, 2014 1:17 PM

• Proposed as answer by ANEESH BALU Tuesday, June 03, 2014 1:17 PM

• Proposed as answer by ANEESH BALU Tuesday, June 03, 2014 1:17 PM

First of all make sure that

DB size: SQL server, SQL agent is up and running or you can restart the above service

Management server: make sure that SDK service is up and running or restart the SDK service

Roger 

Thanks Roger.

Once I restart the SDK service and its working fine for me.

This issue we had today !!!.
After installing new updates and a reboot things went downhill fast.. but it had nothing to do with the updates (DUhhhh)

Found out that the port  the SQL server was listening on was manually set (at a later stage) to a static port so we didnt need the SQLbrowser, but we installed SCOM 2012 R2 (and) thus the management server talking to the default SQL port 1433 in the early stage.
All working fine until you reboot the management server...

This was found due to the fact that there was no communication between the Console and the Root MS (port 5724) and thus the database at all.

We changed the port back to 1433, and started the SQLbrowser exe.. and Voila .. Working like a charm..

We also installed the MS updates again of course

TIP : Check the port  the database is listening on... 

• Proposed as answer by Vijayanand63 Monday, December 01, 2014 4:51 PM
• Unproposed as answer by Vijayanand63 Monday, December 01, 2014 4:52 PM
• Proposed as answer by Vijayanand63 Monday, December 01, 2014 4:52 PM

This issue we had today !!!.
After installing new updates and a reboot things went downhill fast.. but it had nothing to do with the updates (DUhhhh)

Found out that the port  the SQL server was listening on was manually set (at a later stage) to a static port so we didnt need the SQLbrowser, but we installed SCOM 2012 R2 (and) thus the management server talking to the default SQL port 1433 in the early stage.
All working fine until you reboot the management server...

This was found due to the fact that there was no communication between the Console and the Root MS (port 5724) and thus the database at all.

We changed the port back to 1433, and started the SQLbrowser exe.. and Voila .. Working like a charm..

We also installed the MS updates again of course

TIP : Check the port  the database is listening on... 

• Proposed as answer by Vijayanand63 Monday, December 01, 2014 4:51 PM
• Unproposed as answer by Vijayanand63 Monday, December 01, 2014 4:52 PM
• Proposed as answer by Vijayanand63 Monday, December 01, 2014 4:52 PM

This issue we had today !!!.
After installing new updates and a reboot things went downhill fast.. but it had nothing to do with the updates (DUhhhh)

Found out that the port  the SQL server was listening on was manually set (at a later stage) to a static port so we didnt need the SQLbrowser, but we installed SCOM 2012 R2 (and) thus the management server talking to the default SQL port 1433 in the early stage.
All working fine until you reboot the management server...

This was found due to the fact that there was no communication between the Console and the Root MS (port 5724) and thus the database at all.

We changed the port back to 1433, and started the SQLbrowser exe.. and Voila .. Working like a charm..

We also installed the MS updates again of course

TIP : Check the port  the database is listening on... 

• Proposed as answer by Vijayanand63 Monday, December 01, 2014 4:51 PM
• Unproposed as answer by Vijayanand63 Monday, December 01, 2014 4:52 PM
• Proposed as answer by Vijayanand63 Monday, December 01, 2014 4:52 PM

Hi

The issue got resolved after refresh the SCOM Data base access service  account in SQL 2012.

Unable to launch the operations manager 2012 R2 console after extended the C drive of the SQl server ,getting error "The Data Access service is either not running or not yet initialized. "

Got to your SQL server -->databases-operationsmanager--security-users--locate the daa service account and refresh.issue fixed and am able to luanch.

we set the remote connection timeout=0

• Edited by mohamedeid 11 hours 31 minutes ago final modification
• Proposed as answer by mohamedeid 11 hours 30 minutes ago

we set the remote connection timeout=0

• Edited by mohamedeid Tuesday, April 07, 2015 7:38 PM final modification
• Proposed as answer by mohamedeid Tuesday, April 07, 2015 7:38 PM

we set the remote connection timeout=0

• Edited by mohamedeid Tuesday, April 07, 2015 7:38 PM final modification
• Proposed as answer by mohamedeid Tuesday, April 07, 2015 7:38 PM

we set the remote connection timeout=0

• Edited by mohamedeid Tuesday, April 07, 2015 7:38 PM final modification
• Proposed as answer by mohamedeid Tuesday, April 07, 2015 7:38 PM

At some point you changed your password on the System Center Data Access service from services.msc

change your password to match your domain password. Then start the service.

I have been chasing down this problem for days, and finally found the "problem" buried in a small bullet point on this TechNet article:

Technet: dn249696

• The db_owner role for the operational database must be a domain account. If you set the SQL Server Authentication to Mixed mode, and then try to add a local SQL Server login on the operational database, the Data Access service will not be able to start. For information about how to resolve the issue, see (link removed)

We had been having issues logging into SQL Mgmt Studio, and therefore created a SQL user to use temporarily until we figured out the login problem. It turns out, we broke it! 

The reason we were troubleshooting in the first place is that we migrated the VM for SCOM and SQL to a new host, and we were not getting new alerts. Then we couldn't log into SQL, etc etc... I checked everything in the forums, including this one (SPN registration, SQL allow remote connection, Database size, ports, etc etc... ) but finally! So I thought I would share:

DON'T ADD A SQL USER TO YOUR SCOM DATABASE if you're using Mixed Logon mode! :)

Hi ,

I also faced the same issue but its resolved now . :)

It was happening if your server suddenly rebooted or shutdown . Please go to services and register Microsoft System Center Data Access Service . Go to that service and right click properties select account give the account details and restart . Hope it will slove the issue . 

Hello ,

Can you explain how to register the service