AJAX Toolkit Documentation on Vista 500.19
am 26.07.2007 03:26:02 von TonySu
Installed the documentation following the install instructions to the letter
although the steps seem to have been written for IIS6 and earlier.
A virtual directory is created which points to the folder containing the
website files including its own pre-configured web.config. The documentation
says that if the location of the directory and an empty folder for the
databases to be created are exactly as described, no modification should be
necessary to the web.config.
Returning the error at the end of this post on the webpage when attempting
to access the page "http://localhost/AJAXdocs" "As Administrator" where I
mapped the virtual directory "AJAXdocs" to the specified files.
Vista's Default website's web.config is default and mostly empty, so I don't
see anything to do there unless a default setting blocks a "child" virtual
directory web.config. I also don't see anything recognizable to modify
browsing the various IIS7 objects.
I assume that the web.config for the AJAX documentation be suitable
for a virtual directory since the instructions for deployment is that
configuration. Maybe should somethig be added to the Default Website's
web.config or is there an IIS7 setting I've missed?
TIA,
--
Tony Su
www.su-networking.com
ISA
SBS
Enterprise Mobile Solutions Architect
HTTP Error 500.19 - Internal Server Error
Description: The requested page cannot be accessed because the related
configuration data for the page is invalid.
Error Code: 0x80070021
Notification: BeginRequest
Module: IIS Web Core
Requested URL: http://localhost:80/ajaxdocs
Physical Path: D:\Inetpub\AspNet_AJAX_Documentation
Logon User: Not yet determined
Logon Method: Not yet determined
Handler: Not yet determined
Config Error: This configuration section cannot be used at this path. This
happens when the section is locked at a parent level. Locking is either by
default (overrideModeDefault="Deny"), or set explicitly by a location tag
with overrideMode="Deny" or the legacy allowOverride="false".
Config File: \\?\D:\Inetpub\AspNet_AJAX_Documentation\web.config
Config Source: 145:
146:
147:
Re: AJAX Toolkit Documentation on Vista 500.19
am 27.07.2007 12:13:56 von David Wang
On Jul 25, 6:26 pm, Tony Su wrote:
> Installed the documentation following the install instructions to the letter
> although the steps seem to have been written for IIS6 and earlier.
>
> A virtual directory is created which points to the folder containing the
> website files including its own pre-configured web.config. The documentation
> says that if the location of the directory and an empty folder for the
> databases to be created are exactly as described, no modification should be
> necessary to the web.config.
>
> Returning the error at the end of this post on the webpage when attempting
> to access the page "http://localhost/AJAXdocs" "As Administrator" where I
> mapped the virtual directory "AJAXdocs" to the specified files.
>
> Vista's Default website's web.config is default and mostly empty, so I don't
> see anything to do there unless a default setting blocks a "child" virtual
> directory web.config. I also don't see anything recognizable to modify
> browsing the various IIS7 objects.
>
> I assume that the web.config for the AJAX documentation be suitable
> for a virtual directory since the instructions for deployment is that
> configuration. Maybe should somethig be added to the Default Website's
> web.config or is there an IIS7 setting I've missed?
>
> TIA,
> --
> Tony Suwww.su-networking.com
> ISA
> SBS
> Enterprise Mobile Solutions Architect
>
> HTTP Error 500.19 - Internal Server Error
> Description: The requested page cannot be accessed because the related
> configuration data for the page is invalid.
>
> Error Code: 0x80070021
>
> Notification: BeginRequest
>
> Module: IIS Web Core
>
> Requested URL:http://localhost:80/ajaxdocs
>
> Physical Path: D:\Inetpub\AspNet_AJAX_Documentation
>
> Logon User: Not yet determined
>
> Logon Method: Not yet determined
>
> Handler: Not yet determined
>
> Config Error: This configuration section cannot be used at this path. This
> happens when the section is locked at a parent level. Locking is either by
> default (overrideModeDefault="Deny"), or set explicitly by a location tag
> with overrideMode="Deny" or the legacy allowOverride="false".
>
> Config File: \\?\D:\Inetpub\AspNet_AJAX_Documentation\web.config
>
> Config Source: 145:
> 146:
> 147:
If you have questions about AJAX deployment, then you should ask the
question in an AJAX-related forum -- this is actually not a good place
to ask questions related to AJAX. Why? Suppose you had questions about
deploying the application "Comet" on Windows -- would you go to a
forum about general Windows questions or Comet questions?
Now, it happens that the IIS7 custom error tells you exactly what is
wrong and how to fix it. Maybe a little cryptic, but its diagnosis is
definitely spot on.
You won't be able to add anything to Default Web Site's web.config to
affect this -- by-design. If a delegated web.config can change its
security settings, it's not very secure, is it? Like-wise, there
really isn't a missed IIS7 setting. I think the documentation was
never verified against the released version of Vista/IIS7.
The web.config from AJAX is trying to remove an legacy WebServices
handler (presumably it is going to define a new one). However, that
handler is locked by default and there's a bug in AJAX documentation
in how to deal with it.
I don't know what the *correct* thing to do to get AJAX running since
I don't know AJAX, but to get rid of this error you will have to find
the handler definition for WebServiceHandlerFactory-ISAPI-2.0 in
%windir%\System32\inetsrv\config\applicationHost.config and get rid of
the "Locked" attribute on it. I believe section is
delegatable by default (i.e. overrideMode=allow)
It sounds like the instructions were written against an earlier, pre-
release version of Vista and IIS7. The handlers weren't locked down
until the very end of Vista release.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//