Deployment Issue of AjaxControlToolkit

Hi,

I have used the Ajax Control toolkit and on the Development machines it is working fine. but when I deployed it to the production server it stops working. The error it displays is that it is not able to get the embedded JavaScript files. This problem occurs on the pages which are using control like the Accordion and calender pop up.

I am not sure what is causing this because i have installed the latest asp.net Ajax on the server and copied the AjaxControlToolkit dll in the Bin also

Other embedded resources are working fine on type of resources like the images but they give errors when the resource type is JavaScript.

Do you have the proper setup (in web.config file) for the ScriptHandlerFactory handler and the scriptmodule?

Also, does any other ajax control work in your app? If Ajax is not GAC-ed you will probably need to set the app to full trust.

I have copied the Script Handler from the Ajax Toolkit.

Second. I have installed the Ajax and used the default settings.

There is another custom control which is working fine except that we have to put its resources through the Script tag of the ScriptManager. this is also does not load the scripts from the embedded assembly. but it works fine after we referenced the script through the Script Manager.

The same is working just fine on my development machine.

Deploying Atlas to Non Dev Machines

I have an intranent application that gets iframecall.axh errors when deployed. It if I change the script manager paths to point back to a development box.(?).

Debug error message: "A web request made using the iframe executor failed. Make sure that the app's web.config registers iframecall.axd"

What am I missing? Something must need to be done to these test machines to deploy.

The http handler is set :

<addverb="*"path="iframecall.axd"type="Microsoft.Web.Services.IFrameHandler"validate="false"/>

Each of the Web Methods.

WebOperationAttribute(true,ResponseFormatMode.Json,true)

Why does Atlas use the header name and the port to call its self? I found the cause of the problem. Its appears that since we use a CSS ( type of cysco router ) to route traffic on shared servers that the call to the service is using the host header and the port which when re-routed back to the server is incorrect. If the site is available on http://<server>:<port> but the users calls it with the host

headerhttp://<host header> the call back to iframecall ishttp://<host header>:<port>

Here is an example: http://MySite/service1.asmx if hosted onhttp://MyServer:8040/service1.asmx gets called viahttp://MySite:8040/service1.asmx and fails.

Is there a work around for this or how do I fix it?