SCOM: Event ID “33333” in SCOM from Source “DataAccesslayer”

Hi,
From past few days i am getting Event ID code “33333” from source “DataAccesslayer” in Operations Manager Log of my RMS. This events are generating in almost every minute.

The error is indicating about to “Enable "clr" configuration option” is SQL server

Text Error Code

Event Type: Warning Event Source: DataAccessLayer Event Category: None Event ID: 33333 Date: 31/05/2011 Time: 09:28:41 User: N/A Computer: Foo-BAR Description: Data Access Layer rejected retry on SqlError: Request: MTV_SelectProperty_b87e82bc-1a85-4de3-330a-13133cf5f9c3 -- (ManagedTypeId=994bdf28-10b8-52e4-3334-d65a63d9fe52), (IsDeleted=False), (RegExPattern0=(?i)^10.0..*), (RegExPattern1=(?i)^10.1..*) Class: 16 Number: 6263 Message: Execution of user code in the .NET Framework is disabled. Enable "clr enabled" configuration option. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Solution:
I searched few website and finally I got the solution. The solution is to enable “CLR” option is “OperationsManager” database so that user codes in .NET can executes

To do this Connect to your SQL server and log in to SQL Server management Console.

Right Click the “OperationsManager” database and click on “New Query”

In “New Query windows” type the below code and then click on “Execute”

sp_configure @configname=clr_enabled, @configvalue=1 GO RECONFIGURE GO

 

 

In Message Pan you will see that it run successfully and “clr” option in changed from “0” to “1”.

After i done this, the error code “33333” not occurred again … 
source: TechNet
I hope it helps someone :)

Thanks
Aman Dhally

SCOM: SCOM not recognising SQL Server 2008 and Reporting Services installed

Hi
Yesterday I planned to install “Reporting Server” and “Data Warehouse” for SCOM on Microsoft SQL Server 2008. So to implement it i setup a new Server and Install Microsoft SQL Server 2008 and SQL Reporting Services in to it but when i run the “Check Prerequisites” from SCOM Installation media it was not recognising the  SQL and Reporting Services Installed.

Then I Click on More to check the details of the error.


Solutions:
The problem was “SCOM” needs “SQL Server 2008” with “Service Pack 1” or later. You can download SQL 2008 service pack 1 from here.
After Installation of Service Pack .. SCOM Detects the SQL Server 2008 and reporting Services.

I know its my mistakes. I should read the dependencies and prerequisites before doing anything.But I am sharing it may be it helps someone :)

Thanks
Aman Dhally

SCOM: How to Backup System Center Operations Manager 2007 R2

HI All,
Yesterday I was working on “How to Backup System Center Operations Manager 2007 R2”. I go through different document and posts and read few documentations and I think I should also share this information with you.
Our first step is to plan what to backup. So here is the list

1. Note down SCOM servers IP Address, Subnet, Gateway
   
2. Note down the Location of System Center Operations Manager Installation Path
   
3. Backup SCOM Databases
   1. OperationsManager (Operational Database)
      
   2. OperationsManagerDW (Dataware house Database)
      
   3. OperationsManagerAC (Audit Collection Server Database)
      
   4. ReportServer (Reporting Server Database)
      
   5. ReportServerTempDB (Reporting Server Temporary Database)
      
   6. Master (SQL Server Master Database)
      
   7. MsDbData (Msdb database)
4. IIS 6.0 Metabase or IIS 7.0 configuration
   
5. Root Management Server Encryption Key
   
6. Create List of All Management Pack Installed
   
7. Backup of Unsealed (customised) Management packs
   
8. SCOM Registry Keys
   
9. Backup your files

Let’s Start

1. I have noted down the IP-Address of SCOM including Subnet mask, Gateway IP and DNS Entries.
   
2. I noted down the location where is my SCOM in Installed, in my case it is installed on “C:\Program Files\System Center Operations Manager 2007”
   
3. Backup Databases

