Event 31552 after OpsMgr and DW db moves
Hey all,
I have moved my scom opsmgr, OpsMgrDW, reportsdb and reportstempdb databases to a new server. (not the report server itself, just the backend databases). The new server is a cluster and I am addressing it through a cname that points to
that cluster IP. the sql server is listening on the default port on this IP so I have not entered instances anywhere in the configs. I followed the technet articles (http://technet.microsoft.com/en-us/library/cc540368.aspx, http://technet.microsoft.com/en-us/library/cc540384.aspx),
kholmans article and this article (http://blogs.technet.com/b/smsandmom/archive/2007/10/11/scom2007-moving-the-operations-manager-database.aspx).
I did not delete the databases from the original servers as specified in these articles but put them offline in case I needed to roll back.
Everything seems to be working as expected. alerts are coming in, reports are working etc. every 10 minutes I am getting error 31552 against my RMS. I have copied an example below.
I have checked and rechecked the following places for typos. I feel sure I am just missing a perm or an update spot somewhere. can anybody help me 'check my math' here?
opsmgr db server set in:
dbo.MT_ManagementGroup table HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Setup on each management server
dw db set in:
MT_DataWarehouse in opsmgrdb. (here the maindatabasename should be the DW db, right?)
dbo.MemberDatabase in opsmgrDW HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Reporting on reporting server and db server itself
My service accounts have the following db roles:
opsmgr db:
OM_DRA -
DB_datareader, public
OM_DWAA:
db_datareader dwsynch_users public
OM_MSAA:
db_datareader db_datawriter db_ddladmin dbmodule_users public
OM_SDK
configsvc_users db_datareader db_datawriter db_ddladmin public sdk_Users
opsmgrDW DB:
OM_DRA -
db_datareader opsmgrreader public
om_dwaa
db_owner OpsMgrWriter public
OM_SDK
db-datareader opsmgrreader public
I have seen this http://blogs.technet.com/b/kevinholman/archive/2010/08/30/the-31552-event-or-why-is-my-data-warehouse-server-consuming-so-much-cpu.aspx.
I went through the steps to disable the rule and run teh job. the job completes successfully in under 2 seconds.
I tried teh workflow analyzer from the authoring kit but it just spits out a few messages about setting up and then 'trace override has been submitted successfully' but nothing more after that.
help?
thanks
ej
-- cornasdf - http://cornasdf.blogspot.com
May 16th, 2011 2:15pm
I should note that I installed CU4 to the server infrastructure (not the agents) the day before I did this move. I should further note that hte move was from sql 2005 to sql 2008 r2 (hence the CU4 patch).
here is an example of the error I am getting every 10 minutes:
Description:
Failed to store data in the Data Warehouse. Exception 'SqlException': Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DataWarehouse.StandardDataSetMaintenance
Instance name: State data set
Instance ID: {1F656442-5C14-8AA7-6AA2-639319CB295C}
Management group: MYMG
-- cornasdf - http://cornasdf.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
May 16th, 2011 2:20pm
In my setup, SCOM has generated seperate user roles in the databases and assigned the accounts to those roles. Try to use these roles.Regards,
Marc Klaver
http://jama00.wordpress.com/
May 17th, 2011 1:57am
thanks for the response. can you elaborate on what roles/assignments you have? when I moved the dbs over, as soon as I linked my scom accounts they came up with the perms populated, presumably as they were before. The links above specify
the same data reader/writer and a few role perms.
thanks
ej-- cornasdf - http://cornasdf.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
May 17th, 2011 7:13am
Hi,
Regarding this Event, please also refer to:
Getting 31552 ->Exception 'SqlException': Timeout expired very frequently in SCOM server
http://blogs.technet.com/b/sudheesn/archive/2009/07/28/getting-31552-exception-sqlexception-timeout-expired-very-frequently-in-scom-server.aspx
Repost: EventID 31552
http://thoughtsonopsmgr.blogspot.com/2009/08/eventid-31552.html
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Hope this helps.
Thanks.
Nicholas Li - MSFT
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
May 18th, 2011 3:48am
Thanks for the reply.
I tried the above links to no avail. I opened a PSS case and he had me go through these (http://blogs.technet.com/b/kevinholman/archive/2010/08/30/the-31552-event-or-why-is-my-data-warehouse-server-consuming-so-much-cpu.aspx)
steps again. I had done this earlier and the query came back in no time at all. I have more fully qualified my db\instance,port information in the various places mentioned above since that time. Now, when I ran the query, it continued to
run. it has been running for 24 hours now. hopefully doing something. B) I can't tell if the cpu and disk usage on my machine are normal scom traffic or this query. i do see that my temp db has exploded in size (50gb now).
I will reply back w/ what happens. -- cornasdf - http://cornasdf.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
May 19th, 2011 9:10am
I think I messed up :) I didn't read enough of your first post. It looks like my config.Regards,
Marc Klaver
http://jama00.wordpress.com/
May 20th, 2011 2:14am