This article describes a hotfix rollup package that resolves some issues in Microsoft System Center 2012 Service Manager Service Pack 1 (SP1). Additionally, this article contains the installation instructions for Update Rollup 6 for System Center 2012 Service Manager SP1.
Issues that are fixed in this update rollup
This update fixes the following issues that were not previously documented in the Microsoft Knowledge Base:
If the Manual Activities list that is displayed in the Service Manager portal exceeds a certain limit, page loads time out and do not display correctly. This causes a blank page to be displayed.
Incorrect cleanup of custom related types cause grooming on the EntityChangeLog table to stall. This causes the table to grow significantly.
Service requests finish unexpectedly because of a race condition between workflows.
The console crashes when you double-click the parent incident link on an extended incident class.
Windows PowerShell tasks that are created by using the authoring tool do not run because of an incorrect reference to certain assemblies.
Exchange Management Pack gets stuck in pending association after a Management Pack sync job.
“Run as Accounts” is enabled for use with the release version of Exchange Connector 3.0.
SQL broker conversations could lead to a very large OperationsManagerDB size and TempDB size.
Service requests that are put on hold are evaluated incorrectly as completed.
File attachments are not being correctly saved in the database.
The RunbookMonitorWorkflow process cannot handle a failed status of runbooks (workflow).
After you upgrade to SP1, new “Service Dependents” entries that are created for “Business Services” cannot be seen in the console.
Later activities in a service request start to run even though the current activity is not yet complete.
The Review Activity “add reviewer” workflow cannot run.
Simple lists in a self-service portal do not function correctly in the shared services provider (SSP) after you upgrade to SP1.
Windows PowerShell tasks that are created by using the authoring tool do not run.
For users who have both SMTP and SIP endpoints, Service Manager detects the Lync “sip” endpoint. This occurs even when you send email messages to users from the console.
After you select Service Requests with Service Level Warning, you receive a “FullAdapter” exception error message about one hour later.
After you select the Assigned to me view, you receive a FullAdapter” exception error message about one hour later.
Service Manager console maximized window fixes include the following:
- When maximized, the console is slow or unresponsive and has up to 30 percent CPU usage.
- Context menus in the console do not display where they are expected. Instead, they appear at the upper-right corner of the window.
- Work item scroll bars in the preview pane do not display correctly when you run in full-screen mode. When they do appear, they are inactive and cannot be used.
- Forms and wizards are not always displayed correctly. Only the left navigation pane is displayed, and the right side area is blank.
When you edit or create request offerings, user prompts do not display correctly.
Concurrent Windows PowerShell workflows cannot run, although they are listed as successful in the console.
An error occurs in the console when you try to open an attachment in a work item form that was already opened.
The attachment and its associated details of the release record cannot be retrieved after it is marked as closed.
The request offering form takes a long time to display when you create service requests from request offerings.j. The console crashes when you try to use an SR template that has an assigned analyst.
Creating a service request can cause a NullReferenceException error and can cause the console to crash.
The Service Manager console shows a generic SQL exception instead of the detailed Data Collision exception when you run in a non-English environment.
When you are grooming the database, the p_DataPurging stored procedure does not finish, and SQL registers an error that occurs with event ID 8623. The error states that the query processor ran out of internal resources and could not produce a query plan.
Adding multiple “RegEx”es to a group definition causes a SQL error when you add or execute the group.
The Configuration Manager connector does not handle updates to DeviceHasSoftwareItemInstalled correctly. This causes a divergence in the data that is synchronized between the Service Manager and Configuration Manager databases.
For more Info., you can check below link