DPM Installation Error ID:820

April 19th, 2014

 

When you install DPM 2010, right after the prerequisites  verification you receive an error  “Verify that Windows Management Instrumentation (WMI) Service is running. if…

image

in order to fix this issue, you need to reinstall WMI , this is how to do it

From an elevated Command Prompt

1. Disable and stop the WMI service.

sc config winmgmt start= disabled

net stop winmgmt

2. Rename the Repository folder under C:\Windows\System32\wbem to Repository.old

3. Run the following commands.

Winmgmt /salvagerepository %windir%\System32\wbem

4. Re-enable the WMI service and then reboot the server to see how it goes.

sc config winmgmt start= auto

Management Pack Development Training

April 17th, 2014

System Center 2012 R2 Operations Manager Management Pack

 

 

image

SCOM ERRO Failed to connect to server

April 17th, 2014

 

you got the following error after installing SCOM

image

one of the reason is the Database log is full , normally this is not a common Issue we see  in SCOM  installation , since the OperationsManager DB is in Simple recovery mode , sometime you change the recovery mode to Full , in order to setup the database in Availability Group

resolution :

1- take a transactional backup to Shrink the log ,

2- Change the log file to AutoGrow  (i.e. 10 percent)image

3- Setup a frequent Backup for the the Database

 

Date: 4/17/2014 7:56:58 PM
Application: Operations Manager
Application Version: 7.1.10226.0
Severity: Error
Message: Failed to connect to server ‘SCOM01.backado.lcl’

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://scom01.backado.lcl:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:04.0070932. TCP error code 10061: No connection could be made because the target machine actively refused it 10.0.0.10:5724.  —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.0.0.10: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.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://scom01.backado.lcl:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:04.0070932. TCP error code 10061: No connection could be made because the target machine actively refused it 10.0.0.10:5724.  —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.0.0.10: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 (0×80004005): No connection could be made because the target machine actively refused it 10.0.0.10: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)

Microsoft Azure Brazil South region is now in public preview.

April 17th, 2014

 

image

DPM 2012 R2 Support Windows 2003 server

April 17th, 2014

 

Don’t be surprise , DPM 2012 R2 doesn’t support Windows server 2003 ,   the rollup update is coming shortly and it will fix the issue.

I know if Shreesh said that it will happen :)

image

Do I need to run maintenance on MY SCOM DBs ?

April 17th, 2014

 

This question came from Momo my DBA Friend, I have SCOM 2012 installed , what kind if maintenance Plan I need to run, Momo meant DBCC check, Index rebuild etc..

my answer nothing , you don’t need to run any maintain on SCOM DBs and the  reasons are the following :

1- there is a rule name “Optimize Indexes” that execute a daily database maintenance it calls a Store Proc name “p_OptimizeIndexes” , by default the rule runs once a day  at 2:30 AM , you can change the time (Configuration Tab,View DS  ),

image

the index optimization Store Proc has the following

image

SCOM Management Pack for SQL Server Analysis Services

April 17th, 2014

 

There is always something new , in the System Center area,  there is a new SQL Server Analysis Services released early January 2014

it supports the following :

1- SCOM 2012 and later

2- Virtualized SSAS instances

3- Clustered SSAS instances

Download the MP 

From Microsoft web site :

System Center Management Pack for SQL Server 2008 Analysis Services

System Center Management Pack for SQL Server 2012 Analysis Services

Monitoring Pack Purpose

Monitors Scenarios

1- SSAS Instance monitoring

2- SSAS Database monitoring

3- SSAS Partition monitoring

Health Rolls Up :

image

a well detailed article please visit Oleg’s Blog

ldm threshold reached in DPM

April 17th, 2014

 

The Issue started with the ldm threshold reached and we had to delete all the protection group and recreate then.

Due to this mass deletion of protection group. The pressure on the garbae collection job mounted as it had to delete lot of objects from sql database.

Now whenever the garbage collection job ran it increased the size of the tempdb which would consume almost all the space on the drive.

In order to find what query the garbage collection gets stuck we used this script.

image

the result Was:

image

Ran the garbage collection job along with this script and waited for tempdb to grow abnormally.

We got following output from the powershell script.

image

to fix the issue :

image

A huge credit to Abhishek   from the DPM Support Team

this is just a snapshots , from the resolution , if you get this error , don’t try to run the query on your own, i really recommend to contact MSFT support

OPSMGR execution of CLR code

April 17th, 2014

if you just installed SCOm m, and received the following ERRO , this is because CLR is not enabled  on your SQL Server

image

in order to resolve this issue , run the following command in SQL server that host your SQL server DBs

image

DPM 2012 R2 Installation ERROR

April 17th, 2014

 

DPM 2012 R2 doesn’t come anymore with SQL server , you either have to install an instance of SQL server in the same Machine , or use a remote SQL server to host the Database

During  the  installation of DPM 2012 R2 you may receive the following Error

SNAGHTML23e560d5

the cause of the error that DPM  need to have reporting server with HTTPS configured , in order to resolve this issue you need to Configure SSRS with HTTPS ()

image