473,248 Members | 1,878 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,248 software developers and data experts.

ASP.NET Configuration Error under Windows Server 2003 R2

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 <customErrorstag within
a "web.config" configuration file located in the root directory of the
current web application. This <customErrorstag 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 =-

Oct 31 '06 #1
10 2121
Did you upgrade the .Net Framework version on R2 to the Release version ?

The .Net Framework's Release version number is 2.0.50727.42
R2's version number is 2.0.50727.210

Make sure you have the Release version running.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<de*********@gmail.comwrote in message
news:11*********************@h48g2000cwc.googlegro ups.com...
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 <customErrorstag within
a "web.config" configuration file located in the root directory of the
current web application. This <customErrorstag 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 =-

Oct 31 '06 #2
Juan --

Where should I be checking to see if I'm running the release version of
..NET v2.0? If I'm supposed to be looking in the "ASP.NET version"
field inside IIS6's "ASP.NET" tab, it says "1.1.4322". However, the
"File location" field is pointing to the web.config file in the
"v2.0.50727" directory...
-= Tek Boy =-
Juan T. Llibre wrote:
Did you upgrade the .Net Framework version on R2 to the Release version ?

The .Net Framework's Release version number is 2.0.50727.42
R2's version number is 2.0.50727.210

Make sure you have the Release version running.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<de*********@gmail.comwrote in message
news:11*********************@h48g2000cwc.googlegro ups.com...
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 <customErrorstag within
a "web.config" configuration file located in the root directory of the
current web application. This <customErrorstag 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 =-
Oct 31 '06 #3
Juan --

I believe so. At the bottom of the ASPX page (and below the error
messages), I see the following text:

================================================
"Version Information: Microsoft .NET Framework Version:2.0.50727.42;
ASP.NET Version:2.0.50727.210"
================================================
-= Tek Boy =-
Juan T. Llibre wrote:
Did you upgrade the .Net Framework version on R2 to the Release version ?

The .Net Framework's Release version number is 2.0.50727.42
R2's version number is 2.0.50727.210

Make sure you have the Release version running.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<de*********@gmail.comwrote in message
news:11*********************@h48g2000cwc.googlegro ups.com...
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 <customErrorstag within
a "web.config" configuration file located in the root directory of the
current web application. This <customErrorstag 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 =-
Oct 31 '06 #4
Yes, I thought so.

It's a common problem with R2, which I think shouldn't have
been released with a beta version of tyhe .Net Framework.

Only a few more builds and R2 could have gone out with the release version.

You need to download, at least, the release version of the redistributable.

If you've got enough bandwidth, go for the SDK. The developer samples are worth it.

http://msdn2.microsoft.com/en-us/net.../aa731542.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<de*********@gmail.comwrote in message
news:11*********************@e64g2000cwd.googlegro ups.com...
Juan --

I believe so. At the bottom of the ASPX page (and below the error
messages), I see the following text:

================================================
"Version Information: Microsoft .NET Framework Version:2.0.50727.42;
ASP.NET Version:2.0.50727.210"
================================================
-= Tek Boy =-
Juan T. Llibre wrote:
Did you upgrade the .Net Framework version on R2 to the Release version ?

The .Net Framework's Release version number is 2.0.50727.42
R2's version number is 2.0.50727.210

Make sure you have the Release version running.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<de*********@gmail.comwrote in message
news:11*********************@h48g2000cwc.googlegro ups.com...
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 <customErrorstag within
a "web.config" configuration file located in the root directory of the
current web application. This <customErrorstag 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 =-

Nov 1 '06 #5
Juan --

We don't have enough daytime bandwidth, and that link you posted said
the SDK comes with VS.NET 2005 (which is already installed on the
server), so I downloaded the normal .NET v2.0 EXE instead.

However, the problem still occurred after I installed (repaired) .NET
v2.0 and rebooted. What's the specific sequence of events I need to
follow to upgrade from the R2 beta version to the release version of
..NET v2.0? Also, how will I know if the upgrade was successful? Sorry
to bother you with all the minutiae... I certainly do appreciate your
help.
-= Tek Boy =-

Juan T. Llibre wrote:
Yes, I thought so.

It's a common problem with R2, which I think shouldn't have
been released with a beta version of tyhe .Net Framework.

Only a few more builds and R2 could have gone out with the release version.

You need to download, at least, the release version of the redistributable.

