>I checked those links and they are the same as I read yesterday.
>
>We were however able to register the client script files on 4.0 and 2.0. They had to assign something for the security. But, the Web site still does not want to interpret the .axd files.

To clear up an earlier point : Does this problem occur on *one* IIS server simply when switching file locations to a second machine or are we talking about two separate installations - i.e. are you sure you have narrowed the problem down to *just* file location?