we have receiving the SCOM data warehouse Database error from last 3 days. Got event error 31561,31551,31557,31569 and also has the below sql server exception Failed to store data in the Data Warehouse. The operation will be retried. Exception 'SqlException': Error 777970008, severity 16, state 1 was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage. Appreciate your help on this

Hi Can you let us know: - SCOM version: 2007 r2 or 2012 - SQL Version Have you applied any cumulative updates. If so, have you run the SQL scripts against the correct database when applying the update? Has anything changed in the last 3 days? Hot fixes \ patches? Cheers GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Hi Graham, We have SCOM 2007 r2 cu4 and moved the SCOM databases to sql 2008 last week Many thanks David

Sounds like this: http://blogs.technet.com/b/mgoedtel/archive/2007/08/06/update-to-moving-operationsmanager-database-steps.aspx Have you also enabled CLR as mentioned here: *** Note there is a footnote added by a user in the guide to enable CLR. This is REQUIRED it is missing from the core guide. http://blogs.technet.com/b/kevinholman/archive/2010/08/26/moving-the-operations-database-my-experience.aspx Cheers GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

I had enabled CLR and the script which mention on the below link. One of my colleague changed the scom passwords. After that below event is continuously logged on the sql server and above events Exception 'SqlException': Error 777970008, severity 16, state 1 was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage also OPsmgr reporting services not working

Got a Script from Microsoft support team and resolved the issue