Error in Path for .NET Script Mappings

I'm not sure if this is the right place to post this issue; If not, please
forgive me and direct to the correct forum... I've run into an issue and it
may have happened after a SP update for .NET 2.0. We are running .NET
version side by side and noticed that the .NET 2.0 sites were running into an
issue where they were not loading... We have since found that the script
mappings for all .NET 2.0 sites are pointing to an invalid path... (see
below...).

2.0.50727.0 Valid
C:\WINNT\Microsoft.NET\Framework\v2.0.50727\\asp
net_isapi.dll

There are 2 slashes in the path just before the dll is displayed. Does
anyone know where this default setting is set? I am really not looking
forward to setting this on an individual site basis... Can anyone help...

thks...

Re: Error in Path for .NET Script Mappings

i'll take a stab at it.... i assume this is a 2k3 server with IIS 6..

open up IIS manager and go to the web service extensions and find the entry
for 2.0, right click and do properties. select the Required Files tab and
you'll see the entry there. you cant edit it but you can remove/add it and
then just verify that its "allowed" and you should be good to go.

let me know how that works out for you.

Justin

"SJ" wrote in message
news:95D7CAB2-C231-4663-8FFA-5AB907F3BDC4@microsoft.com...
> I'm not sure if this is the right place to post this issue; If not, please
> forgive me and direct to the correct forum... I've run into an issue and
> it
> may have happened after a SP update for .NET 2.0. We are running .NET
> version side by side and noticed that the .NET 2.0 sites were running into
> an
> issue where they were not loading... We have since found that the script
> mappings for all .NET 2.0 sites are pointing to an invalid path... (see
> below...).
>
> 2.0.50727.0 Valid
> C:\WINNT\Microsoft.NET\Framework\v2.0.50727\\asp
> net_isapi.dll
>
> There are 2 slashes in the path just before the dll is displayed. Does
> anyone know where this default setting is set? I am really not looking
> forward to setting this on an individual site basis... Can anyone help...
>
> thks...

RE: Error in Path for .NET Script Mappings

Justin thanks for your response...I did find the string...it was in the
registry... hlm\software\microsoft\asp.net\2.0.50727.0\dllfullpath. It was
actually in the registry as
C:\WINNT\Microsoft.NET\Framework\v2.0.50727\\aspnet_isapi.dl l. Therefore,
every time a new web was added using the .net 2.0 framework, the script
mappings would have the incorrect path... I do believe this happened after a
..net 2.0 SP update.

S.J.

"SJ" wrote:

> I'm not sure if this is the right place to post this issue; If not, please
> forgive me and direct to the correct forum... I've run into an issue and it
> may have happened after a SP update for .NET 2.0. We are running .NET
> version side by side and noticed that the .NET 2.0 sites were running into an
> issue where they were not loading... We have since found that the script
> mappings for all .NET 2.0 sites are pointing to an invalid path... (see
> below...).
>
> 2.0.50727.0 Valid
> C:\WINNT\Microsoft.NET\Framework\v2.0.50727\\asp
> net_isapi.dll
>
> There are 2 slashes in the path just before the dll is displayed. Does
> anyone know where this default setting is set? I am really not looking
> forward to setting this on an individual site basis... Can anyone help...
>
> thks...

Re: Error in Path for .NET Script Mappings

this isnt the first time i had seen this. I figured a reg search would find
what you needed but i think the location i had listed was the gui way to
change this value, either way, your off and running.

Justin

"SJ" wrote in message
news:8BFE22A3-9127-4195-9885-642CA5774032@microsoft.com...
> Justin thanks for your response...I did find the string...it was in the
> registry... hlm\software\microsoft\asp.net\2.0.50727.0\dllfullpath. It
> was
> actually in the registry as
> C:\WINNT\Microsoft.NET\Framework\v2.0.50727\\aspnet_isapi.dl l. Therefore,
> every time a new web was added using the .net 2.0 framework, the script
> mappings would have the incorrect path... I do believe this happened after
> a
> .net 2.0 SP update.
>
> S.J.
>
> "SJ" wrote:
>
>> I'm not sure if this is the right place to post this issue; If not,
>> please
>> forgive me and direct to the correct forum... I've run into an issue and
>> it
>> may have happened after a SP update for .NET 2.0. We are running .NET
>> version side by side and noticed that the .NET 2.0 sites were running
>> into an
>> issue where they were not loading... We have since found that the script
>> mappings for all .NET 2.0 sites are pointing to an invalid path... (see
>> below...).
>>
>> 2.0.50727.0 Valid
>> C:\WINNT\Microsoft.NET\Framework\v2.0.50727\\asp
>> net_isapi.dll
>>
>> There are 2 slashes in the path just before the dll is displayed. Does
>> anyone know where this default setting is set? I am really not looking
>> forward to setting this on an individual site basis... Can anyone
>> help...
>>
>> thks...