You are browsing the archive for Troubleshooting.

SCE 2007: Agent deployment issues

6:55 pm in Uncategorized by mikeresseler

Hey All,

Today I was with a customer and they told me that the system administrators weren’t able to deploy an agent to a certain workstation.  This workstation was just deployed clean with MDT.

The error they got is the following:

The MOM Server could not start the MOMAgentInstaller service on computer <computername> in time

Also, I received error 80070102.

Since I never saw this error, and the logs didn’t really told me a lot, except somewhere in the installation log file that the firewall exceptions couldn’t be made.

This was quite strange since I deployed the firewall exceptions through GPO (it is not only for SCE so I used 1 GPO for all firewall exceptions).

So I started surfing on the net for solutions.

Not much info there, but finally I came across a blog post from Kevin Holman

http://blogs.technet.com/kevinholman/archive/2009/01/27/console-based-agent-deployment-troubleshooting-table.aspx

Ok, since this was one isolated case, I could have gone to the user and installed it manually, as many people advised on the internet, but since I’m quite lazy I didn’t feel like it.

According to Kevin, and I quote:

Sometimes – the Windows Firewall service – even if disabled – will have a stuck rule. Run: (netsh advfirewall firewall delete rule name=”MOM Agent Installer Service”)

So I fired up psexec from my workstation and checked if this could be true.  And yes, there was a rule that called Mom Agent Installer Service.

Since the program wasn’t installed, it was not necessary so I used the command to delete the rule.

Tried the remote installation again, and it worked.

Thanks Kevin :-) I didn’t had to leave my chair today

Cheers,

Mike

System Center Service Manager 2010: Error when registering the Datawarehouse

4:57 pm in Uncategorized by mikeresseler

While registering a Datawarehouse with Service Manager 2010 I got the following error in the eventviewer of the Datawarehouse server…

A module of type “Microsoft.SystemCenter.Orchestration.Module.WorkflowWorkItemModule” reported an exception System.FormatException: String was not recognized as a valid DateTime.
   at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
   at System.DateTime.Parse(String s, IFormatProvider provider)
   at Microsoft.SystemCenter.Orchestration.WorkItem.ShredReader(XmlReader wiInstance)
   at Microsoft.SystemCenter.Orchestration.WorkItem..ctor(XmlReader wiInstance)
   at Microsoft.SystemCenter.Orchestration.WorkItem.GetWorkItem(String processCategory, String process)
   at Microsoft.SystemCenter.Orchestration.Module.WorkflowWorkItemModule.PollForNextWorkItemItem()
   at Microsoft.SystemCenter.Orchestration.Module.WorkflowWorkItemModule.OnDataItem(DataItemBase dataItem, DataItemAcknowledgementCallback acknowledgedCallback, Object acknowledgedState, DataItemProcessingCompleteCallback completionCallback, Object completionState) which was running as part of rule “WorkflowOrchestration.DeploymentRule” running for instance “Deployment Workflow Target” with id:”{0B09E978-69C6-709F-5D5E-B03C5477393C}” in management group “xxxxxx”.

The problem here was that the system locale from the service account used wasn’t set to English-US

After that change (and rebooting the server) the job succeeded

Cheers,

Mike

System Center Data Protection Manager 2007 SP1: Errors

8:36 pm in Uncategorized by mikeresseler

Hey All,

Last week I had a strange error with a customer.  Here’s the situation:

One primary DPM server with quite a lot of Protection groups and protected servers that handled the disk to disk backup.  A secondary DPM server that did the backup to tape and of course the backup off the first DPM server.

All backups on the first DPM server went most of the times without any problem, and if there was a problem it could be solved with a consistency check or a rerun of the failed job.

However, everything on the second server failed completely. 

After investigation, I’ve noticed that many times the DPMRA service crashed on the primary server each time the backup server was doing a backup of the first.

I’ve read log files, event viewers but every error described on newsgroups and blog posts were about DPM servers that didn’t had the latest hotfix rollup.  This server and the secondary server however had all the hotfixes installed till date.

So because I couldn’t figure it out, I decided to log a call together with the customer.  Because I am not often with that customer I let him handle it but requested to forward me the steps taken by Microsoft support and hopefully the solution. 

After one week, they found the solution together with the Microsoft engineer.

Just as extra information, here is the error they got on the secondary server

Error Messages: The protection agent on primaryserver.FQDN was temporarily unable to respond because it was in an unexpected state. (ID 60 Details: Internal error code: 0x809909B0) followed by DPM failed to communicate with the protection agent on primaryserver.FQDN because the agent is not responding. (ID 43 Details: Internal error code: 0x8099090E)

