Ok, got your url and tested it out. I got the same problem here so dug a little deeper with a tool called “Fiddler” which shows the actuall http traffic between my browser and your server and discovered the problem immediately: Your server is not serving up the webresource.axd resources which is absolutely required to run AyaNova WBI or any other modern asp.net application.
For a brief explanation of what this is about see here: http://aspnet.4guysfromrolla.com/articles/080906-1.aspx
Essentially AyaNova will not work until the server is configured to serve webresource.axd. This is not a file, it’s a resource that is autogenerated by asp.net 2.0 controls. By default an out of the box installation of IIS 6 with .net 2 should have the webresource.axd handler installed and working by default so something is misconfigured, missing or blocking that handler at your server.
The problem here is there are many possible reasons why this might be happening on your server and not really related to AyaNova WBI itself, however I’ve done some digging on Google:
There are known issues which I will link to for you here, we had one other client with a similar problem and it seemed thatreinstalling fixed it which is a bit of a mystery, but apparently they had copied an installed wbi to another directory or something so if the setup wasn’t default then you might want to consider it as well, I will put those steps at the bottom of this post as a last resort thing to try, but it’s more likely one of the following issues:
Web farm / Web garden - if you have one multiprocessor IIS server configured as a web farm or multiple servers configured as a farm there is a known issue with webresource.axd I couldn’t find much more info on it but this thread indicates a solution:
Some form of 3rd party security tool installed on the server which is outdated or not familiar with webresource.axd handler as mentioned in this thread:
Also if anyhttp compression tool is installed on the server it can cause issues with webresource.axd so look for any 3rd party http compression tools and if found explicitly disable webresource.axd or .axd extension.
WBI comes with a compression module built into it and in our web.config file for WBI we explicitly exclude webresource.axd for the same reason that it should be disabled for a 3rd party general compression utility on an IIS server, it’s possible that section of your web config is missing or is damaged, make sure you see something like this:
<add path=“WebResource.axd” />
in the WBI web.config file near the top in the Compression section.
There is some talk about turning on the webresource.axd handler, I’ve yet to find a good link that shows that and I’m not sure if it’s even possible, but something to consider if the configuration has been messed about with.
Finally if none of that works, try a good old fashioned re-install per these instructions:
- Uninstall WBI completely - after the un-installation, if any left over files, remove completely.
- Reboot the computer
- Now perform the WBI installation again - but take the defaults such as installing to the Default Web Site (when experiencing an issue, by taking the defaults you eliminate other influences that are causing the issue)
- Edit Web.Config as directed in the steps.
- Now delete the cache on the web browser on a