I have tried to setup a test instance of BOXI 3.1 SP3 using the configuration of both IIS and Tomcat installed just so I can guage the differences between the classic/vanilla BOXI Java/Tomcat install and the BOXI .NET install.
Everything appeared to correctly install and the BOXI CMC Login on WACS works but the BOXI Infoview Login does not and instead gives me a 403.18 forbidden error when I try to access the page.
Have had a look in IIS and the application pools and related directories seem to have installed correctly. I also have tried changing the login user of the Application Pool to other users (e.g. to Local Admin’s, Network Admin’s etc.) but to no avail
did you find an answer. i am getting this now while trying to do a new install…
the exact message:
Server Error in Application "DEFAULT WEB SITE/INFOVIEWAPP"Internet Information Services 7.5
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/InfoViewApp
Physical Path C:\Program Files (x86)\Business Objects\BusinessObjects Enterprise 12.0\Web Content\InfoViewApp\InfoViewApp
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 InformationThis 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.
View more information »
How are you trying to access the page? What url, port? I thought WACS gave you an odd port, 8443 - sound right?
Permissions? What user runs IIS, can it see the folder where this gets deployed (an odd folder under BO, not the same as the rest of Infoview) - I always suspect that with that AUTH set of errors…
I managed to fix the 403.18 error on my Windows 2008 R2 server by adding roles to IIS using the “Server Manager” program -> “Customise this server” -> “Add roles” -> “IIS”.
If IIS is already installed, you may have not added enough roles. If in doubt add all available roles.
Also, the IIS Application Pool used by XI needs to be set to run 32 bit applicatons. This is done in IIS Manager -> Application Pools -> Select the "Classic .NET Applicaiton Pool -> right-click for Advanced Settings -> change “Enable 32 bit applications” = “True”.
(BOB member since 2009-11-03)
(BOB member since 2002-08-29)