"Access Denied to this Object" Error on Windows 2000

Problem:

The following error appears when you are using TimeForce on Windows 2000:

"Server object, ASP 0178 (0x800A0005) The call to Server.CreateObject failed while checking permissions.  Access is denied to this object."

Solution 1: (from www.microsoft.com):

  • For debugging purposes, configure the Application Protection of Virtual Directory where the ASP page resides to "High (Isolated)."  This forces the ASP page to run in its own process, which allows the security to be changed without affecting the rest of the web site:

    1. Start Internet Services Manager.

    2. Right-click on the Virtual Directory where the ASP page resides, and then click on Properties.

    3. Click on the Virtual Directory tab, and then select High (Isolated) in the Application Protection drop-down list.

    4. Click on the Apply icon.

  • Turn off Anonymous Access for this Virtual Directory and make sure Integrated Windows Authentication or Basic Authentication is selected:

    1. On the Properties dialog box for the Virtual Directory, click on the Directory Security tab.

    2. Click on Edit for Anonymous Access and authentication control.

    3. Make sure that the Anonymous access check box is cleared.

    4. Check either Integrated Windows Authentication or Basic Authentication.

  • If Integrated Windows authentication is used, then run the client browser to access the ASP page under the same user account as the Visual Basic IDE debug session.  If Basic authentication is used, enter the username and password for the same user account that the Visual Basic IDE debug session is running under.

Note: This workaround assumes that the COM "Default Access Permissions" have not been altered.  If the "Default Access Permissions" have never been altered, then COM constructs an access control list (ACL) that grants permission to the System account and Server Identity.  In this scenario, the Server Identity is the user logged in running the Visual Basic IDE debug session.  If the DCOM "Default Access Permissions" have been altered, then the second workaround requires that the user account that the Visual Basic IDE debug session is running under be added to "Default Access Permissions."  This can only be done by using DCOMCNFG.  For more information, please see the MSDN Online Library help topic on COM Security.

Solution 2:

The authenticated user for the Visual Basic (VB) run-time file (Msvbvm60.dll) does not have sufficient permissions.  The authenticated user is the IUSR_computername account when you use anonymous access, or the user that is authenticated with the web page.

To resolve this problem, assign Windows NT File System Read and Execute file permissions to the "Everyone" group (or to the appropriate users) for VB run-time (Msvbvm60.dll).  VB run-time is usually located in the "Winnt\System32" folder.