Visual Studio 2008 Publish Fails.

Question

HI everyone, i need some advice regarding Visual Studio 2008 Pro.

We develop a lot of web service applications and ever since we started we keep encountering an error on our production server that does not seem to occur on the development or test systems.

When publishing new code to the server we are normally met with the following error.

Publish Failed : Bad Gateway : Status Line Invalid. (very similar to this our dev team were not able to provide me a screenshot or exact wording unfortunatly).

even though we get this error the web service always functions 100% the way we expect it to. has anyone else come across this error ? or a solution / reason for it ?

the PC doing the publish is a windows xp SP3 system, the server we are publishing too is a fully patched windows 2003 server box.

The test and Dev servers we have are pretty much clones of the production system and like i mentioned when publishing to test / dev we get no hint of this problem or error it only ever shows up when publishing live.

If it makes a diff, the test / dev servers are on the same network addresses as the client PC (10.0.0.x) whereas the production server is on a different network range (192.168.0.x) With a Firewall between them.

This problem only ever seems to rear its ugly head on one particular project, other programs (webservices if thats the correct term) publish to the same server without incident.

thanks for any help guys

Kris

Answer 1

OK This problem has been resolved. turned out to be something a lot simpler than expected.

we use sub-domains of our main website to point to servers within our network, for publishing etc (this was the late idea of a previous IT Person). what we have found is publishing to these domain names generates the Bad Gateway error pretty much constantly.

however using the internal network ip of the server never generates this problem.

it seems to be down to how we have the domains configured and the routing through the firewall which is causing this problem. although we are going about doing the publishes in a very round about way.

the solution to us was to use the internal IP addresses to publish to the servers rather than a domain that pointed to external IP's that routed through the firewall.