IIS 5 & IIS 6
IIS 6 .Net 2.0 ASPX website Migrated to IIS 10
Last post Jan 01, 2018 06:56 AM by Yuk Ding
Dec 31, 2017 06:07 AM|zm1868179|LINK
I was tasked with trying to migrate an old program the operates some Kiosks over to a new version of IIS. The Program used to run on a Windows XP machine that had a .net 2.0 Service executable and also had a .net 2.0 ASPX website running that the clients
connected to both services. I've run out of ideas on how to migrate this over to IIS 10 on Server 2016 All the program services connect but the IIS website portion the kiosks will give out a Service unavailable message if they cant talk to the web service
correctly. We did not develop this program and the company no longer exists. In the IIS Logs I see this:
It seems like the iis web service is giving out a http 405 error method and I have tried every kind of method I can think of. Would anyone have any suggestions on how I could approach this.
Dec 31, 2017 08:55 AM|Rovastar|LINK
try failed request tracing for that http status code 405
maybe that will give more clues on what method is being requested.
Or go for wireshark it and look at the packets directly.
Jan 01, 2018 06:56 AM|Yuk Ding|LINK
Most of time, it means that the IIS use the wrong mapping handler or the http method is not allowed by the request filter. Please enable the failed request tracing to trace 405 as Rovastar said, then you should be able to see the Module and handler name
in the detailed error information. Then please ensure it is mapping to the right place. If it is mapping to the default document module or directory listing module, please adjust the order list in IIS manger handler mapping. In handler mapping, you could click
a hander->edit->request restriction->VERB, please ensure your method is allowed.
Finally, please ensure all the application development feature in turn windows features on or off/internet information service/world wide web service/application development feature has been installed.
Of course, you could try to change the application pool to .net 2.0, classic mode like your IIS 6 server.
You could try the process monitor, maybe some permission is required for the application. It could monitor the permission in w3wp.exe