So here are the steps taken and the solution.

1) They needed to run an MPS report as described on

http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-88B7-F9C79B7306C0&displaylang=en

2) They needed to run the following command (run as administrator!)

MOUNTVOL >c:\mountvol.txt

The engineers from Microsoft quickly viewed the problem

As you can see in the following exctraction out of the mountvol.txt file

\\?\Volume{8639bea9-80c6-11de-a621-0015179ff253}\

        Q:\Program Files\Microsoft DPM\DPM\Volumes\Replica\servername\MSDEWriter\naamdatabase

        D:\Program Files\Microsoft DPM\DPM\Volumes\Replica\servername\MSDEWriter\naamdatabase

\\?\Volume{32c0e517-64c6-11de-9f82-0015179ff253}\

Q:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Servername\Non VSS Datasource Writer\Computer\SystemState\SystemState\

        D:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Servername\Non VSS Datasource Writer\Computer\SystemState\SystemState\

\\?\Volume{1ea729a2-7c50-11de-bff1-0015179ff253}\

        Q:\Program Files\Microsoft DPM\DPM\Volumes\DiffArea\Servername\File System\D-2a56f4ae-783c-11de-8b69-005056ac1ad1\

        D:\Program Files\Microsoft DPM\DPM\Volumes\DiffArea\Servername\File System\D-2a56f4ae-783c-11de-8b69-005056ac1ad1\

The whole file was full with duplicate paths to the same volume, although this was not seen in a normal explorer

This happened because they once changed the location of the volumes.

Now the customer can use the mountvol command (with /d to remove the duplicates one by one, or take the the old disk offline and use the /R for all in once) to clear out the duplicate paths.

That solved the case

Cheers,

Mike

System Center Service Manager 2010: Error when installing the Compliance and Risk Process Management Pack

2:49 pm in Uncategorized by mikeresseler

Hey All,

When I tried to install the Compliance and Risk Process Management Pack, I got following errors:

Output:
G:\Sources\Compliance and Risk Process Management Pack (Beta)\ComplianceAndRiskProcessMPBeta\Setup\Microsoft.ServiceManager.GRC.mpb


G:\Sources\Compliance and Risk Process Management Pack (Beta)\ComplianceAndRiskProcessMPBeta\Setup\Microsoft.ServiceManager.GRC.DocumentManagament.mpb
G:\Sources\Compliance and Risk Process Management Pack (Beta)\ComplianceAndRiskProcessMPBeta\Setup\Microsoft.ServiceManager.GRC.ControlManagement.mpb


Error:
The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection.The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.

After searching on the web, and even posting a question on the system center service manager forum, I found the answer.

Many problems seem to arrive if your servers locale is different from en-us.  After changing that on my servers, the installation went smoothly.

Cheers,

Mike

Newly Released Cluster Management Pack

4:16 pm in Uncategorized by mikeresseler

Hey All,

If you were planning on installing the newly released cluster management pack, you want to read this post first from the operations manager team: http://blogs.technet.com/momteam/archive/2009/02/27/two-issues-with-the-recently-released-cluster-management-pack.aspx

 

Cheers,

Mike

Update on the withdrawn QFE (957123)

12:14 pm in Uncategorized by mikeresseler

Hey All,

The operations manager team blog has released some extra information about this problem from this week.  If you had installed it, please read this to fix the issue:

http://blogs.technet.com/momteam/archive/2009/02/25/problem-with-the-iis-modules-qfe-957123.aspx

Cheers,

Mike

SCCM: Troubleshooting Guide for Deploying Intel vPro Technology with MS SCCM 2007

11:00 am in Uncategorized by mikeresseler

Hey All,

Received from Steve Davies from Intel

For those who need help troubleshooting Intel(R) vPro with Microsoft(R) SCCM, the first revision of the Deploying Intel vPro Technology and Microsoft System Center Configuration Manager Troubleshooting Guide is now publically available on the Intel vPro Expert Center at http://communities.intel.com/thread/2988

It assumes familiarity with normal Microsoft configuration tools such as Microsoft Management Console (MMC), and gathers together tips that have been successfully used in deployments in multiple geographies over a 7-month period

The guide can be used as a detailed aide-memoire when planning for a deployment and/or can be used to systematically validate and debug deployment projects

There will be further public revisions over time and an up-to-the-minute internal version will also be maintained

Constructive feedback or new tips are always welcome

