Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jul 24, 2009 03:40 PM by Thomas Thayil
Oct 30, 2006 03:12 PM|LINK
I know I've seen posts similar to this before and have tried a few things to no avail. Is it a configuration / compatibility issue? Is is simply a bug that needs ironing out before release?
I'm using Windows 2000 / IIS5 / IE 6.0.2800. Getting on a bit I know but we have no choice. I realise this is unsupported, does this also mean incompatible in this case?
I have tried navigating to the AXD files referenced by the source - and this works fine.
Also, if I clear the temporary internet files and refresh, I don't get it on the next round trip. Any future page refreshes bring up the error again.
CTRL-F5 also stops the error.
Any help would be hugely appreciated.
Oct 30, 2006 08:20 PM|LINK
in internet explorer, go to tools, internet options. clcik the settings button. check "every visit to the page and then drag the slider all the way to 1. Then click OK. Click delete files, then OK. Go to the advanced tab, and uncheck "Show friendly http
error messages" and "show friendly urls". then click ok.
try again, and see if you get the same error.
Oct 30, 2006 10:07 PM|LINK
Sys undefined means that you're not getting the client side files loaded on your browser.
btw, windows 200 server is supported. if you searh this forum, you'll find a post by a team member where he says that the docs are wrong about that.
Oct 31, 2006 02:46 AM|LINK
if you are using Beta1 release of Atlas Framework Sys is now moved to the Preview name space. Ensure your script manager tag has a scripts section as follows:
<asp:ScriptManager ID="ScriptManager1" runat="server">
<asp:ScriptReference Assembly="Microsoft.Web.Preview" Name="Microsoft.Web.Resources.ScriptLibrary.PreviewScript.js" />
<asp:ScriptReference Assembly="Microsoft.Web.Preview" Name="Microsoft.Web.Resources.ScriptLibrary.PreviewGlitz.js" />
<asp:ScriptReference Assembly="Microsoft.Web.Preview" Name="Microsoft.Web.Resources.ScriptLibrary.PreviewDragDrop.js" />
Hope if helps
Nov 07, 2006 10:48 AM|LINK
I've had the same problem yet neither of the steps seem to have resolved my problems.
It's mainly for client testing purposes, as in my development machine is XP but certain of my clients are running I.E 5.5 and Win 2000 etc. As a side note are there any resources as to what the requirements are client side for browser version and OS?
Nov 07, 2006 01:56 PM|LINK
I had the same error. Turns out I had created a normal "ASP.NET Web Site" and not an "ASP.NET
Ajax Enabled Web Site". Not sure what the difference is, but the 'sys is undefined' went away with the Ajax Enabled site.
Hope it helps,
Nov 07, 2006 02:17 PM|LINK
Try this from the migration guide:
In the Web.config file, add the following entry in the
<httpHandlers> element for the new ScriptResourceHandler object in Beta 2:
The release notes state the following:
This handler requires an entry in the web.config file. If the entry is missing, you might see the following error:
'Sys' is undefine.
I hope this helps!
Nov 07, 2006 02:45 PM|LINK
Good one, ncipollina - this "ajax-enabled" my existing projects. Thanks!
Nov 08, 2006 05:25 AM|LINK
I had the handler defined but still got the error but found a fix, read it at
Nov 08, 2006 12:15 PM|LINK
When I create a standard Asp.Net Web Site and then try to use ajax controls I get the same problem.
However, when I create a project from Ajax Control Toolkit Web Site the problem dissapears.
I compared 2 newly created sites and found that they have totally different web.config . In addition,