HTTP Error 403.18

[explorer]

Lansweeper is installed and seems to be working. Computers that run lsclient.exe show up in the Lansweeper Configuration utility. With firefox and ie8 I can get to http://localhost:9524 and get the message "congradulations your lansweeper service is running..." etc and the total number of computers processed is right. My problem is that I can not open http://localhost/lansweeper - that gives me a "HTTP Error 403.18". The Permissions look correct . Is this supposed to give me the same display / informaiton as the configuration utility ? How can I get it to open in the browser ?

Installed on Vista ultimate sp2 / IIS7 Manager shows 'lansweeper' as a virtual directory and the path to it is correct.

[explorer]

Thanks Lansweeper - I got it going now thanks to your link. I had the same issue with .net and asp.net not added into IIS that this other person had. After adding both .net and asp.net, I had one more small issue that I'll mention here for the benefit of anyone else running into this. After adding .net and asp.net to IIS, I got a "HTTP Error 500.19 - Internal Server Error".

The "config source" section on this error page showed that the config file was trying to add "default.aspx" as a duplicate entry which causes the error. In the C:\inetpub\wwwroot\web.config file, I removed the line
"<add value="default.aspx" />"
from the "files" section:
<files>
<add value="default.aspx" /> <<-----remove just this one line
</files>

and that took care of that little problem.

[Hemoco]

Please check if this solves your problem : http://www.lansweeper.com/forum/yaf_postst1419_HTTP-Error-40318-on-Server-2008.aspx

[explorer]

Ofcourse, here is the entire output:
-----------------------------------------------------------------------

Server Error in Application "DEFAULT WEB SITE/LANSWEEPER"
Internet Information Services 7.0

Error Summary
HTTP Error 403.18 - Forbidden
The specified request cannot be processed in the application pool that is configured for this resource on the Web server.

Detailed Error Information
Module IIS Web Core
Notification BeginRequest
Handler StaticFile
Error Code 0x00000000
Requested URL http://localhost:80/lansweeper/
Physical Path C:\Program Files (x86)\lansweeper\website\
Logon Method Not yet determined
Logon User Not yet determined


Most likely causes:

* An ISAPI filter or custom module changed the URL to run in a different application pool than the original URL.
* An ISAPI extension (or custom module) used ExecuteURL (or ExecuteRequest) to run in a different application pool than the original URL.
* You have a custom error page that is located in one application pool but is referenced by a Web site in another application pool. When the URL is processed, it is determined by IIS that that it should have been processed in the first application pool, not the other pool.
* The Web site has multiple applications configured. The application this request is configured to run in is set to run in an application pool that does not exist.

Things you can try:

* If you have an application that is trying to process a URL in another application pool (such as trying to process a custom error), ensure that they both run in the same application pool if appropriate.
* If you are trying to process a custom error URL that is located in another application pool, enable the custom errors Redirect feature.
* Verify that the application pool for the application exists.
* Create a tracing rule to track failed requests for this HTTP status code and see if ExecuteURL is being called. For more information about creating a tracing rule for failed requests, click here.

Links and More Information This error occurs if the application pool for the request does not exist, or if an ISAPI filter, ISAPI extension or HTTP module calls the ExecuteURL server support function (or ExecuteRequest) with a URL that is configured in a different application pool. Due to security reasons, a Web site in one application pool cannot make ExecuteURL requests against a URL in another application pool. If you have an application that is trying to process a URL in another application pool, ensure that they both run in the same application pool if appropriate.

[Hemoco]

Could you please post the output of your complete error screen.

Might be related to this issue : http://support.microsoft.com/kb/942037