The Known Issues section of the KB article indicates that the agents need to be updated via the Repair Install process, not by simply approving them from the Pending Management view. Is this not correct? Your article indicates that they can be updated normally from the Pending Management view.

Thank you Kevin for a detailed step-by-step! Really appreciate it.

Good to see you back! However, this webpage appears to render images with the word "image" and not a real pic in ff and in IE I get the red X.

We did the update here and even in our tiny environ (87 agents, 2 MS, 2 GW), we had to stop the SCOM services on our MSs to do the SQL scripts. Otherwise, it went flawlessly, we had a couple of agents that didn't update, but that had nothing to do with SCOM (full C: drives, anyone?)

Glad you are back. Thanks for the details!

We update our agents manually (via SCCM). So far I have installed the URS agent update manually to about 10 servers. Every server wanted to reboot. I thought Microsoft committed to no reboots for agent updates. We can suppress the reboot in SCCM but will this cause any issues with the agent?

Hi Kevin,

A few days ago I've started receiving alerts in SCOM regarding "Failed to store data in the Data Warehouse. The operation will be retried.
Exception 'InvalidOperationException': The given value of type String from the data source cannot be converted to type nvarchar of the specified target column".

I've searched through the net and didn't find any proper solution regarding this issue.
In addition since I get these errors I'm experiencing problems with my RMS. Every time and now it turns to gray along with the Gateway server and only after I restart the SCOM services it returns to green.

1. Do you think that these issues are related ?
2. Is this fix mentioned in the post here can fix this issue ?

Thx in advance.

Dudu Sakharovich

Hi Kevin,

I installed the Update Rollups 3 on each system / role. Now when I run the first SQL script (UR_Datawarehouse.sql) against the OperationsManagerDW Database I get the following errors:I've installed all components successfully and I followed the right order by updating the components.
Msg 208, Level 16, State 1, Procedure GetStateDaily, Line 63
Invalid object name 'vManagedEntityMonitor'.
Msg 208, Level 16, State 1, Procedure GetStateHourly, Line 63
Invalid object name 'vManagedEntityMonitor'.

Hi actually i'm planning to install new SCOM 2012 R2 so shall i install only UR3 or start from UR1 until UR3.
Thanks

cool and useful docu, thanks a lot!

Here is a simple work around.

Known issues: Transaction (Process ID 152) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Stop all management server services (Monitoring, Data Access, Management system) on all the Management servers and rerun the SQL update.

Results Command completed Successfully.