Operations Manager Operational Database (OperationsManager) 
The OperationsManager database contains almost all of the Operations Manager environment configuration settings, agent information, management packs with customizations, operations data, and other data required for Operations Manager to operate properly.
Note:     If your backup procedure sets the OperationsManager database to be offline during backup, Operations Manager caches incoming data, and then, after backup is complete, Operations Manager stores that data in the database.
Open “Microsoft SQL Server Management Studio” , Expend the “Database” , Right click on “OperationsManager”, choose “Tasks” and click on “Backup”

For now, I am choosing “Backup type = Full” and Name of the Backup and Backup Destinations, (for now I am backing up the data in to my network folder (Click on “ADD” to define the location of where you want to keep your backup”) and click on “OK”

After “Backup” process finish , you can see the data on your backup destination folder.


Do the same for all SCOM Databases ( OperationsManagerDW, OperationsManagerAC,ReportServer,ReportServerTempDB,Master,MsDbData)

• Reporting Databases (just a brief intro)

Operations Manager Reporting uses the following databases:
· Operations Manager 2007 data warehouse (OperationsManagerDW)
· SQL Server Reporting Services databases (ReportServer and ReportServerTempDB)
The OperationsManagerDW database contains all of the performance and other operational data from your Operations Manager environment. SQL Reporting Services then uses this data to generate reports such as trend analysis and performance tracking.

• ACS Database (just a brief intro)

The Audit Collection Services (ACS) database, OperationsManagerAC, is the central repository for events and security logs that are collected by ACS forwarders on monitored computers.
The OperationsManagerAC database can grow significantly depending upon how many ACS forwarders send events to the ACS database and the filters configured to control what events are written to the database.

• Master Database (just a brief intro)

The master database is a system database, which records all of the system-level information for a Microsoft SQL Server system, including the location of the database files. It also records all logon accounts and system configuration settings. The proper functionality of the master database is key to the operation of all of the databases in a SQL Server instance.

• MSDB Database (just a brief intro)

The MSDB database, Msdbdata, is a SQL system database, which is used by the SQL Server agent to schedule jobs and alerts and for recording operators. The proper functionality of the MSDB database is key to the operation of all the databases in a SQL Server instance.

Backup IIS Metabase
My SCOM installed on “Windows 2003 server”  so I am using IIS 6.0. To backup IIS 6.0 metabase, Go to RUN (windows key + R) and type “%systemroot%\system32\inetsrv\iis.msc” and hit OK

Right click on your “Computer Name” and then click on “All tasks” and choose “Backup/Restore configuration”

Click on “Create Backup” and then type the “Configurations backup Name” and then hit on “OK”

By Default all Metadata are stored in “%systemroot%\system32\inetsrv\MetaBack”


Backup Root Management Server Encryption Key
To restore SCOM from scratch we need “RMS Encryption Key”. You must backup “RMS Encryption Key” and store it on secure locations.
To backup an Encryption Key go to “C:\Program Files\System Center Operations Manager 2007” double click SecureStorageBackup.exe

When you double click “SecureStorageBackup.exe”, an “Encryption Key Backup and restore wizard” Open, click on NEXT

in “Select Action” choose to “Backup Encryption Key” and click on “NEXT”

Now “Specify the location of Backup File” where you want to save your encryption key, name it and click Next

Specify the password to protect the key and SCOM will ask for this password when we restore it after restorations after failure.

Click on “Finish”


Create List of All Management Pack Installed
It is handy to keep the latest list of all “Management Pack” installed in SCOM. The list will helps us to download or restore them. To create an List of All Management Packs, open “Operations Manager Shell” and type :
“Get-ManagementPack | Export-csv c:\ManagementPackList-May-2011.csv”


this will export all management packs in to .CSV file which we can import to excel and see the list of sealed and unsealed Management Packs
for example : Import the CSV file in to Microsoft Excel and create a filter on Data and the you are view list of All management packs by “sealed” or “Unsealed”


Backup of Unsealed (customised) Management packs
Open “System Center Operations Manager Console” click on “Monitoring” , click on “Management Packs” and sort the Management Packs by “Sealed” or “Unsealed”, choose the “Management pack” which you want to export, then right click it and choose “Export management pack”

choose the location where you want to save “Management Pack” and click on “Ok”

Exported “Successfully” , do the same for every unsealed Management Pack


Backup SCOM Registry Keys
I read on some posts that we need to backup SCOM registry Keys and it seems a good backup practice. so open “Registry editor" navigate to “My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\” and export the whole key.

Right Click on “Microsoft Operations manager” ,Click on “Export”

Choose the location where to save registry keys, and choose the file name make sure you have selected (Selected branch), and click on “Save”


Backup your files
The last thing to backup is your installation folder. :-).

