System Center Operations Manager by Jonathan Hambrook

August 27, 2007

Cannot save report subscription in SCOM

Filed under: Errors, Microsoft, SCOM 2007 — opsmgr @ 6:36 pm

You get the following error after you fill in the Reports Scheduler Wizard.

Cannot save report subscription 

Date: 17/07/2007 10:03:33
Application: System Center Operations Manager 2007
Application Version: 6.0.5000.0
Severity: Error
Message: Cannot save report subscription.
System.Web.Services.Protocols.SoapException: The value provided for the report parameter ‘StartDate_BaseValue’ is not valid for its type. —> The value provided for the report parameter ‘StartDate_BaseValue’ is not valid for its type. —> The value provided for the report parameter ‘StartDate_BaseValue’ is not valid for its type.
  at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
  at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
  at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.ReportingService.ReportingService2005.CreateSubscription(String Report, ExtensionSettings ExtensionSettings, String Description, String EventType, String MatchData, ParameterValue[] Parameters)
  at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.ManagementGroupReporting.SetSubscription(ManagementGroupReport report, ManagementGroupReportSubscription subscription, String description, String deliveryMethod, IDictionary`2 deliveryOptions, ScheduleDefinition schedule, IDictionary`2 reportParameters)
  at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.ManagementGroupReporting.CreateSubscription(ManagementGroupReport report, String description, String deliveryMethod, IDictionary`2 deliveryOptions, ScheduleDefinition schedule, IDictionary`2 reportParameters)
  at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.Wizards.Schedule.ReportSubscriptionProgressPage.BackgroundWorkerDoWork(Object sender, DoWorkEventArgs e)

FIX:

There is a hotfix release and available from Microsoft, request MS for KB 938507. Its not release for public viewing so you will need to call MS up.

This HF needs to be installed on any machine with the Operations Manager Console on it.

July 12, 2007

Error: Replication Monitoring – Access Denied

Filed under: Errors, Microsoft, SCOM 2007 — opsmgr @ 5:38 pm

So you have followed the Active Directory Management Pack Guide for Operations Manager 2007 to the letter and you get Access Denied errors. You also get the same error in Event Veiwer as seen in the Screen Shot:
AD Replication Monitoring Error

Here are some things you will also need to check above an beyound the supplied documentation.

Container Permissions
1. On page 9 of the AD MP Guide it mentions that you need to create the MomLatencyMonitors container. I have found that in a heavely locked down environment you will need to add Read/Write permission to this container. (DC=Domain, DC=com). The permission need to be of the account specified under the ‘Configure an Account for Replication Monitoring’ of Page 9 of the AD MP Guide.

2. Also you may like to check the ForestDNSZones as well. This can be done via ADSI Edit by connecting to DC=ForestDNSZones, DC=Domain, DC=com. You will see MOMLatencyMonitors, right click and select security.

Agent Permissions
If you deployed all your agents using Local as per the following screenshot:
Agent Install Local System
You will also find you will have some issues as the Health Service will start with Local System, which is fine but the Agent Action Account will also be specified as account to do all the processing by that agent. This is fine for all other servers if you require it but you will need do the following on the Domain Controllers

1. Add/Remove Programs
2. Select the System Center Operations Manager Agent and click Change
3. Select Modify
4. Select Modify Management Group
5. Click Next on the next 2 screens until you get to the Ready to Install screen
6. Click Back
7. Specify a Domain Account. (See the deployment Guide page 31 for the permission of the Agent Action Account)
8. Click Next then Install

By doing the above steps, The Service will still start with the Local System Account but will do all its proccessing using the Domain Agent Action Account. You should now be able to restart the Health Service and your permissions issues should go away.

I do however recommend that all Agents be deployed using a domain Agent Action Account.

July 3, 2007

Error: Access to the registry key ‘Global’ is denied.

Filed under: Errors, Issues, Microsoft, SCOM 2007 — opsmgr @ 9:01 pm

I noticed this Error in a few blogs and thought I would have a crack at it and I was able to recreate it in my lab.

