Link to home
Start Free TrialLog in
Avatar of sanagarwl
sanagarwl

asked on

404 web services migration 1.1 to 4.0

we recently migrated from 1.1 .net to 4.0 .net - every thing works well locally but when we deployed to one of our development servers I'm getting a 404 error while accessing a web service.

any help would be much appreciated. The web service is a web application project and the current version of .net is selected.

ASKER CERTIFIED SOLUTION
Avatar of strickdd
strickdd
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of sanagarwl
sanagarwl

ASKER

thanks strickdd,

I looked at the extended log files and it turns out that the it was a path issue - it was trying to access the web service locally when in fact it should have gone to a remote server.

turns out while converting from 1.1 to 4.0 certain configuration setting are added added to the web. Config and since we have environment specific Config files these configuration settings in the default config file had to be manually configured in each of the environment specific configuration files.

We had the web services set to be picked up dynamically and due to the missing configuration settings (than are sepcific to .net 4.0) it was trying to get the web service locally which was nonexistant.

also we are using app pools - unfortunately the iis versions differ between production and the other environments - ie. uat dev and test.

should the app pool not be 4.0 irrespective of IIS version?

thanks for the help.