U R G E N T please help.. 1.1 redistributable installation in production

  • Thread starter Thread starter alien2_51
  • Start date Start date
A

alien2_51

We have a production server running 1.0 ASP.NET apps, the aspnet_wp process
runs under the system account, we installed the redistributable framework
1.1 package and the apps fail with this error.

Access denied to 'E:\InetPub\mncapp\CustomerRelations\'. Failed to start
monitoring file changes.

Curiously at the bottom of the stack trace was this..

Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
Version:1.1.4322.573.

I would have expected it to be version 1.0.3705.. So this sheds light on the
access denied error, the 1.0 app is now being run under the 1.1 after the
redistributable installation, this is because I have not yet changed the
processmodel section of the machine config for 1.1 version of framework the
aspnet_wp will still be running under the machine account, which does not
have access to the application directory.

My Questions:
Is it possible to have 1.0 IL jit-ted to run under the 1.1 framework, reason
I ask this is the redistributable alters the current config of 1.0 apps to
run under 1.1...?
If I'm running a 1.0 ASP.NET app and a 1.1 ASP.NET app on the same machine
will I have two aspnet_wp's running simultaneously...?
How do I setup a virtual directory to run under a particular version of the
framework...?

TIA..
 
Thanks, I appreciate the reply... I ran this on my development machine I
think it's cool, I don't think my systems administrators would trust running
this code on their servers without having looked at the source code... Do
you know how this tool is overriding the framework version for each
virtual....?

Regards,

Dan
 
alien2_51 said:
Thanks, I appreciate the reply... I ran this on my development machine I
think it's cool, I don't think my systems administrators would trust running
this code on their servers without having looked at the source code... Do
you know how this tool is overriding the framework version for each
virtual....?
Click to expand...

Although it is possible to run both 1.0 and 1.1 framework apps side-by-side,
it is highly preferable to test and run your 1.0 apps under the 1.1
framework.

Just uninstall the 1.0 framework, leaving only the 1.1 framework. All 1.0
will just run using the 1.1 libraries and the 1.1 JIT'er.

David
 
Thanks for the help.... Just for the record, I've answered my questions
below...

alien2_51 said:
We have a production server running 1.0 ASP.NET apps, the aspnet_wp process
runs under the system account, we installed the redistributable framework
1.1 package and the apps fail with this error.

Access denied to 'E:\InetPub\mncapp\CustomerRelations\'. Failed to start
monitoring file changes.

Curiously at the bottom of the stack trace was this..

Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
Version:1.1.4322.573.

I would have expected it to be version 1.0.3705.. So this sheds light on the
access denied error, the 1.0 app is now being run under the 1.1 after the
redistributable installation, this is because I have not yet changed the
processmodel section of the machine config for 1.1 version of framework the
aspnet_wp will still be running under the machine account, which does not
have access to the application directory.

My Questions:
Is it possible to have 1.0 IL jit-ted to run under the 1.1 framework, reason
I ask this is the redistributable alters the current config of 1.0 apps to
run under 1.1...?
Click to expand...
Yes, totally possible most likely probable
If I'm running a 1.0 ASP.NET app and a 1.1 ASP.NET app on the same machine
will I have two aspnet_wp's running simultaneously...? Yes

How do I setup a virtual directory to run under a particular version of the
framework...?
Click to expand...
something like this...
''for 1.0 framework...

C:\WINNT\MICROSOFT.NET\FRAMEWORK\V1.0.3705\aspnet_regiis.exe -s
"w3svc/1/Root/WarrantyReserve"
''for 1.1 framework....

C:\WINNT\MICROSOFT.NET\FRAMEWORK\V1.1.4322\aspnet_regiis.exe -s
"w3svc/1/Root/WarrantyReserve"
 
Your post (aspnet_regiis) is exactly what that tool does for you, but it
gives you a nice UI.
-mike
MVP
 
Back
Top