If you've got enough bandwidth, go for the SDK. The developer samples areworth it.

http://msdn2.microsoft.com/en-us/net.../aa731542.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<de*********@gmail.comwrote in message
news:11*********************@e64g2000cwd.googlegro ups.com...
Juan --

I believe so. At the bottom of the ASPX page (and below the error
messages), I see the following text:

================================================
"Version Information: Microsoft .NET Framework Version:2.0.50727.42;
ASP.NET Version:2.0.50727.210"
================================================
-= Tek Boy =-
Juan T. Llibre wrote:
Did you upgrade the .Net Framework version on R2 to the Release version?

The .Net Framework's Release version number is 2.0.50727.42
R2's version number is 2.0.50727.210

Make sure you have the Release version running.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<de*********@gmail.comwrote in message
news:11*********************@h48g2000cwc.googlegro ups.com...
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 <customErrorstag within
a "web.config" configuration file located in the root directory of the
current web application. This <customErrorstag 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 =-
>
Nov 1 '06 #6
re:
how will I know if the upgrade was successful?
Run aspnet_regiis -lv from the .Net framework 2.0's directory
( Drive:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 )

That will list all the installed versions.

If version 2.0.50727.210 is still registered, either run the uninstall tool found here :
http://msdn.microsoft.com/vstudio/su...l/default.aspx

....or uninstall manually and then reinstall the release version.
The instructions for a manual uninstall are there, too.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================

<de*********@gmail.comwrote in message
news:11**********************@m7g2000cwm.googlegro ups.com...
Juan --

We don't have enough daytime bandwidth, and that link you posted said
the SDK comes with VS.NET 2005 (which is already installed on the
server), so I downloaded the normal .NET v2.0 EXE instead.

However, the problem still occurred after I installed (repaired) .NET
v2.0 and rebooted. What's the specific sequence of events I need to
follow to upgrade from the R2 beta version to the release version of
..NET v2.0? Also, how will I know if the upgrade was successful? Sorry
to bother you with all the minutiae... I certainly do appreciate your
help.
-= Tek Boy =-

Juan T. Llibre wrote:
Yes, I thought so.

It's a common problem with R2, which I think shouldn't have
been released with a beta version of tyhe .Net Framework.

Only a few more builds and R2 could have gone out with the release version.

You need to download, at least, the release version of the redistributable.

If you've got enough bandwidth, go for the SDK. The developer samples are worth it.

http://msdn2.microsoft.com/en-us/net.../aa731542.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<de*********@gmail.comwrote in message
news:11*********************@e64g2000cwd.googlegro ups.com...
Juan --

I believe so. At the bottom of the ASPX page (and below the error
messages), I see the following text:

================================================
"Version Information: Microsoft .NET Framework Version:2.0.50727.42;
ASP.NET Version:2.0.50727.210"
================================================
-= Tek Boy =-
Juan T. Llibre wrote:
Did you upgrade the .Net Framework version on R2 to the Release version ?

The .Net Framework's Release version number is 2.0.50727.42
R2's version number is 2.0.50727.210

Make sure you have the Release version running.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<de*********@gmail.comwrote in message
news:11*********************@h48g2000cwc.googlegro ups.com...
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 <customErrorstag within
a "web.config" configuration file located in the root directory of the
current web application. This <customErrorstag 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 =-
>

Nov 1 '06 #7
Juan --

All fixed! Before you wrote back, I uninstalled the .NET Framework
2.0, rebooted, then reinstalled the final version of the .NET Framework
2.0 (2.0.50727). After that, I ran the utility you suggested
("C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\as pnet_regiis.exe -lv")
and discovered that all of my applications were still mapped to the
v1.1.4322.2300 of the .NET Framework. Running the following script
recursively set the default version to v2.0.50727:

===================================
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspn et_regiis.exe -lv
===================================

I've been working with Classic ASP for eight years -- long enough to
have read more than a few of your articles and books -- so I recognized
your name right away when you replied. I certainly appreciate you
taking the time to help me out... it's amazing how basic issues like
this are still relatively difficult to find cohesive information on,
in- or outside of repositories like MSDN or Usenet.

I'm gonna add another reply to my top-level post, detailing everything
just in case people happen across the article, and need a play-by-play.
Thanks again!
-= Tek Boy =-
Juan T. Llibre wrote:
re:
how will I know if the upgrade was successful?

Run aspnet_regiis -lv from the .Net framework 2.0's directory
( Drive:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 )

