We got the web interface installed and it works fine from the server that is hosting the site. We can also access the WBI from other computers on our LAN except we always get the error “Can’t init script for WebDialogActivator” at the bottom of the page and the page doesnt load properly. The login page also gets an error and the details are error line 65 and object expected. I really need to get this up and running.
Thank in advance for any assistance.
tanderson (1/8/2007)We got the web interface installed and it works fine from the server that is hosting the site. We can also access the WBI from other computers on our LAN except we always get the error “Can’t init script for WebDialogActivator” at the bottom of the page and the page doesnt load properly. The login page also gets an error and the details are error line 65 and object expected. I really need to get this up and running.
Thank in advance for any assistance.
Hello, that’s very strange. It sounds like a general problem of some kind with the browsers configuration. There are no known issues similar to what you report. I suspect perhaps the browsers being used may be locked down or have functionality disabled that is preventing it from working. Javascript is a definite requirement, if it’s turned off or disabled that could result in many odd problems.
Since it works at the server and partially works (at least you can navigate to the site and get some response) that rules out the usual culprits like firewalls and security at the server itself.
What I would recommend is one of two things: If you are intending on opening this up for outside users of your network and it’s accessible via the internet we can test it from here, email privately to support@ayanova.com with the address and a test login we can use.
If it’s not accesible externally then what I would suggest is a two pronged approach: download and test with an alternate browser that has all it’s default settings, i.e. if you are using internet explorer now, download and install FireFox (http://www.getfirefox.com) or Opera (http://www.opera.com/)just to narrow the scope of the problem.
This is just for diagnosis, I’m not suggestion you need to change browsers permanently, but if a completely different browser has the same problems then it eliminates your standard browser itself as the source of the problem. If it does not have a problem then it points squarely at your current browser and it’s settings.
The other part of this would be to gather the version number and type of each browser you are testing it with and let us know what they are, as well check the browsers settings and note if javascript is enabled or not and also very important make a note of any 3rd party software that might be installed for web browsing security which might be messing with the page transfer or partially blocking the site.
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:
http://www.thescripts.com/forum/thread442090.html
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:
<excludedPaths>
<add path=“WebResource.axd” />
</excludedPaths>
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: