You are currently offline, waiting for your internet to reconnect

How To Track "Permission Denied" Errors on DLL Files

This article was previously published under Q286198
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
When you try to create a component or access a method, you may receive the following error message:
Run-time Error '70':Permission Denied
Or you may receive the following error message from Active Server Pages (ASP):
Error Type:
Server object, ASP 0178 (0x80070005)
The call to Server.CreateObject failed while checking permissions.
Access is denied to this object.
/Test/abort.asp, line 3
These errors mean that there are insufficient permissions to access a file.
To find the dynamic-link library (DLL) file on which the caller has insufficient permissions, you can trace all access to all files with the Filemon tool. Similarly, you can trace all calls that go to the registry with the Regmon tool. You can download both of these tools from the following Sysinternals location:

Steps to Capture Permission Issues

  1. Start Filemon. The tool immediately scrolls and sends a lot of information about which process is accessing which file. It also displays the results of those interactions.
  2. Reproduce the error, and click the magnifying glass on the toolbar to tell Filemon to stop logging.
  3. Save the results to a log file.
  4. In Microsoft Excel, open the log as a text file. In the wizard about how to convert the text file into a spreadsheet, click Finish.
  5. In Excel, on the Data menu, click Filter, and then click AutoFilter to filter the results.
  6. On the Results column, click Permission Denied.
In the Process column, you can see which process tried to access the file; in the Path column, you can see which file received the "Permission denied" error. You can reset the NTFS permissions on this file to resolve the problem.

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Article ID: 286198 - Last Review: 12/26/2006 07:00:56 - Revision: 1.2

  • Microsoft COM+ 1.0
  • Microsoft Transaction Services 2.0
  • kberrmsg kbhowto KB286198