Server.CreateObject Error of ASP program

Because of the past has not used XP system (or in the university that will XP just came out of the time used, later has been no use XP, then did not like its gaudy interface, hehe. ), never encountered such a problem, today in the help of a friend mm solution Excel import into the SQL Server database encountered such a problem, the ASP code does not have the right to create Excel objects (my XP Professional English), probably XP default permissions limit the problem, So to Baidu search a bit, found the solution is as follows:

Many people who use the IIS stand often encounter similar problems.

An error occurred while the ASP program was CreateObject, roughly the server object error ' ASP 0178:80,070,005 ', which typically occurs on a newer version of IIS or a Windows platform.

If you are using the Chinese version, the error message is as follows:

Program code:

Server object error ' ASP 0178:80,070,005 '

Server.CreateObject Access Error

.. /config/coon.asp, Line 5

A call to Server.CreateObject failed while checking for permissions. Access to this object is denied.

If this is an English version, the error message is as follows:

Program code:

Error Type:

Server object, ASP 0178 (0x80070005)

The call to Server.CreateObject failed while checking permissions. Access is denied to this object.

.. /config/coon.asp, Line 5

Workaround:

1. When the "Server.CreateObject" ("Mssearch.application") is invoked, an error occurs, resolved as follows:

Start-> Run->DCOMCNFG

Find "MSSearch" (this name depends on what you call the object), and then the right button->properties->security to all three permissions to everyone, in fact, the first can be.

2. The reason for this problem is indeed the question of competence.

One workaround is to modify the permissions of IIS for anonymous access.

The second easiest way to do this is to register your components in a different place, especially if you don't want to put them on a desktop or some special directory in C (the system disk), and you should put them on a disk such as D,e. The reason is because your IIS is usually used by the account is a lower system permissions account, if you are logged in with your own account, then the desktop access may be more than the permissions of IIS account.

3. The database of MS was checked and the solution was as follows:

To resolve your problem, reset NTFS permissions in "%programfiles%common Filessystem". To do this, follow these steps:

1. Open Windows Explorer.

2. In the folder view, expand the%programfiles%common Filessystem folder.

3. Right-click Folder on the shortcut menu, click Properties.

4. Click the Security tab.

5. Add all the existing permissions to everyone, at least read the permissions, and apply these new settings to all the files and subfolders.

6. Click OK.