Hello,

When deploying our website to our test server with VWG 6.4 we are getting a 404 Page Not Found error.

More specifically, our *.wgx Handler Mapping appears to be getting ignored completely by IIS. The error text on the 404 page shows:
Module: IIS Web Core
Notification: MapRequestHandler
Handler: StaticFile
Error Code: 0x8007002

During investigation we realized that if we remove or break the StaticFile handler mapping from our site (ie, set the path to *.NOTHING) our 404 error page shows:
Module: IIS Web Core
Notification: MapRequestHandler
Handler: Not Yet Determined
Error Code: 0x8007002
 

The *.wgx Handler Mapping is as such:
Request Path: *.wgx
Executable: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll

The app pool is in Classic mode with .NET Framework v4.0.30319

This server is successfully hosting several other versions of our site with VWG 6.3.15 and .NET 3.5. 

Any ideas?  Why does ASP.NET not seem to acknowlege our Script Mapping?

Thanks,
Andrew

Thanks Palli, but I don't think that applies here.  We aren't using any virtual directories, each site is it's own top-level site.  Any other ideas?

Thanks Palli,

We did what you suggested: we removed all *.wgx handler mappings from all sites, and then added one *.wgx handler mapping at the server level using this executable: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll.  When we still received the 404 error I created the same handler mapping at the site level, but we still get a 404 error.

Can you verify this setting in our web.config?  It previously had a version of 3.0.5701.0 and a Public Key Token...

<add verb="*" path="*.wgx" type="Gizmox.WebGUI.Server.Router,Gizmox.WebGUI.Server,Version=4.0.5701.0,Culture=neutral,PublicKeyToken=null" />

Thanks, any other ideas you have would be helpful.
Andrew