Ajax beta 2 is not working with iis 6

i downloaded the ajax beta 2 from ajax.asp.net and install it in the production server which has iis 6, and i publish the site which is running well in the development server, ajax is not working any more, with any pages action they page refresh itself, i dont know what's is going on!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

OK!Have you deployment it?
Can you actually respond with actual errors it would help US help you..

Hi,

As my knowledge it wills works without any errors,

Please go through your code, you might be did mistakes in the code.

Or can you send the code then only forum can help you.

Maximum problem with your code only..

Pradeep Kumar Bura

the pages dosn't display any error message, the situation is that the page has update panel , so when user click on a search button it should display the result inside the update panel without refreshing the page, and thiss happen in the development server, but on the production page the same page server when user click on the search button, the pages is refreshed :(

Hi,

Have you checked event log for errors?

Pradeep Kumar Bura

Hi. I had a similar problem. After Installation on productive server, the sites were'nt executable because the webserver didn't found one the assemblies which will be installed while the extension installation (Microsoft.Web.Extension and Microsoft.Web.Extension.Design).

I installed and registered the assemblies whith gacutil and the aplication was running again.

I've deployed AJAX Beta 2 to four servers running IIS6. On two of the four I ran into the same issue that Michael63 describes. For me Microsoft.Web.Extension.Design was not added to the GAC. You can either register it in the GAC or you can copy it to your site's bin directory. I did the GAC way on one server and copied it into the bin folder on another - both work fine. The other thing you may want to check is that a new entry in the web.config is required. Check out the readme included with the installations for instructions.
Your site has to be running in full trust mode to be able to run the dlls in the bin folder.

i did that, and i checked that the assemply is added to the GAC , but still the site working very well in dvelopment server, but on production server, it's not the only differnce is that the development server has atlas component before but i uninstalled it before install ajax, but it was the only differnce

http://forums.asp.net/thread/1485037.aspx
follow this threadhttp://forums.asp.net/thread/1485037.aspx

AJAX Beta 1 has forced my pages to US Date format !

Since adding AJAX Beta 1 to my PC all my IIS sites are now showing and requiring dates in MM/dd format instead of dd/MM as they were before.

I have tried:

<globalization culture="en-NZ" uiCulture="en-NZ"/> in by config file and set each page to the same.

Anyone else know why this is and how I can get around this issue ?

Thanks

Matthew Hill

hello.

hum...strange...atals used to have some globalization support but in only influenced client side locale methods. how are you putting the dates on the pages?

I have FormView & GridView controls that display various data from a database. The queries to the database returns the dates as Date fields as per normal but since adding AJAX Beta 1 and the corresponding AJAX Toolkit the dates are showing as MM/dd/yyyy. I set the locale to en-NZ in every page and in the global settings but still they are showing wrong. I also checked my locale settings.

Is it possible that something may be corrupt in the website?

Mat

hello.

though i'm no globalization expert, i think that the problems you're facing are related with ASP.NET and not AJAX extensions. It's really strange that it only has affected your app after adding the extensions...does removing the extensions solve the issue?

Thanks for your reply.

I have tested copying it to another server with AJAX and the dates are around the right way. I still can't figure out why none of the settings are changing the dates back to en-NZ. If I view the site from another PC it is around the wrong way. Argggghhh.

Mat

hello.

quick question: are you pages configured to use localization? if so, are they configured so that they get the values from the browser? if that is tru, then what might be happening is that the browser may be using US culture by default and sending that info back to the site...

I have checked and can't find a US date setting anywhere in IIS, IE7, Regional Settings, Visual Studio, Ajax, Ajax Toolkit. I'm hoping it's not gettings it's settings from the system's Regional properties (the ones created during Windows install) as I don't know how to change them. Also I don't know why they have only just started to effect IIS.

If you visit my website from another PC it shows in US format too, so it is definately an IIS issue.'

Mat

I have checked and can't find a US date setting anywhere in IIS, IE7, Regional Settings, Visual Studio, Ajax, Ajax Toolkit. I'm hoping it's not gettings it's settings from the system's Regional properties (the ones created during Windows install) as I don't know how to change them. Also I don't know why they have only just started to effect IIS.

If you visit my website from another PC it shows in US format too, so it is definately an IIS issue.'

Mat

In ScriptManager's element try to add attribute EnableScriptGlobalizationwith value false:

<atlas:ScriptManagerrunat="server"ID="scriptManager"EnableScriptGlobalization="false"EnablePartialRendering="true"/>

Probaly it's because of your preffered languages in IE7 (as rule there is "English [en-us]").

AJAX becomes full postback in IIS

I made a simple AJAX page in Visual Studio 2005, which has a button click to get server's system time. It works fine inside the VS2005. But when I put it on IIS in Windows Server 2003, the button click becomes a full postback. Do I miss something? Does anyone have any idea?I wrote a testing Ajax website to get server time in a asp:UpdatePanel and deplyed it to Windows Server 2003 IIS.It worked fine and didn't?happen?to full postback.Here are my sample codes for your reference.Wish this can give you some helps.
<div>
<asp:UpdatePanel ID="upnlServerTime" runat="server">
<ContentTemplate>
<asp:Label ID="lblServerTime" runat="server" Text="Server Time"></asp:Label>
<asp:Button ID="btnServerTime" runat="server" Text="Get Server Time" OnClick="btnServerTime_Click" />
</ContentTemplate>
<Triggers>
<asp:AsyncPostBackTrigger ControlID="btnServerTime" EventName="Click" />
</Triggers>
</asp:UpdatePanel>
</div>
Behind Code:
protected void btnServerTime_Click(object sender, EventArgs e)
{
Label lblServerTime = upnlServerTime.FindControl("lblServerTime") as Label;
lblServerTime.Text = DateTime.Now.ToLongTimeString();
}