Access to registry key Global is denied

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[UnauthorizedAccessException: Access to the registry key 'Global' is denied.]
Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str) +2116595
Microsoft.Win32.RegistryKey.InternalGetValue(String name, Object defaultValue, Boolean doNotExpand, Boolean checkSecurity) +2779509
Microsoft.Win32.RegistryKey.GetValue(String name) +29
System.Diagnostics.PerformanceMonitor.GetData(String item) +96
System.Diagnostics.PerformanceCounterLib.GetPerformanceData(String item) +147
System.Diagnostics.PerformanceCounterLib.get_CategoryTable() +82
System.Diagnostics.PerformanceCounterLib.CategoryExists(String machine, String category) +65
System.Diagnostics.PerformanceCounterCategory.Exists(String categoryName, String machineName) +125
System.Diagnostics.PerformanceCounterCategory.Exists(String categoryName) +9
Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.Counters.BuildPerformanceCounter(DalCounter counterName, String instanceName) +302
Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.Counters..ctor() +197
Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.DataAbstractionFactory..ctor() +24
Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.DataAbstractionFactory..cctor() +20[TypeInitializationException: The type initializer for 'Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.DataAbstractionFactory' threw an exception.]
Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.DataAbstractionFactory.GetInstance(IDataAbstractionBuilder builder) +0
Microsoft.EnterpriseManagement.OperationsManager.WebConsole.WebDalWrapper.get_OpsSdkWrapper() +37
BaseWebConsolePage.get_OpsSdkWrapper() +210
login.Page_Unload(Object sender, EventArgs e) +22

You will also get this error in the Event log on the Web Console server (Click to view full size):
Event 10

This is what I did to create the Issue and further down is the workaround which is a common fix for this issue in some other Blogs and also with other errors Microsoft have in their Knowledge Base that arn’t specific to SCOM.

To set the scene this is what I set out to achive. I wanted to create a New Monitoring Diagram View to display a couple of intranet sites that I want to monitor from all our national offices and unlike the Web Application State view I only wanted to see the Websites status ie: Health or Critical etc.

I order to do this I would have to do the following, create new Groups, new Monitor, new Management Pack, new View and to then restrict access to only show the one new View in the Web Console for a few people.

1. Created the Management Pack

2. Created the Web Application monitor for the sites

3. Created a Group and then added 2 other Groups as Child Groups. (One for each Application and added the appropriate Web Application to each group)

4. Created the new Monitor to report the status of the 2 Child Groups

5. Created the Custom Diagram View showing the Primary Group and the 2 Child Group.

6. Under Adminitriation I created a new Read-Only Operator, New user Role.

7. Added the Domain Users (Same Domain as SCOM is in) that would have access to this group and also specified that all they could see was the 3 new groups I had created and the new view as well as the Web Applications State view. (Now this is where I think I need to look further to see whats happening.)

8. I then accessed the Web Console and got the above error.

9. Applied the resolution: Added all the users from the new ‘User Role’ to the local Performance Monitor Users group on the server that runs the Web Console. (I however didnt add them to the local Users group as this is inherited by the Domain Users group. If this isn’t the case for you then you should make sure those users are also added to this group)

10. Closed all IE browser and Performed an IISReset (run from cmd)

11. Logged back on and EVERYTHING was working great. Here is what I saw for reference.
Monitoring View

June 28, 2007

Web Console Error: “Server Error in ‘/’ Application – Requested value ‘UrlViewType’ was not found.”

Filed under: Errors, Microsoft, SCOM 2007 — opsmgr @ 9:19 pm

SYMPTOMS

You get the following error in the SCOM Web Console:

Server Error in ‘/’ Application – Requested value ‘UrlViewType’ was not found.

CAUSE 

This is due to the fact that Microsoft doesn’t support Web Page Views in the web console.

RESOLUTION

Remove the Web Page View or don’t use the Web Console.
 I believe MS are working on a fix for this.

June 19, 2007

SRS Server Validation Error – (407) Proxy Authentication Required

Filed under: Errors, Issues, Microsoft, SCOM 2007 — opsmgr @ 3:12 pm

ISSUE:

If like me, you are behind a proxy and you use a proxy.pac file to athenticate to the Internet, and you have this set in IE. You may get an SRS Server Validation Error. To find out if this is the case use the following command line to log the instalation of the SCOM Reporting MSI:

msiexec /i reporting2007.msi /l*v c:\reportinglog.txt

Look at the reportinglog.txt file and you will see the following:

Action start 12:25:05: _ValidateSRSWebSiteBindingsCA_Wizard.
MSI (c) (58:44) [12:25:05:568]: Invoking remote custom action. DLL: C:\DOCUME~1\itsjrh\LOCALS~1\Temp\MSI2C2.tmp, Entrypoint: ValidateSRSWebSiteBindingsCA
MSI (c) (58!E4) [12:25:06:146]: PROPERTY CHANGE: Adding REPORT_SERVER_FULL_HTTP_PATH_VALID property. Its value is ‘0’.
MSI (c) (58!E4) [12:25:12:787]: PROPERTY CHANGE: Adding FailedMsgProperty property. Its value is ‘CheckHttpAddressResponse: Failed Status Code of The remote server returned an error: (407) Proxy Authentication Required.’.

RESOLUTION:

Remove all proxy setting from IE and re-run Reporting installation.

May 17, 2007

Error 0x8004005: Unspecified Error

Filed under: Errors, Microsoft, SCOM 2007 — opsmgr @ 2:36 pm

SYMPTOMS

