Re: ASP.NET Configuration Error under Windows Server 2003 R2

To Whom It May Concern --

I was able to resolve the problem with the help of Juan T. Llibre. I'm
posting a summary of what the problem was, and how I solved it, in case
anybody else happens across this post.

Apparently Windows 2003 R2 shipped with a beta version of Microsoft
..NET Framework 2.0 ( 2.0.50727.210 ), which Juan identified as the
source of my problems. I uninstalled both the .NET Framework 2.0 and
(just for good measure) the .NET Compact Framework 2.0 via the "Start
Menu > Control Panel > Add/Remove Programs" wizard. After that, I
rebooted my machine, then downloaded and installed the final versions
of the .NET Framework 2.0 ( 2.0.50727 ) and .NET Compact Framework 2.0
Service Pack 1 redistributables from
http://msdn2.microsoft.com/en-us/netframework/aa731542.aspx and
http://www.microsoft.com/downloads/details.aspx?familyid=0C1B0A88-59E2-4EBA-A70E-4CD851C5FCC4&displaylang=en
, respectively.

After I finished replacing the beta version of the .NET Framework v2.0
with the release version, I ran the following script to list which
items in IIS6 mapped to which versions of the .NET Framework. Below it
is the output:

===================================
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -lk

W3SVC/ 1.1.4322.2300
W3SVC/1870793688/root/ 1.1.4322.2300
W3SVC/1990904101/root/Calendars/ 1.1.4322.2300
W3SVC/1990904101/root/Tests/ 1.1.4322.2300
W3SVC/401904627/root/ 1.1.4322.2300
===================================

That showed me that all of my websites were mapped to the .NET
Framework v1.1. To fix this problem, I ran the following script, then
rechecked the mappings to make sure they were properly pointed to .NET
v2.0:

===================================
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -s
W3SVC/

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -lk

W3SVC/ 2.0.50727.0
W3SVC/1870793688/root/ 2.0.50727.0
W3SVC/1990904101/root/Calendars/ 2.0.50727.0
W3SVC/1990904101/root/Tests/ 2.0.50727.0
W3SVC/401904627/root/ 2.0.50727.0
===================================


And that's it! Suddenly my ASPX page started working, and all was
right in the world. I hope this saves somebody else some headaches,
going forward...


-= Tek Boy =-


deathtospam@xxxxxxxxx wrote:
My employer is starting to take the first steps towards migrating its
Classic ASP codebase to ASP.NET v2.0. We have a copy of our existing
website on the new Windows Server 2003 R2 test server, and everything
is running fine. However, when I create a simple "HelloWorld.aspx"
file, then browse to the page from VS.NET 2005 on the same machine, I
get the following error message:

================================================
Server Error in '/' Application.
-----------------------------------------

Runtime Error
Description: An application error occurred on the server. The current
custom error settings for this application prevent the details of the
application error from being viewed remotely (for security reasons). It
could, however, be viewed by browsers running on the local server
machine.

Details: To enable the details of this specific error message to be
viewable on remote machines, please create a <customErrors> tag within
a "web.config" configuration file located in the root directory of the
current web application. This <customErrors> tag should then have its
"mode" attribute set to "Off".
================================================


I've searched high and low on Google Groups, and all I can find are
posts that allude to some kind of permissions problem. However, I have
no idea where -- or how -- to start searching for these potential
permissions problems... or if that's even the problem. Any help that
folks could offer or suggest would be greatly appreciated... thanks in
advance!


-= Tek Boy =-

.

Relevant Pages

  • Re: ASP.NET Configuration Error under Windows Server 2003 R2
    ... been released with a beta version of tyhe .Net Framework. ... Juan T. Llibre, asp.net MVP ... website on the new Windows Server 2003 R2 test server, ... This <customErrors> tag should then have its ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Object reference not set to an instance of an object
    ... I already know my code fails on the server. ... Does the Web Matrix tell you HOW to make the changes? ... you can also ask your AT&T ISP whether they can support ASP.NET ... AT&T - does not have .Net Framework 2.0 installed. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ASP.NET Configuration Error under Windows Server 2003 R2
    ... Did you upgrade the .Net Framework version on R2 to the Release version? ... website on the new Windows Server 2003 R2 test server, ... To enable the details of this specific error message to be ... This <customErrors> tag should then have its ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: 2008 TS Gets "Access Denied" When Printing to Redirected Printer
    ... The clients need not just .NET Framework 3.0, ... MCSE, CCEA, Microsoft MVP - Terminal Server ... The clients can connect to the server and run their app -- they ... Easy print driver is, indeed, the one Windows will try and use. ...
    (microsoft.public.windows.terminal_services)
  • Re: Ive broken Sharepoint V2.0 by running aspnet_regiis.exe -i
    ... tab in the Properties window. ... attempts to open a webpage on my server with a close button on it. ... However I had a number of choices re which net framework directory to run ... This didn't resolve my GFI issue but did break my sharepoint. ...
    (microsoft.public.windows.server.sbs)
Loading