Home     Products      Support      Corporate     Sign In 
Support Knowledge Base, Article 1382
Product
All Products
Title
Troubleshooting permissions errors with Process Monitor
Problem
You receive some type of permissions error when running your application. The solution described below is how to troubleshoot the source of a permissions error. The actual permissions needed to resolve permissions issues will vary depending on the desired system configuration.

The specifically error being used for this example is:

Server object error 'ASP 0177 : 800401f3'
Server.CreateObject Failed
/SAFileUpSamples/uploadsamples/Simple/asp/formresp.asp, line 27
800401f3

However these concepts can be applied to most permission issues.

Solution

This tutorial is geared towards System Administrators. In this tutorial I will be troubleshooting a permissions error using Process Monitor (ProcMon). Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, registry and process/thread activity. The latest version of Process Monitor is available for download at http://technet.microsoft.com/en-us/sysinternals/bb896645

Step 1

Once Process Monitor is running make sure that Capture Events is checked.


Step 2

Recreate the error message. In my case it was attempting to upload a file using my FileUp application.

Step 3

After the event has been recreated while Process Monitor is running you can Uncheck capture event and review the log.

Step 4

When reviewing the log you will likely have thousands of entries. By clicking on the find icon which appears as binoculars or pressing the shortcut key Ctrl+F you can search for a keyword. In my case I am searching for Access Denied

My results appeared as below. I can see that the IIS worker process cannot access the HKCR\SoftArtisans.FileUp registry key.


From this example I can see that the w3wp.exe process does not have the correct permissions on the HKCR\SoftArtisans.FileUp registry key. By setting the correct permissions in the registry I was able to resolve the issue.

Created : 5/3/2011 1:34:28 PM (last modified : 5/3/2011 1:34:28 PM)
Rate this article!
Comments