IIS 8 issue with SQL Monitor 3.3
absnom
Posts: 6
Hi,
We have installed a trial version of SQL Monitor 3.3 on a Windows Server 2012 box with SQL Server 2012 and IIS 8. I have followed the instructions for IIS at:
http://www.red-gate.com/supportcenter/C ... M_UsingIIS
and
http://www.red-gate.com/supportcenter/C ... ASP_issues
However, when I attempt to go the home page of the app, I get a routing error from IIS 8:
HTTP Error 404.0 - Not Found
Detailed Error Information:
Module IIS Web Core
Notification MapRequestHandler
Handler StaticFile
Error Code 0x80070002
Requested URL http://localhost:4444/UrlRouting.axd
Physical Path C:\Program Files\Red Gate\SQL Monitor 3\WebSite\UrlRouting.axd
Logon Method Anonymous
Logon User Anonymous
Request Tracing Directory C:\inetpub\logs\FailedReqLogFiles
There is, of course, no UrlRouting.axd. The fact that it is looking for one seems to indicate there is something mis-configured about the routing - but what? Appreciate any insight. Thank you.
We have installed a trial version of SQL Monitor 3.3 on a Windows Server 2012 box with SQL Server 2012 and IIS 8. I have followed the instructions for IIS at:
http://www.red-gate.com/supportcenter/C ... M_UsingIIS
and
http://www.red-gate.com/supportcenter/C ... ASP_issues
However, when I attempt to go the home page of the app, I get a routing error from IIS 8:
HTTP Error 404.0 - Not Found
Detailed Error Information:
Module IIS Web Core
Notification MapRequestHandler
Handler StaticFile
Error Code 0x80070002
Requested URL http://localhost:4444/UrlRouting.axd
Physical Path C:\Program Files\Red Gate\SQL Monitor 3\WebSite\UrlRouting.axd
Logon Method Anonymous
Logon User Anonymous
Request Tracing Directory C:\inetpub\logs\FailedReqLogFiles
There is, of course, no UrlRouting.axd. The fact that it is looking for one seems to indicate there is something mis-configured about the routing - but what? Appreciate any insight. Thank you.
Comments
Having said that though, I would recommend that you double check that you have correctly configured the application pool to use integrated mode (Application Pool > Basic Settings).
Fortunately, we managed to get it working yesterday. It turns out that something had changed in our web.config file. We never manually touched it, it was changed via the IIS Manager, as we adjusted settings. However, we kept a copy of the original web.config file and simply replacing the altered config file with the original was sufficient to get it working.