Posted by bertoheep on 03/01/06 18:33

I've found the solution to my problem:

Thought someone would save some time and headaches by using this post.

Our tech department is migrating to Windows 2003 Server and they have
some complex security implementations between our Web Servers and our
Application (COM) servers.

If you have this type of scenario and are receiving the "Warning
(null)(): Unable to lookup.... Access is denied." error, it is because
the "Identity" in the Web Server's application pool does not have
sufficient permissions to connect to the Application (COM) Server.

To fix this:

- create a new Application Pool
- right click the new pool and select "properties"
- click on the "Identity" tab
- change the permissions from "Network Service" to a user on the Web
Server who has access to call the Application (COM) server.
- right click the application pool
- click "start"
- right click your web site
- click on the "Home Directory" tab
- change the application pool to the new application pool you've just
created.
- restart IIS

Hopefully this will save someone some time and headaches.

• Next in forum: design question: sessions vs arguments
• Prev in forum: MySql VCHAR column converted to float by PHP :-(
• Thread view: Re: PHP, DCOM, IIS 6, Application Center Installation

[Reply to this message]