Deployment on production server : Ajax does not function; on local WorkStation is Ok

Hello,

I have just put to me to the AJAX, I installed it well on my PC, my ajax project with "Update Panel" functions locally.

I put it in production, I put the extensions in [bin]: "AjaxControlToolkit.dll"; System.Web.Extension is quite present in the GAC and when I click on the button to refresh the "update panel" in which a label update yourself. a traditional PostBack of alll the page is carried out! as if there were no Ajax!!?

Help me!

En fran?ais :

Bonjour,

Je viens de me mettre à l'AJAX, je l'ai bien installé sur mon poste, mon projet ajax avec un Update Panel fonctionne en local.

Je le mets en production, j'ai mis les extensions dans [bin] :
"AjaxControlToolkit.dll", System.Web.Extension est bien présent dans le GAC

et quand je clique sur le bouton pour rafraichir l'update panel dans lequel un label se mets à jour. un rafraichissement classique de toute la page s'effectue! comme si il n'y avait pas d'Ajax!!?

un peu d'aide ne serait pas de refus!

The first think I will ask you is to make sure the same version of Ajax is installed on the production server. I know it may sound silly, but I know several people with similar problem and they claim that they have the same version, but when they take a deeper look, they notice that there was not the same.

Deployment of AJAX-enabled web page on production server trouble

VS 2005 sp2, vb.net, sql 2005 enterprise sp2, IE7 & IE6, AJAX 1.0 toolkit and extensions.

The specific problem I am having is that I can't get the tabcontrol/tabpanels ("tab controls") to show up properly on the production server. I have a tabcontrol with 3 tabpanels. Inside each panel, I have a gridview and/or detailsview. When I load the page, I see the center gridlines (without the outer borders) of the gridview and detailsview and no tabs and no data. I also notice the "Done. Page loaded with errors" message on the bottom left status bar.

As with most of you, I have a dev machine and a production server. The tab controls show up just fine on the dev machine but when I move it to the production server, the same tab controls do not completely show up. The following is the watered-down version of what I am using:

<asp:ScriptManager ID="ScriptManager1" runat="server">
</asp:ScriptManager>
<cc1:TabContainer ID="Tabs" runat="server">
<cc1:TabPanel runat="server" ID="tab1" HeaderText="Tab1">
<ContentTemplate>
<asp:GridView ID="GridView1" runat="server" meta:resourcekey="GridView1" AutoGenerateColumns="False">
<Columns>
<asp:BoundField DataField="Column1" HeaderText="Column1" meta:resourcekey="BoundFieldResource1"></asp:BoundField>
<asp:BoundField DataField="Column2" HeaderText="Column2" meta:resourcekey="BoundFieldResource2"></asp:BoundField>
</Columns>
</asp:GridView>
</ContentTemplate>
</cc1:TabPanel>
<cc1:TabPanel runat="server" ID="tab2" HeaderText="Tab2">
<ContentTemplate>
...
</ContentTemplate>
</cc1:TabPanel>
</cc1:TabContainer>

I have installed the extensions on the production server (to fix another problem) and I have also confirmed that the dll's are in the bin folder. Any assistance as to why the tab controls not showing up is appreciated.

Thanks in advance to all. I am able to provide further information upon request.

anyone?

Just in case this may help someone else,

I found out the root of my problem was that I was using an AJAX enabled web-site instead of using the AJAX control toolkit template when I first made my website. I have mixed and matched some lines from my orginial "AJAX enabled" web-site and my new "toolkit template" web-site and found that the difference is only a few lines in the web.config file.

However, being exhausted in the search for an answer and not wanting to debug any further..., I decided to just move over all of my pages and worked it up in the "toolkit template" style.

I am having some of the same problems with my website and using the Tab Control. However, my website is pre-AJAX so I incorporated the new web.config and converted the existing web to use AJAX. Everything works fine on my development machine, but not when I deploy to the production server (which is running IIS 5.1). Do you think I should create a new website by using the new "toolkit template" and then copy pages to it?

I think installing the lastest versions of the toolkit and using the AJAX template is a good idea, perhaps not the only idea but the only one I have run across so far. Try to stay away from the AJAX enabled website since that was what I was using. I had also tried installing the AJAX toolkit extensions on the production server, which helped fix another problem I had with accordionpanes. This may have been related or not but since the toolkit is very new, it looks like there are still a lot of kinks they need to go over and for us to go around for now. But I would do the upgrade first before going and installing things on the production server.

If you can/have figure(d) out the difference in the web.config file, that should be enough but if it would give you peace of mind, upgrading it might not be a bad idea as it seems to have fixed additional minor bugs that I have run across.

When upgrading, the major difference I noticed was that I had to delete the two <cc1> references on each page (first the reference at the top of each page and the second in the page itself) and replaced it with <ajaxtoolkit> only inside the page. The reference was not needed at the top of each page for <ajaxtoolkit>, maybe something to do with the new web.config.

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.

Deploy Toolkit to Server

Please help!

My development box works gret with the latest toolkit. When I try to deploy to the production server, my popups do not work. I've installed the latest AJAX components per the instructions on the server and copies the latest AjaxControlToolkit.dll to the bin directory. What am I missing?

If this helps:

The ScritManager output from the site that works is:

<script type="text/javascript">
//<![CDATA[
Sys.WebForms.PageRequestManager._initialize('ScriptManager1', document.getElementById('form1'));
Sys.WebForms.PageRequestManager.getInstance()._updateControls(['tupTable','tdateStart$UpdatePanel2','tdateEnd$UpdatePanel2'], [], [], 90);

//]]>

The ScritManager output from the site that does not work is missing the //<![CDATA[

Also,

the page that does not work does not have any of the javascript create code from the toolkit.

Any ideas?

Did you modify the web.config properly on the server (should pretty much match your dev machines one...) also on your server make sure you have this entry in it:

<location path="ScriptResource.axd">
<system.web>
<authorization>
<allow users="*"/>
</authorization>
</system.web>
</location>
</configuration>

Thats the probable solution if all the installs went well and are properly GACed