March 2008 - Posts
I thought I had our SCOM reporting up and running but to my surprise, when I go to http://SCOMReportServer/Reports the other day, I got the below error message
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
A name was started with an invalid character. Error processing resource 'http://nytwopmp03/ReportS/'. Line 1, Position 2
<%@ Page language="c#" Codebehind="Home.aspx.cs" AutoEventWireup="false" Inherits="Microsoft.ReportingServices.UI.HomePag...
Again googling around and there are some users have the similar issues and they point to asp.net. But non of the solutions I got from the net solve my problem. So I contact MS support. They told me to check the report server app pool and make sure it is running and verify the ASP.Net version is 2.0.50727 and “allowed” in web service extension which all are correct. The below trick solve my problem:
open a command prompt
cd %systemroot%\microsoft.net\framework64\v2.0.50727
enter the following command
aspnet_regiis -u (this is a key step missing from my online search!)
enter the following command
aspnet_regiis -i
The other day when I work late night hours to setup our SharePoint testing enviroment. It was very late and I made a few mistake. When I try to delete the SSP and recreate it. To my unpleasant surprise, there are no way I can do this through our Central Administration interface.
After digging around and a few trial and errors – the below command get the job done!
stsadm –o deletessp –title “MOss Shared Service” -force
We have a SCOM 2007 environment and initially it was a one server (RMS, OpsDB)environment. We upgraded it to SP 1 recently. Now we are adding two more servers for reporting purpose. One for the Data Warehouse and the other is for reporting server.
I follow the design and deployment guide. But when I was trying to create the DW DB on the Data Warehouse Server, I run into the below error:
“the setup wizard was interrupted before Operations Manager 2007 could by installed”
I was able to create DW DB by using the Database Configuration Wizard – I thought I was OK there!
Database Configuration Wizard
Then when I tried to install the reporting server – I got this error:
“Invalid Microsoft Operations Manager Dw database version
setup found that the Microsoft operation manager database version on the specified database server is not the same as the current product version”
I was goggling around and couldn't find the solution. I have to call Microsoft Support and they quickly identified the problem.
It turns out when I was installing the reporting component, since our SCOM server is already upgraded to SP1. I think it would be logic to use SP1 media to install the reporting part. But since there is no official SP1 media out yet. I used the Evaluation SP1 media and thought if it asks, I can put in our license information. I WAS WRONG ON THAT! That’s why I got those “Invalid DW database version” errors. What I need to do is to use the SCOM RTM media to install the reporting components and then use the SP1 Upgrade media to upgrade the reporting servers to SP1. I did all that and now my reporting server is UP and RUNNING!
Another thing I would like to point out is that you may see some Microsoft documentation or blog saying that for SQL 2005, the DW DB can be SP2 but the reporting service has to be SP1.
SQL SP
This is no longer the case, I guess may be the SCOM SP1 fixed that. Now all my Ops DB, DW DB and reporting DB are all running SQL 2005 SP2
To set up the Data Warehouse database using the Database Configuration Wizard
|
1. Create a new directory on the database server.
2. Copy the file DBCreateWizard.exe from the following directories on the installation media:
\SupportTools\DBCreateWizard.exe
3. From a computer with the Operations Manager 2007 Operations Console installed, copy the following files to the directory you created on the database server:
· C:\Program Files\System Center Operations Manager 2007\ Microsoft.EnterpriseManagement.UI.ConsoleFramework.dll
· C:\Program Files\System Center Operations Manager 2007\ Microsoft.MOM.UI.Common.dll
· C:\Program Files\System Center Operations Manager 2007\ Microsoft.MOM.UI.Wrappers.dll
4. Double-click DBCreateWizard.exe to run the wizard.
5. On the Welcome page, click Next.
6. On the Database Information page, select to create a Data Warehouse Database.
7. Select the instance on which to install.
8. Specify a unique name or accept the default. It is recommended to accept the default.
Note
If you specify a custom name for the Data Warehouse database, be sure not to include a '-' character. The database installation will fail if a '-' character is included in the name.
1. Specify a database size.
2. Click Next.
Note
For a Data Warehouse, the installation skips to the Summary page.
3. Specify a domain security group which has the Operations Manager Administrators, and then click Next to continue.
4. On the Error Reporting page, choose to send error reports, and then click Next to continue.
5. Review the Summary page, and then click Finish. |
After I upgrade to SCOM SP1, everytime I restart SDK service, I got the below alert:
Alert: SDK SPN Not Registered
Source: XYZ.whatever.com
Path: XYZ.whatever.com
Last modified by: System
Last modified time: 3/4/2008 6:04:21 PM
Alert description: The System Center Operations Manager SDK service failed to register an SPN. A domain admin needs to add MSOMSdkSvc/XYZ and MSOMSdkSvc/XYZ.whatever.com to the servicePrincipalName of Domain\SDKaccount
The below link has the detailed explanation and fix. I follow the instruction and the alert is gone!
System Center Operations Manager SDK service failed to register an SPN
Thanks Kevin Holman!
I just upgrade our SCOM environment to SP1 the other day. I have followed the Operations Manager 2007 SP1 Upgrade Guide which is in the UpdateCDImage.
The whole upgrade process is rather smooth except when I was trying to take OperationsManager DB offline to make a backup, It is “In Progress” forever. I have to hard “kill” the process and then tried the below query
ALTER DATABASE [mydb] SET OFFLINE WITH ROLLBACK IMMEDIATE (The rollback immediately statement will force currently executing statements to rollback immediately)
I got an error message “ ALTER DATABASE failed because a lock could not be placed on database 'OperationsManager'. Try again later.”
After I stopped OpsMgr Config Service & OpsMgr SDK Service, I run the above query again – it worked imediately!
I then upgrade the agents using the Operations Console – In the administrtion pane, expand Device Management and then click Pending Management. In the pending Management pane, expand Type: Agent Require Update, select them all and Click Approve.
Most of our agents are upgraded successfully except two of our Blackberry Server and one Exchange (2000) Server. One Blackberry server was in “pending” reboot state. I don’t know if it is just a coincidence or not, a day later, the server stopped responding (Memory Leak?). We have to reboot the box which give me the opportunity to upgrade the agent. I still have WMI errors on the other two servers and I am waiting for a reboot opportunity and troubleshooting afterwards.
I also upgrade the Management Packs by importing the management packs in the UpdateCDImage. This part is also very cool. If you import a management with out importing the MP it depends on, the import process will fail. If you have an old version of the same MP, you will getting a message which tells the old MP (version number) will be replaced by the new MP (version number) and wait for your confirmation.
Now a couple of days after the upgrade. We get significantly less alerts on this one – “Alert: Script or Executable Failed to run” which we had a lot before the upgrade. But we do get a lot of alerts on this one “Alert: Performance Module could not find a performance counter” which I disabled for now.
All in all, this is a very smooth upgrade and I have to say Microsoft have done a great job to make our life easier!