If you saw the “This item cannot be updated because it has been changed by another user or process. To update the item, please close the item and open it again” exception then you know all that PAIN what filling engineers who implementing SCSM. But now we have THE SOLUTION.
Small note about how is helpful can be careful reading of the KB articles before do something. If you try to install SCSM 2012 R2 UR2 to unregistered SCSM DW you will get an error:
An error occurred while executing a custom action:_PatchMP
In log file you can find:
PatchMP: No Mp with MP Name ServiceManager.ServiceRequest.Library to patch, so failing in the MP patching
The reason is simple: have to read KB article. http://support.microsoft.com/kb/2904710/en-us :
Before you install the update, read the following instructions:
- Exit all Service Manager-related applications before you apply this update rollup. For example, exit the Service Manager console, the Self-Service Portal links, and the authoring tool.
- Make sure that the Service Manager data warehouse server is successfully synchronized with the Service Manager management server at least one time. For more information, see Registering with the Service Manager data warehouse to enable reporting (http://technet.microsoft.com/en-us/library/hh914224.aspx)
So, you CAN’T install UR2 on unregistered DW.
Thanks to Stanislav for pointing me to KB.
Sometimes you can’t install update rollup for SCSM because right after you press Install button on first page, the update process crashed. This issue came from very early versions of the SCSM and still sometime happened at this time, even for SCSM 2012 R2 UR2 update.
If you already read my blog posts about SLA in SCSM 2012 (Object model, How it’s works and “Hidden” features and “pausing” SLA) then you know what SLA process in SCSM 2012 is really complex and depend from many internal features of the SCSM. We are working in IT and know what sometime a things can work wrong even if no one touch it (or touch but don’t want to talk about this). This article is attempt to summaries information about issues with SLA in SCSM 2012 and how to troubleshoot them and solve.
You can change some settings for SCSM Self Service portal buy changing Settings.xml file. For example you can change number of questions per page (“DefaultNumberQuestionsPerPage“ parameter). But few days ago I have faced with strange issue: changes in Settings.xml doesn’t reflect on portal itself. Restart IIS and entire server has no effect.
When you create your own code to create new objects inside SCSM then soon or not but you’l get next exception just after calling Commt() method:
Cannot process extension elements as EnterpriseManagementObject. User EnterpriseManagementObjectProjection for all extension element CRUD operations.
What is that and why you get this?
You have imported your workflow to the SCSM but it doesn’t work. When you check Operations Manager log you find exception:
You’ve created a new workflow with XML and import it to SCSM. But for some reason it doesn’t listed in Workflow –> Status view. Why?
You’ve created a new class based on any existing class and have added existing form (with or without modifications) for it. Then you was imported management pack to SCSM and have tried to use that form but console was crashed with exception. Error “System.ArgumentException: propertyName” was recorded in “Operations Manager” event log. Why this happened?
Very short blogpost. SCOM agent of any version DOESN’T work on SCSM 2012 servers, even don’t try to install it, you can damage your SCSM installation. This is true for Beta, and, unfortunately, this is true for RTM too. So the only way to monitor SCSM servers with SCOM is a using agentless monitoring.
This is WRONG and confirmed by product team. OpsMgr agent of any versions still CAN’T coexist with SCSM 2012 RTM.
Updated 22.07.2013. Information about SCSM 2012 SP1. The SCSM 201 SP1 already contains the SCOM 2012 SP1 agent. For you this means:
- You can attach SCSM 2012 SP1 server to SCOM 2012 SP1 as manually installed. You no need to install agent on SCSM 2012 SP1 Server.
- You CAN’T update the SCSM 2012 SP1 agent to any new version of the SCOM 2012 Sp1 agent. Please don’t try to install SCOM agent’ UR on SCSM 2012 SP1 Server..