You deploy an agent from the Management Server and in the pop-up deployment windows its listed as Successful however the server remains in Pending Management listed as ‘Install in Progress’.

The OpsMgr Health service fails to start and returns the following error: Error 0x8004005: Unspecified Error

CAUSE

This is caused by the Management Group changing and no longer being contactable but with the agent still being deployed and you try to install over the top into a new Management Group.

You will see the following error when you try to start the OpsMgr Health service:

Error 0×80004005: Unspecified error

You will also see the following error listed in the Event Viewer of the destination server:

Event Viewer Error 7023

If you the ablity to run a TraceLogSM and get it analised by Microsoft you will see a log similar to bellow. Not the hightlighted sections show the domain, service account and Management Group. If any of there are incorrect then you have found the issue.

You will need to run the TraceLogSM with the follow parameters:
TraceLogSM -start HSCORE -f hscore.etl -b 8 -ft 30 -guid #417B7AE0-9B8F-4E3F-8FCA-19C706EFF3D4 -flag 0xF -cir 100

To stop use: TraceLogSM -x

Send the file hscore.etl to Microsft for analysis.

67     HealthServiceCommon  23900  8856   2      0      05\17\2007-11:04:12:399    Logging informational event with args MGROUP
68     SecureStorageManager 23900  8856   2      0      05\17\2007-11:04:12:430    SSRef 63745834-3e54-936c-1b47-2d632054a177 resolves to 00BD5E70CBE8C70C8ABA7F843EB0BB42BA1920A05C00000000000000000000000000000000000000 : 0(ERROR_SUCCESS)
69     SecureStorageManager 23900  8856   2      0      05\17\2007-11:04:12:446    Account QBEAU\SCOM_AAA logged on : 1(ERROR_INVALID_FUNCTION)
70     SecureStorageManager 23900  8856   2      0      05\17\2007-11:04:12:446    Unable to create logon token : 1(ERROR_INVALID_FUNCTION)
71     SecureStorageManager 23900  8856   2      0      05\17\2007-11:04:12:446    Unable to log on user : 1(ERROR_INVALID_FUNCTION)
72     SecureStorageManager 23900  8856   2      0      05\17\2007-11:04:12:446    Unable to log on account : 1(ERROR_INVALID_FUNCTION)
73     SecureStorageManager 23900  8856   2      0      05\17\2007-11:04:12:446    Unable to retrieve the action account reference : 1(ERROR_INVALID_FUNCTION)
74     SecureStorageManager 23900  8856   2      0      05\17\2007-11:04:12:446    Unable to add store to store hashtable : 1
75     ConnectorManager     23900  8856   2      0      05\17\2007-11:04:12:446    Secure Storage Manager failed during MG notification : -2147467259(E_FAIL)
76     ConnectorManager     23900  8856   2      0      05\17\2007-11:04:12:446    Unable to inform components about management groups : -2147467259(E_FAIL)
77     HealthServiceExecutive     23900  8856   2      0      05\17\2007-11:04:12:446    Start of 1 manager failed with code -2147467259(E_FAIL).
78     HealthServiceExecutive     23900  8856   2      0      05\17\2007-11:04:12:446    ManagerStartup failed with code -2147467259(E_FAIL).
79     HealthServiceExecutive     23900  8856   2      0      05\17\2007-11:04:12:446       ServiceInitialization failed with code -2147467259(E_FAIL).
80     HealthServiceExecutive     23900  8856   2      0      05\17\2007-11:04:12:446    Health service is stopping.
81     HealthServiceCommon  23900  8856   1      0      05\17\2007-11:04:12:446    “Logging success event with args DOMAIN1, SCOM_AAA, MGROUP
82     HealthServiceHost    23900  22684  1      0      05\17\2007-11:04:12:868    HealthService.exe exiting.
83     HealthServiceExecutive     23900  8856   2      0      05\17\2007-11:04:12:868    Health service entered the stopped state.
84     HealthServiceExecutive     23900  8856   2      0      05\17\2007-11:04:12:868    Start failed with code -2147467259(E_FAIL).
85     ConnectorManager     23900  15272  3      0      05\17\2007-11:04:12:868    GetHealthStatus called after service shutdown.
86     ConnectorManager     23900  7008   0             05\17\2007-11:04:12:868    OnLocalDataAvailable called after service shutdown.
87     ConnectorManager     23900  7008   0             05\17\2007-11:04:12:868    GetHealthStatus called after service shutdown.

RESOLUTION

1. Manually uninstall the agent from the destination server.
2. Using regedit confirm that the following registry entry doesn’t exist:
HKLM\software\microsoft\microsoft operations manager\3.0\Agent Management Groups\%ManagementGroup%
3. Deploy the agent again either via the Management Server or Manually

May 14, 2007

