Especially those components that have just been installed, You need to manually set permissions, because for security reasons, permission restrictions are very low. You can refer to the following method settings.
Error message:
Server Object error 'asp 0178: 66661'
Server. CreateObject Access Error
../Asp. asp, row 123
Failed to call Server. CreateObject when checking the permission. Deny access to this object.
If the error is prompted, the permission is used.
Solution:
1. An error occurs when "server. createObject (" mssearch. application ")" is called. The solution is as follows:
Start> RUN> dcomcnfg
Find "mssearch" (the name depends on what the Object is called), right-click "Properties", and choose "security" to grant all three permissions to everyone. In fact, the first permission is enough.
2. When the above problem occurs, the reason is indeed the permission problem.
One solution is to modify the IIS Anonymous access permission.
The second simplest way is to register your components from another place, especially not to some special directories on the desktop or C disk (System Disk). Instead, you should register your components in a directory such as D, e. The reason is that the accounts used by your IIS are generally accounts with low system permissions. If you log on with your own account, the desktop access permission may be higher than that of the IIS account.
3. Check the MS database. The solution is as follows: fromaspxuexi.com asp Learning Network:
This article was previusly published under Q315454
SYMPTOMS
When you attempt to browse to an Active Server Page (ASP) database results page created in Microsoft FrontPage, you may receive an error message similar to the following:
Program code:
Server object error 'asp 0178: 100'
Server. CreateObject Access Error
../Config/coon. asp, line 5
The call to Server. CreateObject failed while checking permissions. Access is denied to this object.
CAUSE
This behavior can occur if incorrect NTFS permissions are defined for your "% ProgramFiles % \ Common Files \ System" folder.
RESOLUTION
To resolve your issue, reset the NTFS permissions on the "% ProgramFiles % \ Common Files \ System" folder. To do this, follow these steps:
1. Open Windows Explorer. To do this, right-click Start and then click shortcut E on the shortcut cut menu.
2.. In Folders view, expand the "% ProgramFiles % \ Common Files \ System" folder.
3. Right-click the folder and click Properties on the shortcut menu.
4. Click the Security tab.
5. Add Everyone to the existing permissions, give at least Read permissions to Everyone, and apply these new settings to all files and subfolders.
6. Click OK.
--------------------------------------------------------------------------------
For local debugging:
To solve the problem, reset the NTFS permission for the "% ProgramFiles % \ Common Files \ System" folder. To do this, follow these steps:
1. Open Windows Resource Manager.
Right-click Start and Click Browse on the shortcut menu.
2. In the folder view, expand the "% ProgramFiles % \ Common Files \ System" folder.
3. Right-click the folder and click Properties on the shortcut menu.
4. Click the Security tab.
5. Grant at least Everyone the existing permissions, read the permissions to Everyone, and apply these new settings to all files and sub-files.
6. Click OK.
--------------------------------------------------------------------------------
If it is a server, grant the relevant dll The everyone permission.