I doubt you don't create web application when you create a virtual directory in IIS.Right mouse click virtual directory in IIS and select Properties,Click "Create" button to create application name and Choose Execute Permission for "Scripts only" or "Scripts Executable" from permission DropDownList.Try to addNetwork Service to virtual directory?when?deploying?Ajax?
website.
Wish this can give you some ideas.

ajax become slowly after iisreset

Hi there,

After reset iis the ajax become slowly for about 15 seconds and then contiue as regular.

It seems like it stucks for a few minutes.

Does anyone know this phenomena ?

Thanks a lot !

After iisreset, the first call to your application will have a longer response time. This is because the app is no longer compiled, and has to be compiled by the JIT compiler before it is executed. Once this initial compile is complete, subsequent requests are much faster.

AJAX and Vista -

I just upgraded to Vista from XP where I had IIS running very happily and AJAX installed and working great.

After upgrading to Vista I get this browser error on any AJAX website:

'Sys' is undefined

I remember seeing that error months ago back when it was called Atlas. But now that I'm running the latest OS, with a non-beta AJAX, why should I be getting this now? The upgrade to Vista has been painful all around, but I've managed to fix or find workarounds for most problems except this one.

It seems like the AJAX stuff isn't getting included into the webpage. I even tried creating a fresh project in VWD and specifying to use the VS template for "ASP.Net Ajax Enabled Website" and throwing together a simple page with an updatepanel and a command button. Same error.

I've run Windows Update and gotten all the updates, including the Visual Studio update that tells you to run VWD "as an administrator", which I'm doing.

The line in the generated page that it is complaining about is the first reference to Sys below.

Hopefully there is just some simple security setting in this locked down OS I don't know about to allow this to run? 

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

</script>

Do you have following entry in your web.confg file?

<add verb="GET" path="ScriptResource.axd" type="Microsoft.Web.Handlers.ScriptResourceHandler" validate="false"/>

Also, follow Readme notes on migration issues on ajax.asp.net .

Yes, I have that. This was a functioning ASP.Net 2.0/AJAX 1.0 application when I had XP, but now that I'm running windows Vista, it doesn't work.

I did have to manually edit applicationHost.config in C:\windows\system32\inetsrv\config to add entries for ASP.Net 2.0 (it only had enties for 1.1), so I'm wondering if something must be added there to support AJAX.

I tried downloading and re-installing AJAX, rebooting, all the obvious stuff with no luck. Upgrading to Windows has ALMOST completely shut me down from developing.

I did just discover that when I use the VWD built in web server, AJAX works fine. So AJAX is "installed" correctly on my PC. But as far as when I use the full-blown IIS web server, AJAX is dead.

I didn't see anything in the README relating to Vista migration, only migration from previous versions of Ajax/Atlas, which is not what I'm doing.

Here is what I ended up doing as I spent nearly two days trying to rebuild my Dev machine after purchasing a Vista capable laptop.

1. Mark your site in IIS7 as an Application (The choice is there if you right click on virtual IIS7 entry in the expanded list under websites...

2. Make sure that you have included all of the IIS7 web.config entries:

<

system.web.extensions>

<

scripting>

<

webServices>

<!--

Uncomment this line to customize maxJsonLength and add a custom converter-->

<!--

<jsonSerialization maxJsonLength="500">

<converters>

<add name="ConvertMe" type="Acme.SubAcme.ConvertMeTypeConverter"/>

</converters>

</jsonSerialization>

-->

<!--

Uncomment this line to enable the authentication service. Include requireSSL="true" if appropriate.-->

<

authenticationServiceenabled="true"requireSSL="false" />

<!--

Uncomment these lines to enable the profile service. To allow profile properties to be retrieved

and modified in Atlas applications, you need to add each property name to the setProperties and

getProperties attributes.

-->

<!--

<profileService enabled="true"

setProperties="propertyname1,propertyname2"

getProperties="propertyname1,propertyname2" />

-->

</

webServices>

</

scripting>

</

system.web.extensions>

<

system.webServer>

<

validationvalidateIntegratedModeConfiguration="false"/>

<

modules>

<

addname="ScriptModule"preCondition="integratedMode"type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

</

modules>

<

handlers>

<

removename="WebServiceHandlerFactory-Integrated"/>

<

addname="ScriptHandlerFactory"verb="*"path="*.asmx"preCondition="integratedMode"type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<

addname="ScriptHandlerFactoryAppServices"verb="*"path="*_AppService.axd"preCondition="integratedMode"type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<

addname="ScriptResource"preCondition="integratedMode"verb="GET,HEAD"path="ScriptResource.axd"type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

</

handlers>

</

system.webServer>

Note that the PipeLine extension for the configured site can be set for Integrated (default) instead of the Classic Mode.

With those two steps I was able to get a XP configured site migrated over with Ajax...

My web site is set up as an application, and it uses an application pool set up for ASP.net 2.0.

When I set that application pool to use to use the Integrated mode, I can no longer even load my website (gives 404 error).

This is crazy, this was a perfectly functioning website under XP, and "upgrading" to vista has broken it.

Is there anything in the applicationHost.config file that needs to reference AJAX? I'm at the end of my rope here, I'm about to just install XP and loose ALL my programs and setting just to get back to a usable machine!