Puzzled and on the brink of insanity, I decided to go into IIS and see if my Authentication settings have changed. Sure enough, my ASP.NET Impersonation that my WCF service required was somehow turned off.
With the flick of a switch, everything started working again. I can only presume that the error was being caused because of a bad reference that crops up when turning off Impersonation. Sigh... If my employer only knew what I do all day...
UPDATE:
I turns out that my web.config was the culprit. If impersonation is not enabled in web.config then it resets it in IIS each time you build out to the server. This is the required code:
<system.web> <identity impersonate="true" userName="" password=""/> </system.web>
0 comments:
Post a Comment