Recieve Error -2147217900 when installing SCOM RMS

Filed under: Errors, Microsoft, SCOM 2007 — opsmgr @ 5:02 pm

This error is an access error, its created when the SDK user account does not have write access to the SCOM database.

May 10, 2007

SRS Server Validation Error

Filed under: Errors, Microsoft, SCOM 2007 — opsmgr @ 10:12 pm

If you receive the error: SRS Server Validation Error while installing SCOM Reporting, dont forget you need to Configure Reporting Server first.

To do this you need to go START -> All Programs -> Microsoft SQL Server 2005 -> Configuration Tools -> Reporing Services Configuration. Then on each of the Items that have a Red X or Yellow ! select them and configure them accordingly.

If you see any grey items this means that they cant be validated and even though you have configured another item it could be incorrect. The most common is the Initialisation option, if this is grey then you probably authentication.

SCOM Agents fail to install – Error: 80070643 and agentinstall.log error of 0x80070422

Filed under: Errors, Microsoft, SCOM 2007 — opsmgr @ 8:53 pm

You get a display error of 80070643

The problem is caused by a bug during the install, with the MSI custom action when it tries to register the agent for receiving updates via Microsoft Update. If the Windows Update/Automatic Update service is disabled install will fail.
This issue is bugged with Microsoft  and will be fixed in the future so that the setup will detect this situation and ignore the failure and continue with the install. Unfortunately the only option at this point as a workaround will be to enable Windows Update/Automatic Update on the machine for the purpose of the install.

Bellow is the extracts from the agentinstall.log and momagentmgmt.log

agentinstall.log
MSI (s) (D0:C4) [00:46:55:547]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI150D.tmp, Entrypoint: CanRegisterMU
Action start 0:46:55: _CanRegisterMU.80B659D9_F758_4E7D_B4FA_E53FC737DCC9.
CanRegisterMU: WU version is greater than 5.8.0.2469so we can proceed further.
CanRegisterMU: get_Services() failed. Error Code: 0x80070422.
MSI (s) (D0:98) [00:46:55:829]: Machine policy value ‘DisableRollback’ is 0
MSI (s) (D0:98) [00:46:55:829]: Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 0:46:55: _CanRegisterMU.80B659D9_F758_4E7D_B4FA_E53FC737DCC9.
Return value 3.
MSI (s) (D0:98) [00:46:55:829]: Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (D0:98) [00:46:55:829]: No System Restore sequence number for this installation.
MSI (s) (D0:98) [00:46:55:829]: Unlocking ServerAction ended 0:46:55: INSTALL. Return value 3.

momagentmgmt.log
12:46:42 AM : CServiceModule::SetServiceStatus : State: 4, Error: 0
12:46:43 AM : CMOMAgentFunctions::GetPatches : Entering
12:46:43 AM : CMOMAgentFunctions::GetPatches : MsiGetProductCode failed HResult: 80070647 

Error 0x80004005: Unspecified error when installing SCOM Agent

Filed under: Errors, Microsoft, SCOM 2007 — opsmgr @ 8:38 pm

You get the following error when installing the SCOM Agent on a server.

Error 0×80004005: Unspecified error

I have had this issue on Citrix Servers only and at the moment have no fix for this. I have heard of the same error occurring on servers running Microsoft Virtual Server and the fix for this is to stop the VM service, manually uninstall the agent and then re-deploy.

The Debug output from the ‘agentlog’ file folder should look like this:
00000244 137.91078186 [15044] CAStartServices: CAStartServices was passed. HealthService
00000246 137.91197205 [15044] CAStartServices: Attempting to start service. HealthService
00000248 199.14978027 [15044] WaitForServiceState: Failed to get service state within time limits. Error Code: 0x80070102.
00000250 199.15072632 [15044] CAStartServices: WaitForServiceState failed for start request. Error Code: 0x80070102.

HealthService 0x80070102 ERROR_SERVICE_DISABLED – The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Error 21256 while installing Operation Manager 2007 on a SQL 2005 cluster

Filed under: Errors, Microsoft, SCOM 2007 — opsmgr @ 8:15 am

Cause
——-
SQL cluster dependencies was missing in cluster node

Resolution
=======
Installing MOM 2007 need to have dependencies criteria met.

In my case disk dependencies are not there so added the disk to the SQL Service Dependency list and OpsMgr 2007 installation went successful.

The install was failing due to a dependency missing on the SQL Service in the Cluster group. In cluster administrator I took the SQL Group offline and then clicked on properties of SQL server, then the dependencies tab and checked whether all disks are listed here.

Only Network name was there as I has added a new SAN disk to the group for the Data Warehouse database.

Now for SQL Server we should have minimum of two dependencies
1. Disk Physical Disk
2. SQL Network name (IP address)

Create a free website or blog at WordPress.com.