• Post Reply Bookmark Topic Watch Topic
  • New Topic

Problem in IIS7(64bit) on Windows 2008(64bit) Configuration with JBOSS 4.3.0

Mp Ramkumar
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I am getting the following error on IIS7 setup on windows 2008(64bit) environment.

I followed the guide http://www.jboss.org/community/wiki/UsingModjk12WithJBossAndIIS7.pdf and used the 64bit connecter(i.e., http://www.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/win64/jk-1.2.28/ia64/isapi_redirect-1.2.28.dll). It is not working. The same instruction given in the guide is working fine for 32bit environment with 32bit mod_jk connector.

Just after installing the IIS, I am able to see the IIS page on accessing http://localhost/. Once I place the isapi_redirect.dll from the above mentioned location, I am getting the following error.
Calling LoadLibraryEx on ISAPI filter C:\JK\bin\isapi_redirect.dll failed

I have set the parameter "enable 32 applications" in default app pool to Only http://localhost/ is giving the IIS7 page. But when I access the url http//localhost/awebapp I am getting the error mentioned under Error Summary section. If I access the url without IIS then it is working fine(ie., http://rentsrv15s1:8080/awebapp/)

On IE the error displayed is as follows:

Error Summary: -------------------
HTTP Error 404.0 - Not FoundThe resource you are looking for has been removed, had its name changed, or is temporarily unavailable. Detailed Error Information:Module: IIS Web Core Notification: MapRequestHandler Handler: StaticFile Error Code: 0x80070002 Requested URL: http://localhost:80/awebapp/ Physical Path: C:\inetpub\wwwroot\awebapp\ Logon Method: Anonymous Logon User: Anonymous
Failed Request Tracing Log Directory: C:\inetpub\logs\FailedReqLogFiles

Most Likely Causes:The directory or file specified does not exist on the Web server. The URL contains a typographical error.
A custom filter or module, such as URLScan, restricts access to the file

Things you can Try:Create the content on the Web server. Review the browser URL.
Create a tracing rule to track failed requests for this HTTP status code and see which module is calling SetStatus. For more information about creating a tracing rule for failed requests, click here.

Can some one help me out on this.

Thanks & Regards,

  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!