FCS Fails to Install - Event ID 3013 Source: LoadPerf
- I have a small enviroment which has well over 100+ successful installations of Forefront client security.Currently I have a Windows 2003 Server - with WSUS deploying all FCS installtions to my clients.Upon installation on this server i recieve several error messages:Event Type: ErrorEvent Source: LoadPerfEvent Category: NoneEvent ID: 3009Date: 9/3/2009Time: 11:24:12 AMUser: N/AComputer:Description:Installing the performance counter strings for service MOM_Default (MOM_Default) failed. The Error code is the first DWORD in Data section.As well as -Event Type: ErrorEvent Source: MsiInstallerEvent Category: NoneEvent ID: 10005Date: 9/3/2009Time: 11:24:17 AMUser:Computer:Description:Product: Microsoft Operations Manager 2005 Agent -- Error 25211.Failed to install performance counters.. Error Code: -2147024864 (The process cannot access the file because it is being used by another process.).My best guess would be that a service\process is preventing MOM agent to install, primarily within Performance Monitor ..I've tried my best to research these errors on my own and couldnt come up with anything solid,Any suggestions ? Has anyone seen this before ?
Answers
Hi,
Thank you for your post.
According to your description, I understand that the problem you are experiencing is: Install mom agent on an client server, error occured with errorcode : -2147024864. If anything misunderstand, please let me know.
As far as I know, there are many reasons may cause this issue. Please perform the following steps to troubleshooting this issue:
1. Try to use a clen up tool and run that on the server to make sure all old settings is deleted. Also verify that there is no trace in the management server from your server. Then try to run the installation again.
http://www.microsoft.com/mom/downloads/2005/reskit/default.mspx
2. If you have a antivirus, try to disable it during installation and also stop SNMP service.
3.Please try to rebuild performance counters on the server
http://support.microsoft.com/kb/300956/en-us
If the issue still retains, a recommend way to determining which service will affect it is that to use Filemon during install process. Here is a example:
1. Download Filemon.exe and Handle.exe from Microsoft at
FileMon for Windows v7.04
http://www.microsoft.com/technet/sysinternals/utilities/filemon.mspxHandle v3.30
http://www.microsoft.com/technet/sysinternals/utilities/handle.mspx2. Start a Filemon trace and push the agent from the Management Server. Review the Filemon log and look for "SHARING". You should see something like below:
84267 9:58:47 AM msiexec.exe:5076 CREATE C:\WINDOWS\system32\perfc009.dat SHARING VIOLATION Options: Supersede Access: All
3. We know now that the file that is being locked in perfc009.dat.
4. Export the output to handle.txt. For example you would run "handle.exe > handle.txt" from a CMD line.
5. Look in handle.txt for the file noted in the SHARING VIOLATION in step 2. In case for example we saw the following:
OSRServer.exe pid: 4936 NT AUTHORITY\SYSTEM
2DC: File C:\WINDOWS\system32\perfc009.dat
2E4: File C:\WINDOWS\system32\perfh009.datThis told us that the process OSRServer.exe had a lock on perfh009.dat and perdc009.dat preventing the MOM agent from installing. We should disable it.
Hope it helps.
Regards
Nick Gu - MSFT- Marked As Answer byNick Gu - MSFTMSFT, ModeratorFriday, September 11, 2009 8:20 AM
All Replies
Hi,
Thank you for your post.
According to your description, I understand that the problem you are experiencing is: Install mom agent on an client server, error occured with errorcode : -2147024864. If anything misunderstand, please let me know.
As far as I know, there are many reasons may cause this issue. Please perform the following steps to troubleshooting this issue:
1. Try to use a clen up tool and run that on the server to make sure all old settings is deleted. Also verify that there is no trace in the management server from your server. Then try to run the installation again.
http://www.microsoft.com/mom/downloads/2005/reskit/default.mspx
2. If you have a antivirus, try to disable it during installation and also stop SNMP service.
3.Please try to rebuild performance counters on the server
http://support.microsoft.com/kb/300956/en-us
If the issue still retains, a recommend way to determining which service will affect it is that to use Filemon during install process. Here is a example:
1. Download Filemon.exe and Handle.exe from Microsoft at
FileMon for Windows v7.04
http://www.microsoft.com/technet/sysinternals/utilities/filemon.mspxHandle v3.30
http://www.microsoft.com/technet/sysinternals/utilities/handle.mspx2. Start a Filemon trace and push the agent from the Management Server. Review the Filemon log and look for "SHARING". You should see something like below:
84267 9:58:47 AM msiexec.exe:5076 CREATE C:\WINDOWS\system32\perfc009.dat SHARING VIOLATION Options: Supersede Access: All
3. We know now that the file that is being locked in perfc009.dat.
4. Export the output to handle.txt. For example you would run "handle.exe > handle.txt" from a CMD line.
5. Look in handle.txt for the file noted in the SHARING VIOLATION in step 2. In case for example we saw the following:
OSRServer.exe pid: 4936 NT AUTHORITY\SYSTEM
2DC: File C:\WINDOWS\system32\perfc009.dat
2E4: File C:\WINDOWS\system32\perfh009.datThis told us that the process OSRServer.exe had a lock on perfh009.dat and perdc009.dat preventing the MOM agent from installing. We should disable it.
Hope it helps.
Regards
Nick Gu - MSFT- Marked As Answer byNick Gu - MSFTMSFT, ModeratorFriday, September 11, 2009 8:20 AM
