Update Rollup 2 for System Center 2012 Service Pack 1–Service Manager updates

Update Rollup 2 for System Center 2012 Service Pack 1–Service Manager updates

  • Comments 22
  • Likes

hotfixUpdate Rollup 2 for Microsoft System Center 2012 Service Pack 1 (SP1) is now available and includes the following updates for Service Manager 2012 SP1:

Issue 1: If the number of "Manual Activities" that are displayed in the Service Manager Portal exceeds a certain limit, page loads may time out and do not render correctly. This results in a blank page.

Issue 2: Incorrect cleanup of a custom related type causes grooming on the EntityChangeLog table to stall. This causes the table to grow significantly.

Issue 3: Service requests complete unexpectedly because of a race condition between workflows.

Issue 4: The console crashes when you double-click a parent incident link on an extended incident class.

Issue 5: PowerShell tasks that were created by using the authoring tool do not run because of an incorrect reference to certain assemblies.

Issue 6: The Exchange management pack is stuck in a Pending state after management pack synchronization.

You can get all the details and a download link here:

KB2802159 - Description of Update Rollup 2 for System Center 2012 Service Pack 1 (http://support.microsoft.com/kb/2802159)

J.C. Hornbeck | Knowledge Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Hi team,

    Do you know what happened with Exchange Connector for SCSM? It was supposed to be released with UR2.

  • I too am curious about the Exchange Connector as I am limited in my functionality of Service Manager as a direct result of issues with the Connector.

  • We are targeting a release of the Exchange Connector for the end of the month.

  • Does this rollup work on server 2012 I tried to apply it and I am getting a signature error after accepting the EULA.

  • @Smezzer - yes, it should work on WS 2012

  • Travis, should we be on the lookout for an Update 3, or will the Exchange Connector be standalone?

  • @Luis - EC will be a separate download that will depend on SP1 UR2.  It is targeted to be released around the end of this month.

  • Which servers does the scsm 2012 sp1 update rollup 2 need to be applied to? One article: blogs.technet.com/.../how-to-apply-system-center-2012-sp1-update-rollup-2-ur2-to-other-system-center-components.aspx

    Says first install it on management server, then dw management server and then update all consoles.

    Is this correct?

  • Hi Travis - you say it should work on WS 2012.  Have you or anyone actually successfully done it as I have tried on 2 servers now and both failed with a signature error after the EULA is agreed on the update.

  • Trying to install this update on SCSM 2012 SP1 fresh install

    Installed correctly on Data Warehouse MS running Windows Server 2012

    Failed to install on:

    * Management Server running Windows Server 2012

    * SSP Server running Windows Server 2008 R2 and SPFoundation2010

    * member server running the SCSM console

    In every case:  after accepting the EULA, I get a stop error "Microsoft System Center 2012 Service Pack 1 - Service M has stopped working"

    There is nothing in any log that provides any insight.



     Stopped working

    Problem signature:

     Problem Event Name: CLR20r3

     Problem Signature 01: scsm2012_amd64_patchwizard.exe

     Problem Signature 02: 7.5.2905.125

     Problem Signature 03: 5150c405

     Problem Signature 04: mscorlib

     Problem Signature 05:

     Problem Signature 06: 4fee6afb

     Problem Signature 07: 34a7

     Problem Signature 08: 1c5

     Problem Signature 09: System.IO.IOException

     OS Version: 6.2.9200.

     Locale ID: 1033

    Read our privacy statement online:


    If the online privacy statement is not available, please read our privacy statement offline:



  • Jason, reboot your server and try to install again.

    This error will be resolved by a reboot I think.

  • Smezzer - We are sucessfully updated to Update 2 on Server 2012.

  • Hi travis,

    We have portal permissions page error after scsm 2012 sp1 rollup 2. When we enter the site permissions page on site settings. we have this error two different customers.

    We get this error;

    Server Error in '/' Application.


    Runtime Error

    Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.

    Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".

  • What about the Authoring Tool? Is there a SCSM 2012 SP1 CU2 update for this?

  • @Brad - No updates for the authoring tool in UR2.