That will list all the installed versions.

If version 2.0.50727.210 is still registered, either run the uninstall tool found here :
http://msdn.microsoft.com/vstudio/su...l/default.aspx

...or uninstall manually and then reinstall the release version.
The instructions for a manual uninstall are there, too.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================

<de*********@gmail.comwrote in message
news:11**********************@m7g2000cwm.googlegro ups.com...
Juan --

We don't have enough daytime bandwidth, and that link you posted said
the SDK comes with VS.NET 2005 (which is already installed on the
server), so I downloaded the normal .NET v2.0 EXE instead.

However, the problem still occurred after I installed (repaired) .NET
v2.0 and rebooted. What's the specific sequence of events I need to
follow to upgrade from the R2 beta version to the release version of
.NET v2.0? Also, how will I know if the upgrade was successful? Sorry
to bother you with all the minutiae... I certainly do appreciate your
help.
-= Tek Boy =-

Juan T. Llibre wrote:
Yes, I thought so.

It's a common problem with R2, which I think shouldn't have
been released with a beta version of tyhe .Net Framework.

Only a few more builds and R2 could have gone out with the release version.

You need to download, at least, the release version of the redistributable.

If you've got enough bandwidth, go for the SDK. The developer samples are worth it.

http://msdn2.microsoft.com/en-us/net.../aa731542.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<de*********@gmail.comwrote in message
news:11*********************@e64g2000cwd.googlegro ups.com...
Juan --

I believe so. At the bottom of the ASPX page (and below the error
messages), I see the following text:

================================================
"Version Information: Microsoft .NET Framework Version:2.0.50727.42;
ASP.NET Version:2.0.50727.210"
================================================
-= Tek Boy =-
Juan T. Llibre wrote:
Did you upgrade the .Net Framework version on R2 to the Release version ?
>
The .Net Framework's Release version number is 2.0.50727.42
R2's version number is 2.0.50727.210
>
Make sure you have the Release version running.
>
>
>
>
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<de*********@gmail.comwrote in message
news:11*********************@h48g2000cwc.googlegro ups.com...
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 <customErrorstag within
a "web.config" configuration file located in the root directory of the
current web application. This <customErrorstag 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... thanksin
advance!


-= Tek Boy =-
Nov 1 '06 #8
re:
I've been working with Classic ASP for eight years -- long enough to
have read more than a few of your articles and books -- so I recognized
your name right away when you replied. I certainly appreciate you
taking the time to help me out
My pleasure, Tek Boy, although if you've been working as a programmer
for 8 years maybe you should consider changing your name to "Tek Man".

:-)

re:
I'm gonna add another reply to my top-level post, detailing everything
just in case people happen across the article, and need a play-by-play.
Wonderful!
I wish everybody did that.

Glad to have been of help.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<de*********@gmail.comwrote in message news:11*********************@e3g2000cwe.googlegrou ps.com...
Juan --

All fixed! Before you wrote back, I uninstalled the .NET Framework
2.0, rebooted, then reinstalled the final version of the .NET Framework
2.0 (2.0.50727). After that, I ran the utility you suggested
("C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\as pnet_regiis.exe -lv")
and discovered that all of my applications were still mapped to the
v1.1.4322.2300 of the .NET Framework. Running the following script
recursively set the default version to v2.0.50727:

===================================
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspn et_regiis.exe -lv
===================================

I've been working with Classic ASP for eight years -- long enough to
have read more than a few of your articles and books -- so I recognized
your name right away when you replied. I certainly appreciate you
taking the time to help me out... it's amazing how basic issues like
this are still relatively difficult to find cohesive information on,
in- or outside of repositories like MSDN or Usenet.

I'm gonna add another reply to my top-level post, detailing everything
just in case people happen across the article, and need a play-by-play.
Thanks again!
-= Tek Boy =-
Juan T. Llibre wrote:
re:
how will I know if the upgrade was successful?

Run aspnet_regiis -lv from the .Net framework 2.0's directory
( Drive:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 )

That will list all the installed versions.

If version 2.0.50727.210 is still registered, either run the uninstall tool found here :
http://msdn.microsoft.com/vstudio/su...l/default.aspx

...or uninstall manually and then reinstall the release version.
The instructions for a manual uninstall are there, too.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================

<de*********@gmail.comwrote in message
news:11**********************@m7g2000cwm.googlegro ups.com...
Juan --

