all posts

ASP.NET AJAX - Sys.Debug.isDebug Javascript Error

Published to Blog on 23 Jan 2007

After updating to ASP.NET AJAX 1.0 you may get the following Javascript Error (especially for pages making use of animation):

“Sys.Debug.IsDebug is null or not an object”

or something else about Sys.Debug, depending on your browser of choice.

The issue is that the Javascript files being returned by IIS are cached copies from the previous release and are no longer valid with the code from the new release.

The fix is to run iisreset (or manually stop and restart IIS).

UPDATE: My cohort, Kyle Beyer, has put together a nice summary of the breaking changes for ASP.NET AJAX 1.0 RTM.

Dan Hounshell
Web geek, nerd, amateur maker. Likes: apis, node, motorcycles, sports, chickens, watches, food, Nashville, Savannah, Cincinnati and family.
Dan Hounshell on Twitter

  • On 24 Jan 2007 "Radas"" said:
    Thanks man ! Right on time. It has fixed my issue.
  • On 24 Jan 2007 """ said:
    Radas, glad to be of service.
  • On 24 Jan 2007 "cozta"" said:
    Dan, actually one has to clear the temporary files as well.
  • On 25 Jan 2007 """ said:
    Cozta, by temporary files, do you mean ASP.NET temporary files on the server? Or that the user has to clear temporary files in the their browser? I have seen that the latter is true - a Ctrl-F5 will do the trick.
  • On 17 Apr 2007 "Kenn"" said:
    I'm quite confused... I have 2 servers... Both run IIS. I can publish from VS2005 (all SP'd up) to one server and the animations play fine. The other throws the isdebug error. I've followed all the recommendations to date 1. Clear the Temp ASP.NET files at the server 2. Clear the temp files at the client 3. Ensure the AJAX install is current at the server No matter what I try, I can't lose the error on server one. I even set up a vanilla IIS on a different server and it published and worked like a champ. What else can I check/look for?
  • On 18 Apr 2007 """ said:
    Kenn, sounds like you've covered all the bases. I didn't really have all that much trouble correcting the issue. Basically, running IIS reset did it for me. With the symptoms that you have described, it sounds like the server you are having issues with does not have the newest AJAX bits installed.
  • On 18 Apr 2007 "Kenn"" said:
    Thanks for the quick response. Maybe I've missed an instruction somewhere on installing the correct bits. Other than having the latest framework on the server and installing the extented toolkit, is there something else I can check to ensure all is as it should be?
  • On 18 Apr 2007 """ said:
    Kenn, you can check "Add or Remove Programs". You should have at least 2 new components installed http// The ASP.NET AJAX Extensions 1.0 The Futures January CTP You may also have the Sample Applications if you installed those. Those will all be listed in Add/Remove programs. Also, make sure that you uninstalled the previous versions of the extensions and the futures. I always uninstalled the previous before installing the new, so I don't know if it gives you any kind of warning or otherwise makes you uninstall the previous. If all else fails, you may want to uninstall the Ajax extensions and futures and try re-installing. I did have an issue once where the extensions seemed to be not working correctly and uninstall/reinstall fixed it. That was with an earlier version, though.
  • On 19 Apr 2007 "kumar"" said:
    this works for me, thanks.
  • On 25 Apr 2007 "Shail"" said:
    Thanks, It worked for me also
  • On 10 Aug 2007 "Jason Short"" said:
    I just wanted to add that there are TWO 1.0 MSI's from Microsoft. I was experiencing the same problem listed above and nothing would fix it on one of my servers. I uninstalled / reinstalled and same problem still existed. So on a total lark I redownloaded the 1.0 AJAX from Microsoft (I reinstalled using the same one that was already on the machine). They are not the same size. Both are called 1.0... Hmmm. One is about 70KB larger than the other. My original download was from February 2007, I just downloaded again (Aug 2007) and 1.0 is different! Wierd, but the "current" 1.0 did fix my problem. So if you have 1.0 but are still getting this error uninstall, redownload, and reinstall.