Issues that are fixed by Update Rollup 4 for System Center 2012 Service Manager SP1

The following issues are fixed by Update Rollup 4 for Microsoft System Center 2012 Service Manager Service Pack 1 (SP1).

Issue 1

Customers receive multiple 33610 events on various rules and subscriptions. Additionally, the size of the EntityChangeLog table grows continually because of stalled grooming.

Issue 2

The console crashes when an analyst accidentally double-clicks a Parent Incident link (instead of a single click). This behavior occurs if the Incident Class has been extended. The console does not crash if the Incident class has not been extended.

Issue 3

Service requests are completed unexpectedly. (This behavior is intermittent.) Specifically, a service request is automatically completed, leaving the included activities in a pending state.

Issue 4

When a user has a large number of manual activities assigned to her, the "My Activities" view in the Self-Service Portal does not display the whole list of activities. Depending on the number of activities that are assigned to the user or group, the "My Activities" view may fail to render, and this results in an incorrectly rendered page that contains no information.

Issue 5

The Exchange management pack remains stuck in a "Pending Association" state in the management pack sync job within the console. Additionally, the status in the Management Pack node in the Data Warehouse space is displayed as "Failed." Event ID 33410 may also be generated from Source Deployment.

Issue 6

Service requests that are manually canceled during execution are marked as "Completed." They should instead be marked "Canceled."

Issue 7

When a new SqlNotificationRequest instance is created, new rows are generated in sys.conversation_endpoints DMV, and these show a "CO" state. Because the SqlNotificationRequest class doesn't provide any method to close those conversations, the sys.conversation_endpoints value quickly grows to an extremely large number.

Issue 8

Service requests that have been put on hold are incorrectly marked as "Completed."

Issue 9

File attachments are intermittently saved with 0 bytes in the database. The File Attachment record shows the correct data size together with file names and other information, but no actual data is saved to the database.

Issue 10

Service Manager cannot capture the failed status on invoked runbooks. Therefore, runbook activities have an "In Progress" status even though the invoked runbooks have finished with a "Failed" status.

Issue 11

After an upgrade to Service Manager 2012 SP1, the Service Dependents view under Business Services is not displayed correctly. Additionally, when you add one or more CIs as "Service Dependents" in order to create or edit a new business service, this fails to save the information.

Issue 12

The expected sequence of activities in a service request is not followed. Specifically, later activities in a service request start to run before the current activity has finished.

Issue 13

Event ID 33880 is generated. This event has a description of "A Windows Workflow Foundation workflow failed during execution."

Issue 14

Simple lists do not function correctly in SSP after you upgrade to SP1. Specifically, after you select an option in simple list, the option is not cleared when another option is selected.

Issue 15

You are unable to use "Run As" accounts with Exchange Connector.

Issue 16

PowerShell tasks that are created through the authoring tool do not run as expected. For example, when Service Manager runs the workflow, the workflow fails with the following error: