yep..I think what jody says makes sense. As I had originally posted the IE KB patch did fix my issues. Point to note is that I had followed the following sequence:

1. Uninstalled Beta1.

2. Installed Beta2

3. Installed November CTP

RAM 

I'm afraid to say that I think I have given up with these Ajax controls in their current state as I have spent many hours researching the problem to get nowhere. I will wait for the release and hope the developers sort this most annoying issue out.

I have managed to sort the problem out locally but the second I put it on the server all hell breaks loose. I can bring the SampleWebsite up using the servers local browser, however it takes so long to load you may as well make a cup of tea. If I try and then access it using the development machine's browser, it never comes up and crashes IIS on the server.

I think these controls will be brilliant when they are finished, I just have to cross my fingers and hope. Thanks everyone for attempting to contribute to this thread, I just wish the resolutions to it were a bit more consistent.

Regards

Aurorasi,

Apologies, I was not as clear as I should have been. I was referring to developing new ASP.NET AJAX controls. In this case, fundamental syntax errors can cause this issue.

D

To hazard a guess, there's probably only one reason (already mentioned) why this 'Sys is undefined' issue can happen: the existing code tries to call javascript objects and members before they have fully loaded in the page. Simple as that. It seems unlikely that the issues relate to patches, etc. Having developed a number (+-8) custom AJAX-enabled controls using this framework I know that event sequence is vital (as in all ASP dev). Perhaps the ajax.net chaps will give feedback on this.

Which brings up another related issue... why does there not seem to be a way to check whether all necessary scripts in the page have loaded? Surely there are many development scenarios will call for this (I'm currently experiencing one!). Am I missing something on the ScriptManager? Another discussion thread perhaps...

Dragonman:

To hazard a guess, there's probably only one reason (already mentioned) why this 'Sys is undefined' issue can happen: the existing code tries to call javascript objects and members before they have fully loaded in the page. Simple as that. It seems unlikely that the issues relate to patches, etc. Having developed a number (+-8) custom AJAX-enabled controls using this framework I know that event sequence is vital (as in all ASP dev). Perhaps the ajax.net chaps will give feedback on this.

Which brings up another related issue... why does there not seem to be a way to check whether all necessary scripts in the page have loaded? Surely there are many development scenarios will call for this (I'm currently experiencing one!). Am I missing something on the ScriptManager? Another discussion thread perhaps...

 

Thanks for explaining Dragonman however I am finding it very hard to believe that there is simply one cause of this error due to the inconsistency with the resolutions. Anything from web.config editing to local IE patches resolves this one and it seems as though my server needs a resolution that nobody has discovered yet. The fact that it can load very very slowly without error on the servers local browser kind of tells me that the required libraries are loading completely, the question is why the stupidly long delay? and secondly, why does it not work off a remote machines browser when accessing the same page on the same server?

The routine is fundamental to the page working correctly, it has been commented before on here. However, that being the sole reason for this error is very much unbelievable to me simply from the discoveries in this thread alone.

Thanks again for your help, it's appreciated.
 

I was getting the Sys undefined error with beta 2. Then last night I went thru the following sequence, and everything appears to be working.

- Uninstall Beta2 from dev machine
- Install Beta1 on dev machine
- Uninstall Beta2 from server
- Install Beta1 on server
- Change web.config and references in project to work with Beta1
- Got everything working again with Beta1

Then repeat the process above to remove Beta1 and Install Beta2. Changed references and web.config to work with Beta2. And now Beta2 works fine. Problem for me seems to have been in the uninstall/install and references/config.

Someone asked about errors in Fiddler.  Here is what I get:

The error is on: ../WebResource.axd?d=jyWCtqRVPNi7Vb1OQ8LG0u_bTKIQJXL3ajmxosbD103_-dBoKCyka7ps8IsPCyKW5AdRIV9hUepA3dlMRjZpV48KQ09duB4XZjpj7ozCwOMnqkPDp5gIkMg0oxE7zh7Z4T0qLcgBa2DBNROWaRfQc0e0KjIRcKhk0MRE7W3slRQ1&t=632987789584049531

see is the "Sys. is undefined" error.

hello.

are you using web farms? i think that is traditional error in those scenarios:

 http://forums.asp.net/thread/1237268.aspx

http://forums.asp.net/thread/1389771.aspx 

hello.

using any thrid product on the web service:

http://groups.google.com/group/microsoft.public.dotnet.framework.aspnet/browse_thread/thread/5208e50dd8593f46/4b3b33684628d625?lnk=st&q=%5BCryptographicException%5D%3A+Padding+is+invalid+and+cannot+be+removed.+no+web+farm&rnum=3&hl=en#4b3b33684628d625 

OK, I found my problem.  Doubt that anyone else had this same issue - since it was sort of stupid - but thought I would post just in case.  In the page load of many of our modal web forms, this code has to be placed in the page_init so that the page knows where to post back to (essentially itself):

        Dim x As New System.Web.UI.HtmlControls.HtmlGenericControl
        x.TagName = "base"
        x.Attributes.Add("target", "_self")
        x.Attributes.Add("href", "http://" & Master.WebServer & "/website/page.aspx")
        Master.Page.Header.Controls.Add(x)

When this is in development, Master.WebServer (our public prop off the master page) is set to "localhost".  So when we moved this to a test server and didn't change this property, the served page was looking on the local/client computer for a WebResource.axd file and when it couldn't find the correct one (which was why Fiddler was reporting an error from System.Security.Crypto) it didn't load that file.  I'm pretty sure that is why the reference to sys.webforms.pagerequestmanager couldn't initialize properly.

This tells me that many people are on the right path here.  People may want to look at reasons their webresource.axd file isn't processed (security, *server* ;-), machineKey, etc).  Any of these could be causing a problem.

Hi,

    If you were installed AJAX Extensions Beta2, then go to installation path, in that path you can find README.txt file.

Please go through that file, you can solve that problem easily if you read that file.

Not only this error, in that text file they are showed some bugs and how to clear that bugs.

 Thanks,

 Pradeep

pradpb999:

Hi,

    If you were installed AJAX Extensions Beta2, then go to installation path, in that path you can find README.txt file.

Please go through that file, you can solve that problem easily if you read that file.

Not only this error, in that text file they are showed some bugs and how to clear that bugs.

 Thanks,

 Pradeep

With all due respect mate, have you even read the replies in this thread? We have all followed the steps in the readme.txt file and it has NOT resolved the problem, this is why the thread has been created and has many different resolutions.

 
Regards 

Hi All,

I used to get the same message. My website was an AJAX enabled website. I had a ScriptManager on the page. I added a RoundedCornersExtender and then I got the error message.

I opened up the AjaxControlToolkit solution. Copy/Paste the <system.web> section from the web.config of the SampleWebSite to my own web.config and it worked. Here's that section of my config file.

<system.web>

<pages>

<controls>

<add tagPrefix="asp" namespace="Microsoft.Web.UI" assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<add tagPrefix="asp" namespace="Microsoft.Web.UI.Controls" assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

</controls>

<tagMapping>

<add tagType="System.Web.UI.WebControls.CompareValidator" mappedTagType="Microsoft.Web.UI.Compatibility.CompareValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<add tagType="System.Web.UI.WebControls.CustomValidator" mappedTagType="Microsoft.Web.UI.Compatibility.CustomValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<add tagType="System.Web.UI.WebControls.RangeValidator" mappedTagType="Microsoft.Web.UI.Compatibility.RangeValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<add tagType="System.Web.UI.WebControls.RegularExpressionValidator" mappedTagType="Microsoft.Web.UI.Compatibility.RegularExpressionValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<add tagType="System.Web.UI.WebControls.RequiredFieldValidator" mappedTagType="Microsoft.Web.UI.Compatibility.RequiredFieldValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<add tagType="System.Web.UI.WebControls.ValidationSummary" mappedTagType="Microsoft.Web.UI.Compatibility.ValidationSummary, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

</tagMapping>

</pages>

<!--

Set compilation debug="true" to insert debugging

symbols into the compiled page. Because this

affects performance, set this value to true only

during development.

-->

<compilation debug="true">

<assemblies>

<add assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<add assembly="Microsoft.Web.Extensions.Design, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

<add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>

<add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

<add assembly="System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

<add assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

<add assembly="System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>

<add assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>

<add assembly="System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

<add assembly="System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>

<add assembly="System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>

</assemblies>

</compilation>

<httpHandlers>

<remove verb="*" path="*.asmx"/>

<add verb="*" path="*.asmx" validate="false" type="Microsoft.Web.Script.Services.ScriptHandlerFactory, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

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

</httpHandlers>

<httpModules>

<add name="WebResourceCompression" type="Microsoft.Web.Handlers.WebResourceCompressionModule, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<add name="ScriptModule" type="Microsoft.Web.UI.ScriptModule, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

</httpModules>

</system.web>

U Can't let every client uninstall the patch,and I'm not counting on the beta 2 version.

I just hope it can be fixed in the release version.

I would rather use the MagicAjax now,At least there isn't so much bug!