Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Release Notes for System Center 2012 - Operations Manager


These release notes apply to System Center 2012 – Operations Manager and contain known issues that you might experience.

The release notes contain the following sections:

  • Installation

  • Management Servers

  • Dashboard Views

  • Network Monitoring

  • UNIX and Linux

  • Alerts

  • Operations

  • Performance

  • Management Packs

  • Application Performance Monitoring

  • Management Pack Authoring

  • Product Connectors

You might see the following issues when you install Operations Manager.

Description: In Operations Manager, you can only install the first management server in a management group by using the option to create a new database, or install subsequent management servers to a management group by using an existing database. The option to install by using an existing empty operational database is not available for Operations Manager.

Workaround: There is no workaround.

Description: In Setup, when you designate the installation directory on the "Installation Location" page, if a folder has any leading spaces, the spaces will be removed. For example, "D:\ Test" will be changed to "D:\Test".

Workaround: There is no workaround.

Description: Installation of Operations Manager fails if the domain name or computer name contains Unicode characters. The event log for the installation will not contain an error message that explicitly states that the failure was due to Unicode characters.

Workaround: There is no workaround.

Description: Before you install the Operations console, install the hotfix from article 976898 (http://go.microsoft.com/fwlink/?LinkID=194637) in the Microsoft Knowledge Base. You have to contact Microsoft Customer Support Services to request the hotfix download. This hotfix helps prevent performance problems with the Operations console. After you install the hotfix, you must restart the computer.

This hotfix might not be required for all servers. The Operations console prerequisite checker checks for this prerequisite and alerts the user if it is not there. The hotfix has to be installed if the prerequisite checker finds that the hotfix is missing.

Description: When you uninstall Operations Manager, some exceptions might be logged in the OpsMgrSetupWizard.log file. These exceptions do not affect the functionality of uninstalling the program. You can ignore them.

Workaround: There is no workaround.

Description: Web console server side tracing cannot be performed on a Web console server without the Operations Manager agent or Operations console installed.

Workaround: Either install the Operations Manager agent or Operations console on the Web console server.

Description: After you install the Web console, you might experience ASP.NET or internal server (50x.x) errors, such as HTTP Error 500.19.

Workaround: Perform the following steps.

  1. At an elevated command prompt, reregister Internet Information Services (IIS) to use ASP.NET 4.0 by running the following command:

    %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -r

  2. Change the Webconsole IIS Application pool “OperationsManagerMonitoringView” ASP.NET framework integration from ASP.NET 4.0 to ASP.NET 2.0.

  3. Run IISreset.

Description: After you install the Web console, the console fails to open and you see the following error message:

Could not write to output file 'c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\operationsmanager\857ec549\f35afedc\App_global.asax.tyqhcqzi.dll' 

Workaround: Change the Identity of the OperationsManager application pool to run as LocalSystem by performing the following steps:

  1. Open IIS Manager.

  2. In the Connections pane, expand the server node and click Application Pools.

  3. On the Application Pools page, select the OperationsManager application pool, and then click Advanced Settings in the Actions pane.

  4. For the Identity property, click the ...  button to open the Application Pool Identity dialog box.

  5. Select LocalSystem in the Built-in account menu.

  6. Click OK.

Description: In Operations Manager, if you are using the networking monitoring feature in a management group where the devices being managed are behind gateway servers, these gateway servers must have .NET Framework 4 installed. The prerequisite checker does not check for .NET Framework 4 when you install a gateway server. If .NET Framework 4 is not installed, certain workflows such as network discovery will fail. The event log will only show that workflows have failed and been unloaded, but will not indicate that .NET Framework 4 is required.

Workaround: Install .NET Framework 4 on gateway servers. You can download the .NET Framework 4 redistributable package at http://go.microsoft.com/fwlink/?LinkId=201924.

Description: If you specify an action account during the upgrade process for the agent, the agent can stop communicating with its management server, and the agent will appear in an unmonitored (gray) state in the Operations console. The following events will be logged on the computer that is running the agent.

  • 7022 - The Health Service has downloaded secure configuration for management group Management Group 1, and processing the configuration failed with error code 0x80FF003F(0x80FF003F)

  • 20070 - The OpsMgr Connector connected to ManagementServer1, but the connection was closed immediately after authentication occurred. The most likely cause of this error is that the agent is not authorized to communicate with the server, or the server has not received configuration. Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.

Workaround: In the Operations console, in the Administration workspace, expand Run As Configuration, expand Accounts, right-click Local System Action Account, and then click Properties. In the Properties dialog box, on the Credentials tab, re-enter the password to the action account. Next, restart the Health service to restore communication to the management server.

Description: If you are upgrading an agent from Operations Manager 2007 to System Center 2012 – Operations Manager and that upgrade process fails, the agent may be removed completely. This is because the upgrade process has moved beyond the point where a rollback is possible.

Workaround: Reinstall the agent.

Description: SQL Server has a model database that is used as a template for creating new databases. If the size of this database is larger than the initial size that you specify for either the operational or data warehouse databases, then installation will fail.

Workaround: Specify a database size larger than the size of the model database.

Description: If you opted into the Customer Experience Improvement Program in Operations Manager 2007 R2 and then upgrade to System Center 2012 – Operations Manager, you will be automatically opted out.

Workaround Option 1: Perform the upgrade using the command line with the /SendCEIPReports:1 option. This will opt into the CEIP regardless of the previous setting.

Workaround Option 2: After the upgrade is completed, reset the CEIP settings to opt-in. The steps on how to perform this are in the privacy statement.

You might see the following issues related to management servers in Operations Manager .

Description: When the management server workloads are transferred to another management server on a failover, there is an intentional delay of one minute for the configuration manager to reload managed instances. This can result in managed objects being inactive for one to two minutes after the failover occurs.

Workaround: There is no workaround.

Description: If a management server runs out of Extensible Storage Engine (ESE) storage, it will create an error event in the Operations Manager event log with an ID of 623. This will leave the Health Service on the management server in an unworkable state.


  1. Stop the service System Center Management Health Service.

  2. Delete the health state directory and its contents. By default this is C:\Program Files\System Center Operations Manager 2012\Server\Health Service State. The path is stored in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HealthService\Parameters\State Directory.

  3. Start the service System Center Management Health Service.

You might see the following dashboard issues when you use Operations Manager.

Description: In new dashboard views, Find and Scope on the toolbar do not work.

Workaround: There is no workaround.

Description: To refresh the information displayed in the network or application monitoring dashboard views, you must navigate to another view and then navigate back to the network or application monitoring dashboard view. The Refresh task on the View menu and F5 do not work. If the dashboard view opens in a separate window, such as the Network Node dashboard view or the Network Vicinity dashboard view, you must close the window and then reopen it to refresh the information.

Workaround: There is no workaround.

Description: When you import a management pack mpb file, you must restart the Operations console before you can view the new dashboard view.


This does not apply to new dashboard views for Operations Manager which are installed during setup, nor to new management packs that use installed components. It only applies to .mpb files that install new or updated visual components.

Workaround: After you import a new version of a management pack that contains a binary used for dashboards, restart the Operations console.

Description: If you right-click an agent in the Agent Managed node in the Administration workspace and select to open a state view, the view will fail to open.

Workaround: In the Monitoring workspace, use the Agent Details views or create a custom state view.

Description: When you create a 1-column dashboard view by using the following steps, the dashboard view will display as a blank screen, with no option to add a widget.

  1. In the Monitoring workspace, right-click in the navigation tree, point to New, and then click Dashboard View.

  2. On the Template page, click Grid Layout, and then click Next.

  3. On the General Properties page, enter a name for the dashboard view.

  4. Click Previous.

  5. On the Template page, click Flow Layout and then click Next.

  6. On the General Properties page, click Next.

  7. On the Select Layout page, leave the Column Count value as “1” and click Next.

  8. On the Summary page, click Create.

  9. On the Completion page, click Close.

Workaround: To correct the empty dashboard view, perform the following steps.

  1. In the dashboard view, click the Configure button in the top right corner.

  2. Click Next to open the Select Layout page.

  3. In the Column Count field, overwrite the existing value “1” with “1”.

  4. Click Finish.

Description: If a user has a User Role that does not include all groups in the Group Scope, then the user will not be able to view, create, save, or delete dashboards in the My Workspace pane. This is a known issue in Operations Manager 2012.

Workaround: There is no workaround.

Description: If a user has a User Role that does not include all groups in the Group Scope, then the user may not be able to make personalization changes to dashboards and widgets, even if they are within the user’s scope. This is a known issue in Operations Manager.

Workaround: Have a user with administrative role make the required changes.

Description: If a user with an Author user profile creates a dashboard in the Monitoring pane, they will not see it until an Administrator updates the user role, even if the user role has been configured for all dashboards. This is because the dashboard is not automatically added to the scope of the profile when it is created. This is a known issue with Operations Manager.

Workaround: An Administrator must edit the user profile and provide access to the new dashboard.

Description: Changes that you make to custom views may not work properly. This is due to a known bug in Operations Manager.

Workaround: Restart the Operations console and attempt the configuration change again. If this is unsuccessful, delete the view and create it again.

Description: When you scroll a view with a table, such as an alert view or state view, to the right, the Operations console may crash. This is due to a known problem in Windows Presentation Foundation.

Workaround: Install hotfix described in http://support.microsoft.com/kb/2484832.

Description: When an agent is first discovered, there is a short interval when it may not have a health service watcher. If the agent is registered as not monitored and does not yet have a health service watcher when the Management Group Health dashboard does its calculation, the agent will incorrectly be counted as unavailable.

Workaround: This issue is temporary, and will automatically correct itself, once the health service watcher is discovered.

Description: If you are upgrading from Operations Manager Beta to Operations Manager Release Candidate, you will lose any personalization settings on dashboard widgets.

Workaround: There is no workaround for this issue, you must manually recreate the settings.

Description: You can create dashboards and add widgets to it using the web console. This is not supported in the Operations Manager though if the web console is installed on a localized version of Windows Server. This feature works if the web console is installed on the US-EN version of Windows Server.

Workaround: Use the Operations console to create the dashboards.

Description: The Objects by Performance widget displays the top specified number of objects sorted by a particular performance counter. This widget will display no data if you use (All) for the Instance.

Workaround: Select a specific instance instead of selecting (All).

Description: When a Read-Only Operator attempts to open a diagram view in the Web Console, they may receive an error saying that they do not have sufficient privileges. They may get this error even though they have appropriate permissions to the view. This problem is caused by permissions on a temp folder that are configured incorrectly.

Workaround: To correct the problem, perform the following steps on the server running in the web console.

  1. Open Windows Explorer and navigate to C:\Program Files\System Center 2012\Operations Manager\WebConsole\MonitoringView .

  2. Right-click the TempImages folder and select Properties.

  3. Select the Security tab and click Advanced.

  4. Click Change Permissions.

  5. Select Include inheritable permissions from this object’s parent.

  6. In the Permissions entries box, select the entry for SYSTEM and click Remove.

  7. In the Permissions entries box, select the entry for Administrators and click Remove.

  8. Click OK for each open dialog box.

Description: If the Operations Manager web console was installed with the option to require SSL, dashboards hosted in SharePoint may not display properly. This is an unsupported scenario in System Center 2012 - Operations Manager RTM.

Workaround: Change the configuration of the OperationsManager web site hosting the web console to not require SSL.

You might see the following issues when you use Operations Manager for network monitoring.

Description: If the Windows SNMP Trap service is running on an agent computer, that agent cannot receive SNMP traps from network devices. Ensure that this service is not running on any agent that is receiving SNMP traps that should be analyzed by Operations Manager.

Workaround: There is no workaround.

Description: Deleting more than 20 devices at one time can take considerably longer to run.

Workaround: We recommend that you delete network devices in batches no larger than 20 at a time to get the best performance.

Description: If the same network device is discovered by two or more management servers that are using different Run As accounts, only the first account is used to manage the device. If this account was not distributed to the other management servers, they will log errors about being unable to resolve the account.

Workaround: There is no workaround.

Description: If you use a gateway pool to monitor a large number of network devices, there will be high latency of performance counters and health state changes. This is due to a known performance impact from the method used to deliver data to the pool in Operations Manager.

Workaround: Reduce the number of network devices being monitored.

You might see the following issues related to UNIX and Linux computers in Operations Manager .

Description: If you want to use sudo elevation on a computer running Solaris, and the sudo executable is not in an expected path, you need to create a link to the correct path. Operations Manager will look for the sudo executable in the path /opt/sfw/bin, and then in the path /usr/bin. If sudo is not installed in one of these paths, a link is required.

Workaround: The UNIX and Linux agent installation script creates the symbolic link /etc/opt/microsoft/scx/conf/sudodir to the folder expected to contain sudo. The agent uses this symbolic link to access sudo. The installation script automatically creates the symbolic link, so no action is needed for standard UNIX and Linux configurations. However, if sudo is installed in a non-standard location, you should change the symbolic link to point to the folder where sudo is installed. If you change the symbolic link, its value is maintained for uninstall, re-install, and upgrade operations with the agent.

You might see the following issues related to alerts in Operations Manager .

Description: The All Management Servers Resource Pool Unavailable alert can remain active after all management servers have recovered from an unavailable state. This can occur when more than one management server in the server pool reports as unavailable within the same second, which generates multiple alerts. When the availability issue is resolved, only one alert is resolved.

Workaround: Verify that all management servers have network connectivity, are not in maintenance mode, and that the Health service is generating a heartbeat, and then resolve the alert manually in the Operations console. Do not resolve the alert manually if the majority of management servers are unavailable.

Some alerts in Operations Manager have incorrect or missing product knowledge. Refer to the following product knowledge articles for the following alerts:

Alert Name: Health Service Heartbeat Failure

Alert Description: The Health Service on <mgmt server name> failed to heartbeat.


The Health Service has stopped on a computer.

This alert is generated by the System Center Data Access Service on the agent’s management server when it has determined one of the members of the resource pool has not sent a heartbeat. The purpose of this alert is to inform the administrator that the host computer is unhealthy and will not perform monitoring as expected.

Error Alert: The System Center Data Access Service has failed multiple consecutive times to determine the availability of the server.


The following conditions can cause this alert:

  • The agent computer is not running.

  • The agent computer has lost network connection.

  • The Health service on the agent computer is placed into Maintenance Mode.

  • The Health service on the agent computer has been set to Manual/Disabled and the computer was restarted.

  • The Health service on the agent computer failed to start correctly.

  • The Health service on the agent computer has been stopped.


You can enable a recovery to automatically restart the agent if it fails.

In the event that the recovery is disabled or was not successful, you can navigate to the State Change Events tab and run the recovery from the details pane. To open the State Change Events tab, right-click the alert, select Open, and then click Health Explorer. In the Health Explorer, select the alert that is in a critical state, and then in the right-hand pane, click the State Change Events tab. In the details pane, click the recovery task to run the recovery.


A diagnostic task for this monitor runs ping to determine if the computer can be contacted from the management server. The default firewall settings for computers running Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2 prevent the computers from providing a ping response. To configure these computers to allow incoming ICMP traffic, see "Create an Inbound ICMP Rule on Windows 7, Windows Vista, Windows Server 2008, or Windows Server 2008 R2" (http://go.microsoft.com/fwlink/?LinkId=161045).

Additional Information

The below table explains the reason codes in the alert description:

Reason Code



The Health Service is paused.


The Health Service Action Account is configured incorrectly or has invalid credentials.


The Health Service failed to parse the new configuration.


The Health Service failed to load the new configuration.


A System Rule failed to load.


Collection of Object State Change Events is stalled.


Collection of Monitor State Change Events is stalled.


Collection of Alerts is stalled.


The Health Service is unable to register with the Event Log Service. The Health Service cannot log additional Heartbeat and Connector events.


The Health Service is unable to parse configuration XML.

When you select multiple alerts and then resolve the alerts by using Alert Status in the Properties dialog box, the resolution state for each alert will be updated in the operational database but might not update correctly in the Operations console. The resolution state for all alerts will update in the Operations console when you navigate to another view and then return to the alert view or when a new alert is generated.

Workaround: Navigate to another view and then return to the alert view to update alert resolution state.

You might see the following issues when you use Operations Manager.

Description: The Operations console might experience a memory leak over a period of time. This issue will be fixed in a future release of Operations Manager.

If the Operations console appears to be running slowly, perform the following steps to determine if a memory leak is the cause:

  1. Open Task Manager.

  2. Locate the console process Microsoft.EnterpriseManagement.Monitoring.Console.exe.

  3. Inspect the memory (Private Working Set) is using.

    If the console memory usage is higher than 700 MB, there is a memory leak.

Workaround: Close the console and then reopen the console.

Description: When you open the Operations console in a role other than administrator, My Subscriber Information and My Subscriptions options are available in the Tools menu, but do not work.

Workaround: There is no workaround.

Description: Print Preview does not work in diagram views. If you try to open Print Preview, the Operations console crashes.

Workaround: There is no workaround.

Description: In the Operations console, in the Administration workspace, the New Channel task on the Tasks menu of the toolbar does not work.

Workaround: To create a new channel, in the navigation pane, right-click Channels point to New channel, and then click the type of channel that you want to create.

Description: In an event view, the Show at least time filter does not work.

Workaround: There is no workaround.

Description: In the Operations console, the order of the sections in the Tasks pane might change when you open a view.

Workaround: There is no workaround.

Description: In the Active Alerts view, the options on the Override menu on the toolbar are unavailable.

Workaround: Select an alert, right-click, and point to Overrides. The Disable and Override options are available on this menu.

Description: If you create a state view showing all types of entities, some additional elements are visible with names starting such as "<Identifier Schema=...", which will appear as "Not Monitored".

Workaround: Create views targeted to specific types or limited to specific groups, rather than an entity. If you create a view showing all entities, these entities may be ignored.

Description: Workflows that use managed modules such as Windows PowerShell and Windows Workflow Foundation (WF) might crash when running on monitored Itanium-based systems.

Workaround: If the workflow was started manually, such as running a task, rerun the workflow. Scheduled workflows are likely to succeed the next time that they are scheduled to run.

Description: In Operations Manager, the Change Target Type task in the State Actions section of the Tasks pane does not work for the Discovered Inventory view.

Workaround: There is no workaround.

Description: Health Explorer and some dashboard views open a secondary console window. If you close the Operations console when the secondary console window is open, the secondary console window loses navigation functionality and might crash.

Workaround: Close all instances of the console and start over.

Description: In the Operations Manager , when you use the Online parameter with the Get-Help cmdlet for cmdlets included in the new Windows PowerShell v2 module, the Operations Manager TechCenter is displayed, rather than Help content specific to the cmdlet.

Workaround: Workaround: There is no workaround.

Description: When you open Properties for a Run As account, it may take several minutes for the Properties dialog box to open if the credentials for the Run As account have been distributed to more than 1000 computers.

Workaround: There is no workaround.

Description: If you run a task that targets a hosted entity that is managed by a resource pool, the task might generate inconsistent or inaccurate results. This is due to a change in how task workflows are handled with the addition of resource pools to the Operations Manager infrastructure.

Workaround: There is no workaround.

Description: If an agent is configured in both an Operations Manager 2007 R2 and Operations Manager management group, and that agent is used as the proxy for monitoring an application with the Windows Azure Application Monitoring Management Pack, the application monitoring may not work properly.

Description: If you have Silverlight 5 installed, when you right click an item in a view in the web console, the context menu is displayed but submenus are not. There is no workaround for this issue in Operations Manager.

Workaround: There is no workaround.

Description: Certain folder nodes in the Monitoring pane in both the Operations console and web console may be duplicated. This is a known issue in Operations Manager.

Workaround: There is no workaround required since both nodes are functional.

Description: In some wizards and dialog boxes, when you click a Help link or press F1, the Help file may open with an error page that states "This program cannot display the webpage". These links will be fixed in the next release.

Workaround: In the Help file, use the Contents tab or Search tab to locate the documentation you need.

You may experience degraded performance under the following conditions.

Description: It may take a long time to open a state view in the web console that lists thousands of objects.

Workaround: Workaround: Create a dashboard with a single state widget targeting the same object type but using a filter to only include objects with a particular health state. You can also modify a user role to limit the scope of objects that are included in the state view.

Description: It may take a long time to open the health explorer for an object with a deep monitoring hierarchy. This includes a group that contains many other objects that themselves contain other objects.

Workaround: Open the health explorer for an object lower in the monitoring hierarchy.

Description: It may take a long time to open a performance view that includes many objects with each of those objects containing many performance counters.

Workaround: Open the performance view for a single object.

Description: When you use the Operations Manager 2007 R2 command shell or type or script certain commands that make use of the provider, you might experience slow performance. This is due to changes to the underlying instance space and SDK which allow many more instances in the database. The Operations Manager 2007 R2 command shell was not designed to deal with this many instances.

Workaround: Use the Operations Manager command shell.

You might see the following issues related to Management Packs when you use System Center 2012 – Operations Manager.

Description: Most existing management packs written for Operations Manager 2007 SP1 or Operations Manager 2007 R2 are compatible with System Center 2012 – Operations Manager. If a management pack has any of the following features, it may not work properly in System Center 2012 – Operations Manager.

  • Management packs that require new modules on the agent, management pack templates, or new view types. The APIs for Operations Manager have changed which may break these features.

  • Management packs that attempt to create or update other management packs or management pack elements.

  • Management packs that leverage SNMP modules and SNMP network devices discovered by Operations Manager 2007. These management packs will continue to work after an upgrade, but they will be unable to target network devices discovered through the Operations Manager discovery wizard.

Workaround: You should report any incompatibilities that you identify to the vendor of the management pack so that they can make appropriate corrections. You should also report the issue to the Feedback Center on Microsoft Connect (https://connect.microsoft.com/OpsMgr/Feedback)

Description: The task in the SharePoint 2010 MP to configure the SharePoint servers to be monitored fails in Operations Manager. The task runs a Windows PowerShell script that is leveraging SDK calls that are not supported in Operations Manager. This occurs in both new and upgraded installations. If the task is run in Operations Manager 2007 R2 before upgrading to System Center 2012 – Operations Manager, the SharePoint Servers will continue to be monitored. This issue only occurs if the servers to be monitored are changed or configured for the first time.

Workaround: Import the SharePoint Management Pack from Connect and run the Configure SharePoint Management Pack (SCOM 2012) task.

Description: An error message will be displayed if the Microsoft Exchange 2007 Template management pack is installed from the catalog in Operations Manager.

Workaround: Download the management pack to disk and then import into the management group.

Description: If you use the Operations console to export a management pack which contains resources such as icons, the management pack cannot be subsequently imported in Operations Manager .

Workaround: There is no workaround.

You might see the following issues related to Application Performance Monitoring when you use System Center 2012 – Operations Manager.

Description: If you are using a dashboard that includes an alert widget and you view an alert raised by APM, you will not be able to use the link embedded in the alert description to launch the APM event details in Application Diagnostics.

Workaround: Open the alert in an alert view.

Workaround: Install the web console in the management group.

Description: After you configure client-side monitoring on a server for the first time, you may receive an event with ID 1108 saying that an account specified in the Run As profile Microsoft.SystemCenter.Apm.Csm.EncryptionProfile cannot be resolved. This will create an alert in Operations Manager that does not automatically resolve.

This event occurs because the rules used to collect data for client-side monitoring may start running before the Run As account is sent to the health service. The Run As account will be downloaded, at which point client-side monitoring will be fully functional.

Workaround: There is no workaround required. You can safely ignore the event and resolve the alert.

Description: After upgrading to Operations Manager you may see a series of error events with ID 4508 and 4509 in the event log on agent managed computers. This is because some of the assemblies required by the APM modules have either not yet been downloaded through dependency download or are not being loaded due to a problem with the health service cache.

Workaround: Restart the health service on the agent to clear the cache and ensure that the proper assemblies are loaded.

Description: If you used the .NET Application Performance Monitoring template in the Beta version of Operations Manager to monitor applications, those templates need to be deleted and recreated in the release version of Operations Manager. Any templates created in the Release Candidate will work in RTM.

Workaround: Delete and recreate the templates.

Description: In an environment where the application process is configured to be named <process>_<PID> in System Performance Monitor, performance counters and other data will not be aggregated across all instances of the application. Instead each process will show up as a discreet application.

Workaround: Do not use the PID in the name if require grouping by process name.

Description: If you create a new environment tag with longer than 255 characters, you will get configuration failures on the agent side when the agent tries to configure monitoring for the application.

Workaround: Reduce the size of the environment tag.

Description: With some WCF services the IIS API is unable to detect the version of .NET being used by the application pool. In these cases, the API will default to using the .NET 2.0 configuration files. If this happens, discovery will not be able to pull secondary endpoint properties from the application and will raise a warning.

Workaround: There is no workaround available.

Description: Valid users may on rare occasion lose access to the Application Diagnostics and Advisor consoles. Connections to SQL Server are closed as “un-authorized access”.

Workaround: Restart the SQL Server hosting the Operations Manager database.

You might see the following issues related to management pack authoring when you use Operations Manager.

Description: When creating or modifying a group, it can take a long time to search for an instance if a large number of items are returned.

Workaround: Either wait for the instances to be returned or change the search to return fewer instances.

Description: Management packs that are exported from Operations Manager cannot be opened in the Operations Manager 2007 R2 Authoring Console. Management packs created by the Operations Manager R2 Authoring Console and any management packs created in Operations Manager 2007 R2 can be imported into System Center 2012 – Operations Manager.

Workaround: Edit the management pack in Operations Manager 2007 R2 or export from an existing Operations Manager 2007 R2 management group into the Authoring console. Once you have completed your edits, then import the management pack into Operations Manager.

You might see the following issues related to product connectors when you use System Center 2012 – Operations Manager.

Description: The following connectors are not supported and may not work in System Center 2012 – Operations Manager.

  • Microsoft System Center Operations Manager 2007 R2 Connector for IBM Tivoli Enterprise Console

  • Microsoft System Center Operations Manager 2007 R2 Connector for HP OpenView Operations for Unix

  • Microsoft System Center Operations Manager 2007 R2 Connector for HP OpenView Operations for Windows

  • Microsoft System Center Operations Manager 2007 R2 Connector for BMC Remedy ARS

  • Microsoft System Center Operations Manager 2007 R2 Universal Connector

If you have any of these connectors installed and open the Interop Connectors node in the Operations console, you may receive an error message.

Workaround: Interoperability between Operations Manager and other products is through System Center Orchestrator 2012.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft