- Get the error Info from "Event Viewer"
- Trace the error info in the registry.
- Resolve the security error using "COM Manager"
The first step would be to open up "Event Viewer" that can be found under administration tools on server 2003.
Navigate to the errors that are marked with the red icon and double-click on one to get all the error information.
This is the point where most people get frustrated due to the fact that the error information does not include the name of the application or component that is causing the error. Let us analyse what we do have:
- We know the error has to do with security due to the reference of the word "Permission" in the text.
- We know what permission is missing - "Local Activation"
- We know what account requires permission - "Network Service" in this case.
- We have the Class ID for the assembly causing the problem.
All we need to do now is convert the CLSID into a logical application name. To do this we need to access the registry by executing the command "regedit" from the command line.
Copy the CLSID from the error and do a find using the "Registry Editing" tool. Once you find a match to the CLSID, you will be given a PROGID (Program Identifier). This is the name of the application causing the error, in this case "IIS WAMREG admin Service".
The next step is to find this application using "COM Manager" that can be found under administrative tools in "Control Panel".
Collapse out the tree in component manager until you get to the "DCOM Config" section. Under this section you will find the application in question listed. Edit the properties of this application to fix the problem.
The error specified that the problem was related to "Security" and "Local Activation". Therefore we navigate to the "Security" tab and select the edit button under the "Launch and Activation" section.
Select the "Add User" button and add the "Network Service" to this ACL (Access Control List).