As per Microsoft documentations when you restoring your folder make sure you don’t restore the “Heath service State” folder.

That’s all :-)
Hope it helps someone

Thanks
Aman Dhally

SCOM: Monitoring Windows Event Logs Using SCOM

HI, All
In my IT environment I am using “Symantec Backup Exec” to backup the data of the servers. from past few days some Backup Jobs are getting failed. We knew the failure of these backup jobs after few days after failure. After this incident I decide to monitor these backup failure using “SCOM”. For me the best option was to monitor “Windows Event Log”, because in SCOM it is very easy to monitor “Event Logs”
The “Symantec Backup Exec” log a “failure” or “success” event in “Application” Log. The event code for Failure is “341132. So for Monitoring i need to create a monitor which can alert me when Event ID 34113 created. So I plant to Monitor “Event ID 34113” from “Source Backup Exec”
Problem

Step: 1 Create a Monitor
Open “Authoring” Pane, select “Monitors”

Right click on “Monitors”, choose “Create a Monitor” and choose “Unit Monitor”

Expand “Windows Events” then expand “Simple event detection” and choose “Manual Reset” then choose you management pack where you are planning to save this “Monitor”

Type “Name” for this Monitor i am using “failure of Differential backup” and write a brief “Description” and in “Monitoring Target” i am choosing “Windows Server Operating System” because in my environment “Symantec backup exec” in installed on windows 2003 and 2008 servers, not click Next

choose the “Log Name” where your application write “event logs” in my case “Symantec Backup Exec” writes event in “Application Log” that’s why i choose “Application” now click on Next

Now we need to provide the Event ID and Event Source in Expression Builder so that is any event log matched this criteria created SCOM can alert us. In My case “Event ID is 34113” and Event Source is “Backup Exec” , now click on NEXT

Now we need to “Configure Health Conditions” so If “Event is Raised” then the status is “Warning” otherwise it is “Healthy” now click on “Next”

We need an alert when is Event is Created , so click on “Generate Alerts for this Monitor” and click on “Create”


Step: 2 Create a subscription
I am creating a New Subscription for it so that whenever this Event ID creates or Backup Job Fails then it should send an alert "our “Backup Administrators”
Click on “Administration” and Select “Subscriptions”

Right click on “Subscriptions” and choose “New Subscriptions”

Now Type “Subscription Name” and Description and click Next

In “Subscription Criteria” click on “Created by Specific rules or Monitors” and choose our previously created “Monitor” “Failure of Differential backup” and click on Next

Add users which intended to receive the alerts, after adding users click on NEXT
 
Choose Channels by which you are going to send an alerts, in my case I am sending alerts using an email. click NEXT

Click on “Enable this notifications subscription” and click on Finish.


Step: 3 Testing
Now its time to test the monitor, I used Logevent.exe to create an demo alert in window Application Log. See this link to know more about Logevent utility.


Step: 4 Result
Bingo !!! It shows warning in SCOM Alert window.

and it also send me an email about this alert :-)


I hope that this help someone :-)

Thanks
Aman Dhally