I was creating a new web application on a WSS 3.0 server for hosting BPM application webparts. This new site had to be accessible from Internet. While creating the new web application I provided a host header which was already set up in the DNS server and it had an IP address too. Next I created a site collection.
After creating this web application I provided this IP address on the properties tab in ISS for this website. It was created on port 80. I had also provided the IP address in the "Advanced TCP/IP Settings" of this server. Now when I tried to access this new web application, I got the error "Gateway time out".
I had no clue as to what was causing this error. Then a colleague pointed me to a Microsoft fix for this issue: http://support.microsoft.com/kb/896861
After applying this I had to restart the server and now there was another error. It said "File not found". I edited the web.config of this web application so that I get a detailed error. I changed callstack to "true" and customerror to "Off". The issue was related to some dlls for this BPM webparts. I checked the solution management section in Central Administration - Operations and found that wsp for this BPM application was deployed locally for another web app and not globally. Then I deployed this wsp for my new web application and error vanished. Things are sorted out now.
For more information on the Loopback issue Check this blog
After creating this web application I provided this IP address on the properties tab in ISS for this website. It was created on port 80. I had also provided the IP address in the "Advanced TCP/IP Settings" of this server. Now when I tried to access this new web application, I got the error "Gateway time out".
I had no clue as to what was causing this error. Then a colleague pointed me to a Microsoft fix for this issue: http://support.microsoft.com/kb/896861
After applying this I had to restart the server and now there was another error. It said "File not found". I edited the web.config of this web application so that I get a detailed error. I changed callstack to "true" and customerror to "Off". The issue was related to some dlls for this BPM webparts. I checked the solution management section in Central Administration - Operations and found that wsp for this BPM application was deployed locally for another web app and not globally. Then I deployed this wsp for my new web application and error vanished. Things are sorted out now.
For more information on the Loopback issue Check this blog
Comments