We don't have enough daytime bandwidth, and that link you posted said
the SDK comes with VS.NET 2005 (which is already installed on the
server), so I downloaded the normal .NET v2.0 EXE instead.

However, the problem still occurred after I installed (repaired) .NET
v2.0 and rebooted. What's the specific sequence of events I need to
follow to upgrade from the R2 beta version to the release version of
.NET v2.0? Also, how will I know if the upgrade was successful? Sorry
to bother you with all the minutiae... I certainly do appreciate your
help.
-= Tek Boy =-

Juan T. Llibre wrote:
Yes, I thought so.

It's a common problem with R2, which I think shouldn't have
been released with a beta version of tyhe .Net Framework.

Only a few more builds and R2 could have gone out with the release version.

You need to download, at least, the release version of the redistributable.

If you've got enough bandwidth, go for the SDK. The developer samples are worth it.

http://msdn2.microsoft.com/en-us/net.../aa731542.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<de*********@gmail.comwrote in message
news:11*********************@e64g2000cwd.googlegro ups.com...
Juan --

I believe so. At the bottom of the ASPX page (and below the error
messages), I see the following text:

================================================
"Version Information: Microsoft .NET Framework Version:2.0.50727.42;
ASP.NET Version:2.0.50727.210"
================================================
-= Tek Boy =-
Juan T. Llibre wrote:
Did you upgrade the .Net Framework version on R2 to the Release version ?
>
The .Net Framework's Release version number is 2.0.50727.42
R2's version number is 2.0.50727.210
>
Make sure you have the Release version running.
>
>
>
>
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<de*********@gmail.comwrote in message
news:11*********************@h48g2000cwc.googlegro ups.com...
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 <customErrorstag within
a "web.config" configuration file located in the root directory of the
current web application. This <customErrorstag 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 =-

Nov 1 '06 #9
Juan --

All fixed! Before you wrote back, I uninstalled the .NET Framework
2.0, rebooted, then reinstalled the final version of the .NET Framework
2.0 (2.0.50727). After that, I ran the utility you suggested
("C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\as pnet_regiis.exe -lv")
and discovered that all of my applications were still mapped to the
v1.1.4322.2300 of the .NET Framework. Running the following script
recursively set the default version to v2.0.50727:

===================================
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspn et_regiis.exe -s
W3SVC\
===================================

I've been working with Classic ASP for eight years -- long enough to
have read more than a few of your articles and books -- so I recognized
your name right away when you replied. I certainly appreciate you
taking the time to help me out... it's amazing how basic issues like
this are still relatively difficult to find cohesive information on,
in- or outside of repositories like MSDN or Usenet.

I'm gonna add another reply to my top-level post, detailing everything
just in case people happen across the article, and need a play-by-play.
Thanks again!

-= Tek Boy =-
Juan T. Llibre wrote:
re:
how will I know if the upgrade was successful?

Run aspnet_regiis -lv from the .Net framework 2.0's directory
( Drive:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 )

That will list all the installed versions.

If version 2.0.50727.210 is still registered, either run the uninstall tool found here :
http://msdn.microsoft.com/vstudio/su...l/default.aspx

...or uninstall manually and then reinstall the release version.
The instructions for a manual uninstall are there, too.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================

<de*********@gmail.comwrote in message
news:11**********************@m7g2000cwm.googlegro ups.com...
Juan --

We don't have enough daytime bandwidth, and that link you posted said
the SDK comes with VS.NET 2005 (which is already installed on the
server), so I downloaded the normal .NET v2.0 EXE instead.

However, the problem still occurred after I installed (repaired) .NET
v2.0 and rebooted. What's the specific sequence of events I need to
follow to upgrade from the R2 beta version to the release version of
.NET v2.0? Also, how will I know if the upgrade was successful? Sorry
to bother you with all the minutiae... I certainly do appreciate your
help.
-= Tek Boy =-

Juan T. Llibre wrote:
Yes, I thought so.

It's a common problem with R2, which I think shouldn't have
been released with a beta version of tyhe .Net Framework.

Only a few more builds and R2 could have gone out with the release version.

You need to download, at least, the release version of the redistributable.

If you've got enough bandwidth, go for the SDK. The developer samples are worth it.

http://msdn2.microsoft.com/en-us/net.../aa731542.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<de*********@gmail.comwrote in message
news:11*********************@e64g2000cwd.googlegro ups.com...
Juan --

