The ASP. NET Ajax client framework failed to load, "Sys" undefined

The following issue occurs when you deploy an ASP. NET project on a Windows Server 2003 System: IIS is 6.0

Causes the menu control's picture to be displayed:

WebSite: The picture in the program is displayed as normal.
But with the Asp:treeview control of ASP. NET 2.0, the control does not display a picture

Picture properties:

Address: http://localhost/WebSite/WebResource.axd?d=41VAQHZc9t11gcfcSh8IynBrLxqhiiUYVpPeaSf8-4s1&t= 633965754543750000
Protocol: Hypertext Transfer Protocol
Type: Not available
Creation time: Not available
Modification time: Not available

Such as:

In fact, the problem is another mistake: "The ASP. NETAjax client framework failed to load," Sys"undefined" to solve this problem the picture is displayed as follows:

The first is to use the Internet Explorer tour to find the wrong place, think it is ReportViewer problem

So the search on the internet found a lot of content about that.

However, it is found that the relevant situation is "ReportViewer in IIS7 cannot be displayed" as the theme.

But my IIS is version 6.0, which is supposedly not going to happen. But with the idea of a try, they tried it the way they solved it.

Here's how to fix it:

The reason is because IIS7.5 read the Web. config change, no longer read <system.web>

<system.web>

Under IIS7.5, change to the following:

<system.webServer>

The report can be displayed correctly when Setup is complete

This way, if there is a friend who is unable to display because of IIS7.0, try the method as above.

As for me. Of course, it didn't succeed.

Because the situation here is the same as the one I showed up.

So I was conditioned to think it was webconfig. Configuration error:

The result wasted one night webconfig all changed to rot off also did not solve off ...

The next day, using the firdebug of the Firefox tour to detect

Wow, haha. The result is that the "ASP. NET Ajax client framework failed to load and" Sys "is undefined"

Well, that's the root of the problem.

So we started to search for solutions to this kind of problem ...

The solution is as follows:

Case one: No encoding is set

Add a <globalization requestencoding= "Utf-8" responseencoding= "Utf-8"/> in the <system.web> node to resolve.

Scenario Two: No references were added when publishing the site (this can happen with VS2008)

Because VS2008 takes security into account, it is not necessary to add System.Web.Extensions System.Web.Extensions.Design two DLLs before releasing the program.

Scenario Three: Webconfig configuration issues

Added in the system.web section of Web. config

can be resolved.

Scenario Four: IIS configuration issues

Review the configuration of IIS (if you are not local, contact your space service provider), look for the. Axd mappings in your application configuration, and if you do not have a new, mapped path and. aspx, be careful not to check "Checking for file existence" to determine the effect after testing. The problem should be resolved if the mapping already exists to check if the path is correct and if there is no check for the existence of the file

Basically, these are the things that are happening here.

Then I will try a method. Results.. Not a success ...

Why is it not successful? Because if it succeeds, there's no further.

And then I started thinking.

First of all

Old two server above configuration files are not changed are can be used and the patches are also played webconfig also have to change rotten out of the Internet can find the method of change Webconfig have tried and then this morning in that think yesterday must find the wrong direction because the first is that the RDLC error Later thought is the ASP. AJAX client error is not because it is on the RDLC because the patch these also have to fight and then the webconfig problem also ruled out, only the environmental problems.

The problem with the environment is only one of the problems of Axd, but the Axd side confirms that the file exists and has been removed, so I still don't know where it went wrong.

After a closer look, it's the problem here.

There is a wildcard application mapping (execution order) below the Web site properties above IIS. Here's a little more about ASPNET_ISAPI. DLL's settings.

And then this side of the "Confirm file exists" was ticked.

Then remove the. It sure did solve the problem.

And then try to publish a few new sites found on this server will automatically add one here. Also verify that the file exists is ticked. Our internal testing server does not have this one.

The problem is very pit dad. But the final sleep is solved hehe.

After discussing with the teacher, the following conclusions are drawn:

"In simple terms, ISAPI is used to handle axd, but in fact the Axd does not exist so it goes wrong and his judgment here confirms that the file exists, and that the Axd existence of ISAPI processing does not exist."

Of course, this is just a conclusion to be explored. As for right and wrong, I don't know.

If anyone knows the real reason, please tell me at the bottom thank you ...

The above ideas come from: http://www.cnblogs.com/PleaseInputEnglish/archive/2012/10/18/2729877.html's blog.

The ASP. NET Ajax client framework failed to load, "Sys" undefined