You cannot install Operations Manager 2007 Reporting if the SQL Server Reporting Services instance takes more than 60 seconds to start

New KB Released #951148

SYMPTOMS

When you try to install Microsoft System Center Operations Manager 2007 Reporting, the installation operation fails. This problem occurs if the Microsoft SQL Server Reporting Services (ReportServer) instance takes more than 60 seconds to start.When this problem occurs, the Momreporting.log file contains the following information:

 

ReplaceSRSExtensionsCA error: Cannot start service ReportServer on computer ‘.’.. StackTrace: at System.ServiceProcess.ServiceController.Start(String args) at Microsoft.Reporting.Setup.ReportingManagedCAs.RestartService(String srsServiceName) at Microsoft.Reporting.Setup.ReportingManagedCAs.ReplaceSRSExtensionsCA(Session session)

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

 

http://support.microsoft.com/contactus/?ws=support

 (http://support.microsoft.com/contactus/?ws=support)

Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have System Center Operations Manager 2007 Service Pack 1 (SP1) installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

Hotfix installation instructions

This hotfix provides a Microsoft Installer (.msi) file that you can use to fix the existing Reporting2007.msi file in the installation media. Then, you can use the fixed Reporting2007.msi file to install Operations Manager 2007 Reporting. To do this, follow these steps:

1.

Copy the following file from the hotfix package to a local folder or to a shared folder:

SystemCenterOperationsManager2007-SP1-KB951148-X86-X64-ENU.msi

2.

Run the file that you copied in step 1.

3.

On the Select Installation Folder page of the installation wizard, you can specify a folder in which the hotfix will be installed. By default, this hotfix is installed in the following location:

%ProgramFiles%\System Center 2007 Hotfix Utility\Q951148

4.

The Q951148 folder contains the following files:

A Q951148-x86.mst file for x86 platforms

A Q951148-x64.mst file for x64 platforms

5.

Locate the Reporting2007.msi file in the Operations Manager 2007 Service Pack 1 installation media. The Reporting2007.msi is located in the following folder on the installation media:

Reporting\platform

Note The platform placeholder represents the platform version of Operations Manager 2007 Reporting that you want to install.

6.

Copy this Reporting2007.msi file from the installation media to the Q951148 folder that is mentioned in step 3.

7.

Change the working directory to the Q951148 folder that is mentioned in step 3. For example, if you used the default installation folder in step 2, open a command prompt, type the following command, and then press ENTER:

cd /d %ProgramFiles%\System Center 2007 Hotfix Utility\Q951148

8.

At the command prompt, run the following command:

WiUseXfm.vbs Reporting2007.msi MST_File

Note Replace the MST_File placeholder with “Q951148-x86.mst” or with “Q951148-x64.mst,” as appropriate for your platform.

9.

To verify that the Reporting2007.msi file is successfully fixed, check the last modified time of the Reporting2007.msi file.

10.

Replace the old Reporting2007.msi file by copying the fixed Reporting2007.msi file onto the installation media. If the installation media is read-only, you can install Operations Manager 2007 Reporting directly by using the fixed Reporting2007.msi file. To do this, open a command prompt, type the following command, and then press ENTER:

msiexec /i Modified_MSI_Location\reporting2007.msi /l*v %TEMP%\MOMReporting.log

Note Replace the Modified_MSI_Location placeholder with the folder that contains the fixed Reporting2007.msi file.

Note After you follow these steps, the digital signature in the fixed Reporting2007.msi file will be broken. Therefore, you will receive a warning message when you run the fixed Reporting2007.msi file. You can safely ignore this warning message.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

System Center Operations Manager 2007 Service Pack 1

File name

File version

File size

Date

Time

Platform

Q951148-x64.mst

Not Applicable

2,637,824

01-Apr-2008

06:56

Not Applicable

Q951148-x86.mst

Not Applicable

2,571,776

01-Apr-2008

06:46

Not Applicable

Wiusexfm.vbs

Not Applicable

2,822

18-Oct-2002

08:19

Not Applicable

 

Continue Reading

Hyper-V is RTM!

Microsoft has released Hyper-V. I recently installed it on my Dell Optiplex 745, that has a dual core E6600 Processor with 4gb of RAM.

I am running Server 2008 x64 (Core Edition).

Here are my benchmarks.

  • The red is benchmark for the VMs processor.
  • The orange is the benchmark for the physical processor.

Pretty Impressive!

Continue Reading

You receive error messages when you try to edit the Web application monitoring settings in System Center Operations Manager 2007

Looks like microsoft posted the KB for this. KB 941977

SYMPTOMS

When you try to edit the Web application monitoring settings in Microsoft System Center Operations Manager 2007, you receive the following error messages:

Failed to load Web Application

Microsoft.EnterpriseManagement.Common.ObjectNotFoundException: Requested object(s) not found.

This problem occurs if a user in the Operator user role opens the Operations console when the user in the Administrator user role tries to edit the Web application monitoring settings.

http://support.microsoft.com/default.aspx/kb/941977

Continue Reading

Unable to edit web application monitors after upgrading to SCOM 2007 SP1 hotfix available

If you upgraded to SCOM SP1 from SCOM RTM you will notice that you are no longer able to edit your web monitors that you created before the upgrade. Any Web monitors that were created after the upgrade, you will be able to edit fine.

The error you will get is “There was an error while applying the changes.” “An object of type UnitMonitorType with Id (GUID) was not found.

If you are having this same issue a fix has been created by Microsoft. You will have to call Microsoft Support to the the hot fix. The KB number is 951527.

This fix is not publicly available through the Microsoft website as it has not gone through full Microsoft regression testing.

FileName: SystemCenterOperationsManager2007-SP1-KB951527-X86-X64-ENU.MSI

Continue Reading

If you delete one of your management servers that have SNMP devices reporting to it, the SNMP network devices will become orphaned in the database.

I recently discovered a bug where if you delete one of your management servers that have SNMP network devices reporting to it, the network devices will be orphaned in the database.

We had to remove one of our management servers due to hardware issues. Before we could remove the management server we had to move all computers reporting to it to another management server. The console will not let you remove the management sever until all computers are moved off it.

The problem lies in the fact that Ops Mgr will let you remove a management server that has SNMP network devices still reporting to it.

After the Management server is deleted the devices will no longer show up in the Administration console. You will also not be able to re-discover them as they already exist in the DB.

The only way to fix the problem is to restore the database or some custom magic from MS Professional Support Services.

Microsoft was able to repo this same situation in their labs and confirmed it’s a bug that will be addressed in future versions. Big thanks to Nicholas Dodge from Microsoft PSS for seeing this case through.

Continue Reading

Announcing System Center Operations Manager 2007 Cross Platform Extensions and Connectors

From http://blogs.msdn.com/scxplat/archive/2008/04/29/announcing-system-center-operations-manager-2007-cross-platform-extensions-and-connectors.aspx

Today Microsoft announced a few new beta products – two of which came from our team. The System Center Operations Manager 2007 Cross Platform Extensions, which enable customers to manage Unix/Linux systems from Operations Manager 2007, was delivered as a beta today. If you were attending Bob Muglia’s Keynote this morning then you walked away with a CD containing the beta bits.

The second beta announcement from our team was the availability of the System Center Operations Manager 2007 Connectors for HP OpenView (Unix/Windows) and IBM Tivoli Enterprise Console (TEC). CD’s will be available later this week at MMS.

Both betas are available on http://connect.microsoft.com/ – search for systemcenter. If you’re attending MMS, then stop by and see us at the Operations Manager 2007 Pod. You can also attend the two breakout sessions:
– SO20 – System Center Operations Manager 2007 Cross Platform Extensions
– SO09 – Connectors for System Center: The Microsoft Interop Strategy

Also, there’s a hands on lab for the Cross Platform Extensions at MMS – details will follow later. Tonight there will be a birds of a feather session – BO03 Integrating with Microsoft Systems in a Mixed Environment (Windows, Linux, OSX etc).

If you happen to be at ‘Interop Las Vegas’ down the street at Mandalay Bay, then stop by and see us at the Microsoft booth.

We look forward to keeping this site updated with information, tips, and tricks about these new products from our group. Please check us out often.

The Cross Plat and Interop team

You can download the Cross Platform Extensions Beta through Microsoft Connect. To help you navigate to the right spot, follow these directions:

  • Go to Microsoft Connect, and log in.
  • Click on Connection Directory at the top menu.
  • Scroll down the list of categories to System Center TAP/Beta.
  • Within this category you will see the Program, “Operations Manager Public Beta (Cross Platform and Interop)”. Click Apply Now.
  • Complete the survey, and then you’re in and can download the Ops Mgr Cross Plat Beta!
Continue Reading

NEW MP for cluster services (MSCS) monitoring was released!

UPDATE: NEW MP for cluster services (MSCS) monitoring was released!

http://www.microsoft.com/downloads/details.aspx?FamilyId=AC7F42F5-33E9-453D-A923-171C8E1E8E55&displaylang=en

What is included with this release:
· Bug fixes monitoring of cluster resource group and cluster resource when name contains special character.
· Bug fixes for proper recognition of partially online cluster resource group.
· Bug fixes for noisy level of disk resource monitoring.
· Bug fixes for proper account usage with all discovery workflows (Cluster profile which needs to be populated when default action account doesn’t hold enough privileges to monitor cluster.)
· Preparation for Windows 2008 Failover Cluster management pack (type space and base functionality is shared between Win2k3 and Win2k8 cluster infra monitoring)
· Additional work including some further minor changes …

Following management pack files are available with this release:
Microsoft.Windows.Cluster.Management.Library.mp (6.0.6277.1)
Microsoft.Windows.Cluster.Management.Monitoring.mp (6.0.6277.1)
Microsoft.Windows.2003.Cluster.Management.Library.mp (6.0.6277.1)
Microsoft.Windows.2003.Cluster.Management.Monitoring.mp (6.0.6277.1)

Similarly to previous version, please follow these steps before importing management packs to meet requirements:

If you have installed, remove any and all versions of following management pack files prior to importing version included with this release:
· Microsoft.Windows.2003.Cluster.Management.Monitoring
· Microsoft.Windows.2003.Cluster.Management.Library
· Microsoft.Windows.Cluster.Management.Monitoring
· Microsoft.Windows.Cluster.Management.Library

NOTE: unfortunately with upcoming release of Windows 2008 Failover Cluster Management Packs, breaking change had to be introduced with Cluster Views and minor change in discovery, where such regrettably prohibits importing new version over any prior imported management packs.

Following are steps required to delete said management packs:
1. Navigate to the Administration Space.
2. Select Management Packs.
3. Select Windows 2003 Cluster Management Monitoring, right-click and select Delete, click Yes.
4. Select Windows 2003 Cluster Management Library, right-click and select Delete, click Yes.
5. Select Windows Cluster Management Monitoring, right-click and select Delete, click Yes.
6. Select Windows Cluster Management Library, right-click and select Delete, click Yes.

Before you import the Windows Server 2003 Cluster Management Pack, please do following actions too:

· Import the Windows Server 2003 Base Operating System Management Pack.

· Enable the Agent Proxy on all agents which are installed on servers that are members of a cluster if it was not enabled already.

Based on OpsMgr 2007 SKU, this is quick reminder about dependencies:

· OpsMgr 2007 RTM (version 06.0.5000.0000):QFE needs to be applied and Microsoft.Windows.Cluster.Library management pack needs to be imported immediately after binaries on cluster nodes changed. This is required due to dependency on cluster user profile in the case action account has no access to cluster administration and profile needs to be manually populated to allow monitoring of MSCS as well as hot fix required for WMI event provider used with cluster infrastructure monitoring. (QFE is also included with released package)

· OpsMgr 2007 SP1 RC (version 06.0.6246.0000):No special requirements for runtime are required. But it is required to import Microsoft.Windows.Cluster.Library from QFE (again, it is also attached to web released package). This makes sure you can simply follow steps to download files and successfully import management packs.

· OpsMgr 2007 SP1 RTM (version 06.0.6278.0000):No special requirements are to be met. All referenced management packs are at their latest version. Simply follow steps to download management pack files and import all except Microsoft.Windows.Cluster.Library.

Continue Reading

WMI Encountered a problem and needed to close error

After installing the Dell MP you might start to see a bunch of WMI errors on your Dell Servers.

“Event ID: 1000; Faulting application wmiprvse.exe

This fix was suggested by Dell 3rd level Support.

The problem is caused by the Dell OpenManage Management Pack in SCOM. WMI throws these errors when SCOM queries WMI on Dell server. I have not seen any application issues due to the WMI errors.

These patches are not included in SP2 so if you are running SP2 you will still need the patches.

KB Article
http://support.microsoft.com/?kbid=933061

SUMMARY
A software update is available for Windows Management Instrumentation (WMI) in Microsoft Windows Server 2003. This update improves the stability of the WMI repository.

Windows Server 2003, x86-based versions
Download the WindowsServer2003-KB933061-x86-ENU.exe package now.

Windows Server 2003, x64-based versions
Download the WindowsServer2003.WindowsXP-KB933061-x64-ENU.exe package now.

Continue Reading