I believe so. At the bottom of the ASPX page (and below the error
messages), I see the following text:

================================================
"Version Information: Microsoft .NET Framework Version:2.0.50727.42;
ASP.NET Version:2.0.50727.210"
================================================
-= Tek Boy =-
Juan T. Llibre wrote:
Did you upgrade the .Net Framework version on R2 to the Release version ?
>
The .Net Framework's Release version number is 2.0.50727.42
R2's version number is 2.0.50727.210
>
Make sure you have the Release version running.
>
>
>
>
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<de*********@gmail.comwrote in message
news:11*********************@h48g2000cwc.googlegro ups.com...
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 <customErrorstag within
a "web.config" configuration file located in the root directory of the
current web application. This <customErrorstag 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... thanksin
advance!


-= Tek Boy =-
Nov 1 '06 #10
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/net.../aa731542.aspx and
http://www.microsoft.com/downloads/d...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\aspn et_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\aspn et_regiis.exe -s
W3SVC/

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspn et_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 =-
de*********@gmail.com 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 <customErrorstag within
a "web.config" configuration file located in the root directory of the
current web application. This <customErrorstag 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 =-
Nov 1 '06 #11

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

0
by: Dean | last post by:
This is a problem in ASP.NET, when I run an application from Visual Studio (2003) when I do a "start without debugging". The asp page uses objects that I have built in 3 other projects,...
3
by: fred bliss | last post by:
Hi All We have a new server running the latest framework, windows server 2003 & IIS 6.0, and we're getting the following error when we try to load the app in IE. Server Error in...
4
by: Matthew Louden | last post by:
My ASP.NET application runs ok locally, but after I upload all the files to IIS in Windows Server 2003 Standard Edition, and no longer works. This has the following error messages: Configuration...
4
by: scottrm | last post by:
We have two developers, call them A and B, (on Windows XP) developing a number of asp.net web sites on a shared server (Windows 2003). Everything has been ok but recently for no apparent reason...
7
by: Martin Strojek | last post by:
Hi, I have the following problem with developing some web site. I use Visual Studio 2003 to build a website. I tried Windows 2003 Server and switched now back to Windows XP with PWS but the...
1
by: Ramanfromoz | last post by:
Hi, Developing a new we application. Everything okay on my local WIN XP PROFESSIONAL, IIS 5.0 running locally. The website is running smoothly. Now, the same code I am copying over to a...
0
by: David Lozzi | last post by:
Howdy, I get the error message as displayed below. I'm using Visual Studio 2003 on WinXP Pro SP2 workstation. I'll be sitting here happily developing when all of a sudden blamo this error will...
2
by: heddy | last post by:
Howdy folks. I am trying to build a web service using the following configuration: I have Windows 2003 Server running in VMware. I have IIS set up on it. I installed the .NET 2.0 package on...
1
by: =?Utf-8?B?TWF0dCBDYWxob29u?= | last post by:
Hi there, I have a new server that we are adding to our web cluster. This server has Windows Server 2003 32-bit Service Pack 1 installed. We have .NET 1.1 and 2.0 on this machine. A web...
0
by: abbasky | last post by:
### Vandf component communication method one: data sharing ​ Vandf components can achieve data exchange through data sharing, state sharing, events, and other methods. Vandf's data exchange method...
0
by: stefan129 | last post by:
Hey forum members, I'm exploring options for SSL certificates for multiple domains. Has anyone had experience with multi-domain SSL certificates? Any recommendations on reliable providers or specific...
0
Git
by: egorbl4 | last post by:
Скачал я git, хотел начать настройку, а там вылезло вот это Что это? Что мне с этим делать? ...
1
by: davi5007 | last post by:
Hi, Basically, I am trying to automate a field named TraceabilityNo into a web page from an access form. I've got the serial held in the variable strSearchString. How can I get this into the...
0
by: MeoLessi9 | last post by:
I have VirtualBox installed on Windows 11 and now I would like to install Kali on a virtual machine. However, on the official website, I see two options: "Installer images" and "Virtual machines"....
0
by: Aftab Ahmad | last post by:
So, I have written a code for a cmd called "Send WhatsApp Message" to open and send WhatsApp messaage. The code is given below. Dim IE As Object Set IE =...
0
by: ryjfgjl | last post by:
ExcelToDatabase: batch import excel into database automatically...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.