5

Question is in the title. Has something to do with Sharepoint, but a little bit of searching on my part didn't turn up a good answer.

Alex Angas
  • 2,007
  • 2
  • 26
  • 37
Boden
  • 4,948
  • 12
  • 48
  • 70

2 Answers2

6

Boden,

The IIS WAMREG admin COM+ service component that you're referring to is part of IIS web application manager (WAM) functionality. Basically, WAM allows IIS to work with processes that it doesn't specifically host itself but with which it needs to interact (or even start). WAM provides the interprocess communication (IPC) mechanism between IIS-hosted processes and those that are not hosted by IIS.

There isn't a whole lot of documentation on it readily available, but you can at least see a glossary mention here:

http://msdn.microsoft.com/en-us/library/ms524469.aspx#web_application_manager

I hope this helps!

Sean P. McDonough
  • 786
  • 4
  • 6
1

The typical reason people care about this in relation to SharPoint is that they start seeing errors in their Event Log relating to the IIS WAMREG admin component. Here is the KB article detailing this: http://support.microsoft.com/kb/920783

The errors do not cause any problems with the functionality of SharePoint, and are basically a nuisance.

MattB
  • 11,124
  • 1
  • 29
  • 36
  • Yeah, that's what was going on for me. It's hard to "safely ignore" thirty error messages in a row recurring throughout the day. Made the logs rather ugly :) – Boden Aug 06 '09 at 15:59
  • The KB article does have a "fix" ... If you want to prevent the event ID error messages from being logged in the System log, use the Component Services snap-in to enable the Local Activation permission to the IIS Wamreg Admin Service for the domain user account that you specified as the Windows SharePoint Services 3.0 service account. To do this, follow these steps ... – SteveC Dec 30 '10 at 11:44