For all of you who are working with the vPro Technology and SCCM 2007, this is a must-have guide in your administrators library.

Cheers,

Mike

Scheduled reports, Link does not work

1:00 pm in Uncategorized by mikeresseler

I’m working for the moment with a client and this client wanted me to create very, very, very long reports.  They wanted it scheduled each month so that one of their people can print out the report, take a coffee and can start analyzing the report. 

So I created the reports, published them and scheduled them.  A few days later, the client called me and said that the reports are ok, but the link that came with the reports showed following error when clicking on it:

image

So I started to search why this problem occurred.  After quite a while of reading logs and searching the web, I crossed this knowledge base article form Microsoft:

http://support.microsoft.com/kb/949454

Error message when you try to open a report from a link in the scheduled report e-mail notification in System Center Operations Manager 2007: "An internal error occurred on the report server"

SYMPTOMS

In Microsoft System Center Operations Manager 2007, when you try to open a repor…

In Microsoft System Center Operations Manager 2007, when you try to open a report from a link in the scheduled report e-mail notification, you receive the following error message:

Reporting Services Error
—————————————
An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help
Object reference not set to an instance of an object.

CAUSE

If the scheduled report that is received through e-mail has more than one chart,…

If the scheduled report that is received through e-mail has more than one chart, the original URL for the report exceeds the default value of 1,500 for the StoredParametersThreshold parameter. Therefore, Microsoft SQL Server Reporting Services uses the value of the StoredParametersID parameter to replace the whole parameter value list.
However, the shortened URL is not the correct URL. Additionally, because the link does not contain the necessary parameter, the link does not work. The link returns an internal error in Windows Internet Explorer.
The following URLs are examples of the original URL and of the shortened URL.
The original URL for the report contains all the parameters, as follows:

http://Servername/reportserver?%2fMicrosoft.SystemCenter.DataWarehouse>.Report.Library%2fMicrosoft.SystemCenter.DataWarehouse.Report.Alert&Start Date_BaseValue=2008-01-09T13%3a44%3a00&ObjectList=%3cData%3e%3cObjects%3e%3cObject+Use%3d%22Containment%22%3e374%3c%2fObject%3e%3c%2fObjects%3e% 3c%2fData%3e&EndDate_BaseValue=2008-01-09T13%3a44%3a00&Severity=0&Severity=1&Severity=2&EndDate_OffsetType=None&StartDate_OffsetValue=0&StartDat e_OffsetType=None&EndDate_OffsetValue=0&TimeZone=E001000000000000C4FFFFFF00000B0000000100020000000000000000000300000002000200000000000000%7cPaci fic+Standard+Time&StartDate_BaseType=Sunday&Priority=0&Priority=1&Priority=2&Interactive=False&EndDate_BaseType=Today&TimeZoneName=(GMT-08%3a00) +Pacific+Time+(US+%26+Canada)&ManagementGroupId=95a34c84-2de7-3224-1315-ce740d173598&SiteName%3aisnull=True&rs%3aParameterLanguage=en-US

The shortened URL in the e-mail notification is as follows:

http://Servername/reportserver?%2fMicrosoft.SystemCenter.DataWarehouse.Report.Library%2fMicrosoft.SystemCenter.DataWarehouse.Report.Performance &rs%3aStoredParametersID=ssnyvd453xhqvm453vkz5u45&rs%3aParameterLanguage=en-US

RESOLUTION

To resolve this problem, separate the charts in the report. Use only one chart i…

To resolve this problem, separate the charts in the report. Use only one chart in a report. This step reduces the length of the URL. Then, the URL works correctly.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that ar…

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

 

Hmm, apparantly a bug in the product.  Hopefully this will be resolved in R2

Hyper-V Host Performance issues

3:01 pm in Uncategorized by mikeresseler

I know, it has nothing to do with operations manager, but a colleague of mine gave me the following information and I think it is quite interesting:

Problem: Hyper-V Windows 2008 Core (Datacenter edition).  When to many virtual systems are on the host machine, and the host or hosts are clustered, the minimum limit of memory for the host that you can define in System Center Virtual Machine Manager does not seem to be respected.

Solution: A Microsoft engineer told us to put the memory limit straight into the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization
REG_DWORD
RootMemoryReserve

Default value: 20(h) or 32(d) (Megabytes)
Maximum value: 400(h) or 1024(d) (i.e. 1GB)

The parent partition memory reserve feature may be disabled by setting the RootMemoryReserve value to 0.
The server must be restarted for this setting to take effect.

Cheers