AH fixed it. Has to do with running in IIS 7 and on the local machine
Now that we've covered that, if your ASP.NET app has HTTP modules and you want to make sure it runs in both IIS6 and IIS7 Integrated Pipeline mode (from here on out just referred to as IIS7), you need to make some changes to web.config (there are other things to consider as well when running an ASP.NET site under IIS7, so definitely check out this article first for details). The web.config changes needed are for your HTTP modules and handlers. For IIS6, they were configured in the <system.web> section, as such:
<system.web> </httpModules> <add name="..." type="..." /> </httpModules> <httpHandlers> <add verb="...." path="..." type="..." /> </httpHandlers></system.web>
However, to get these to work in IIS7 you must *move them* from the <system.web> section to the new <system.webServer> section, which is what IIS7 requires when running in Integrated Pipeline mode (it's not needed for Classic Pipeline mode). So instead of the above you'd have this instead:
<system.webServer> </modules> <add name="..." type="..." /> </modules> <handlers accessPolicy="Read, Write, Script, Execute"> <add verb="...." name="..." path="..." type="..." /> </handlers></system.webServer
Notice there are a couple slight changes, which means you can't just copy and paste these as-is from <system.web> into <system.webServer>:
<httpModules> and <httpHandlers> have been renamed to <modules> and <handlers>, respectively.
Each handler in IIS7 requires a name attribute. If you don't specify it, you'll get an error message.
The handlers node has an optional, but good-to-define accessPolicy attribute. This value depends on your handlers, so use the ones that are right for you.
a work around would have been to switch the Application Pool Pipeline Mode from integrade to classic but it is better to get it to work with IIS 7 to get all things good!
Points for all~!