Symptom 1: During the pre-requisite check you receive notification that ASP.net is not started but the service is running.

Symptom 2: During setup you receive the “srs server validation” error  

To fix this

• Of course confirm that ASP is installed. If it is then do the following.
• Open the command prompt go to

C:\windows\Microsoft.NET\Framework\v2.0.50727

• Run the following command

aspnet_regiis /i

Resolution is to fix WMI. And here is exactly how I did it.

Well almost exactly. You will need to send me an email for the files required to do this.

On effected server

1. copy mom_tracing.mof to any location on the server. I used c:\downloads

 2. open the command prompt and navigate to c:\downloads and
run the following command without the quotes.

 ”mofcomp mom_tracing.mof”

 This will most likely lead to an error looking for the EventTrace class in WMI which the mom_tracing.mof is dependent upon. (This can be verified by running wbemtest connecting to Root\WMI and doing a recursive Enum of the classes and looking for EventTrace as a class, if necessary).

To fix the error proceed to step 3

3. Copy the contents of the mof folder (email me for this folder) to c:\%SystemDirectory%\system32\wbem
4. Open command prompt and navigate to c:\%SystemDirectory%\system32\wbem
Run the following command without the quotes.

“For /f %s in (‘dir /b *.mof *.mfl’) do mofcomp %s”

Restart WMI services.

Install SCOM agent from file://scomserver/agent/i386

And that’s it. The entire process should take less then a few minutes.

Brad Hearn

Enterprise Server Analyst

http://bradstechblog.com/

The OpsMgr Connector could not connect to MSOMHSvc\rms01.local

haha, I have.

Using a domain account is not supported and will not allow you to start the service. But it will register a second servicePrincipalName to the domain account. If this happens the agents will no longer be able to communicate with the server. Or at least until the duplicate servicePrincipalName is removed.

I found this out during the test phase when I changed the service login account during trouble shooting the health service. (The original problem with the health service was that it would keep failing and stopping. The resolution was never found, and that was with an open Microsoft call. We reinstalled the server and that resolved it. However the servicePrincipalName was still messed up in active directory.)

The following is what I have documented and used to fix this.

Here is a clipping from another post (http://www2.wolzak.com/index.php?option=com_frontpage&Itemid=1) on this that I found.

To generate a list of accounts that the SPNs are registered to, run the following command at the command prompt.

1. From the domain controller, open a command prompt and then type the following string: ldifde -f domain.txt
2. Open the text file in Notepad and then search for the SPN that is reported in the event log. ServiceClass/host.domain.com (in this case look for MSOMHSvc/rms01.local)
3. Note the user accounts under which the SPN is located and the organizational unit the accounts reside in….the userPrincipalName should be located directly above the servicePrincipalName registration as in the example below.
userPrincipalName: useraccount@domain.com
servicePrincipalName: ServiceClass/host.domain.com

Use one of the following options to delete the account SPN registrations from the accounts that should not contain registrations to ServiceClass/host.domain.com. (i.e. Typically any accounts containing an SPN registration for SeriviceClass/host.domain.com that services are not explicitly starting with). Make sure you know which credentials you want to keep (in this case the system account or the domain administrator) and see to it that the service is running with the credentials you want to use. Delete the other one.

Using ADSIEdit

1. Add ADSIEdit to the MMC and bind to the domain using the Domain well known naming context.
2. Navigate to each user account you previously documented as having a duplicate SPN registration and right click the account and select properties.
3. Scroll through the list of attributes until you see servicePrincipalName, double click servicePrincipalName and remove the duplicate SPN registration and click on OK and exit ADSIEdit.

Using SetSPN

1. From the command prompt type the following command and hit enter.setspn -D ServiceClass/host.domain.com:Port AccountName

Make sure to test before performing this operation in a production environment.

Brad Hearn

Enterprise Server Analyst

http://bradstechblog.com/