Archive for the ‘Operations Manager’ Category

Management Pack Development Training

Thursday, April 17th, 2014

System Center 2012 R2 Operations Manager Management Pack

 

 

image

Do I need to run maintenance on MY SCOM DBs ?

Thursday, 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

Thursday, 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

OPSMGR execution of CLR code

Thursday, 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

SCOM ERRO Failed to connect to server

Wednesday, March 5th, 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)

CSMCollector service becomes inactive and doesn’t process requests after enabling 32-bit applications in “OperationsManagerCsmCollector v4.0” app pool configuration

Friday, April 26th, 2013

We have been working with ViaCode to deploy our APM monitoring, we have notice a strange behavior dealing with CSM monitoring implementation

As you know on 64-bit boxes in app pool configuration you can check to “Enable 32-Bit Applications” option. Say, for some reasons I had to enable it for CSMCollector app pool (“OperationsManagerCsmCollector v4.0”):

image

 

Having done this I noticed that I started missing CSM data. Albeit the web application pages are injected with uX scripts, the requests are sent to CSMCollector (I can check this with Fiddler), but I get no client-side events and statistics received at all.

I enabled APM trace log on affected server and got plenty of “CSMCollector ServiceManager is not active” errors like below:

Agent version: 7.0.5000.0
.NET Framework: v4.0.30319.269
ProcessID: 30488; InstanceID: 0;
InstanceName: w3wp.exe;
ApplicationPool: OperationsManagerCsmCollector v4.0;
Full Domain name: /LM/W3SVC/8/ROOT/CSMCollector-1-129917338260256050;

[0]30488.21608::09/10/2012-02:57:03.248 [Agent.CSMCollectorService] []
[Error] :CsmCollectorService.ProcessCsmEvent{csmcollectorservice_cs257}( 015DF0E0 )CSMCollector ServiceManager is not active.
[8]30488.1648::09/10/2012-02:58:34.369 [Agent.CSMCollectorService] []
[Error] :CsmCollectorService.ProcessCsmEvent{csmcollectorservice_cs257}( 020CF7FB )CSMCollector ServiceManager is not active.

 

When you enable 32-bit applications on the pool, it might start looking for CSMCollector keys in 32-bit branch and cannot find it there, while actually it’s registered in 64-bit registry path.

as MVP I have contacted Microsoft , and we filed up a bug.

SCOM 2012 Self-Study Guide

Tuesday, October 30th, 2012

from TechNet:

Microsoft Virtual Academy

Videos and Webcasts

Podcasts

Virtual Labs

Articles/Documentation

Useful Websites

Useful Blogs

Script Resources

Forums

  • Upgrade SCOM 2012 to Full Version

    Monday, August 13th, 2012

    After Installing SCOM 2012, you will notice that it is trial version , you can verify the status of your license either by running the PowerShell Command  or from the MMC about

    From PowerShell run the following command

    Get-SCOMManagementGroup | ft skuforlicense, version, timeofexpiration –a

    image

    open Operations Manager Console —> Help –> About

    image

    To convert from Eval to Full Version run the following command

    Set-SCOMLicense –productid <pid> where the PID is your product key.

    to confirm that you are in full version run again the following command

    image

    image