Urgent: help deploying an ASP.NET app!!

[RCS]

I am trying to deploy an app to a WLBS cluster. We've been testing on our QA
WLBS cluster. In VS.NET 2K3, I typically use the "Copy Project" button to
copy the project to the next tier. This is the first ASP.NET app that is
going on the production cluster. I've been writing a testing (and deploying
from dev to the QA cluster) quite a bit.

When I try to copy I get "Internal Server Error" from BOTH servers (I try
copying to each individually).

Where this is copying TO - are two servers that are set up identical (our
production intranet), there are new "virtual websites". These servers have
..NET 1.0 and 1.1 installed. This is a 1.1 application.

I re-installed FPSE on that website and that looks normal, I re-ran
aspnet_regiis.exe -i

I am also logged on (and have connected) to both servers as an
administrator - security shouldn't be an issue in this particular
environment.

I still get the same error on both machines. Does this ring any bells?? ANY
IDEAS???? thanks

 

[RCS]

Any have any ideas??? I got a bunch of people hounding me, I wasn't
expecting an error this uncorrectable at the last minute!!!

I re-created the virtual website, re-extended FPSE 2K2, ran aspnet_regiis
again, checked permissions.. I still get "Internet server error" if I try to
copy the source out there - or if I manually copy the files out there and
try to run a page.

Any ideas at all??

 

[john_20_28_2000]

does it help if you turn off friendly errors?

 

[RCS]

What's odd is the application is "/WAS/" and the regular browser error is:

Server Error in '/' Application.

So it doesn't even recognize /WAS as an application - and yes, I've gone
into IIS and even went as far as making it "Isolated" and it's own
application. Same result.

I have a .NET DLL that's used on this page (for a legacy ASP app that
consumes it as a COM+ object) - but aside from that, this is the first real
..NET app and first ASP.NET app on this server...

thanks for the response!

 

[sze tan]

The server error is too generic to troubleshoot what the problem may
be.
In your web.config file, change the
<customErrors mode="RemoteOnly"/>
default setting to
<customErrors mode="Off"/>
Access the page again locally and see what detailed error it gives you.

Maybe we can help you from there...

 

[RCS]

I have a web.config in the root AND in /WAS that already has that - still
same error

I have since re-installed .NET 1.1 sp1 and rebooted - still the same... this
seems like some sort of fundamental configuration problem, but I've tried
everything I can think of!!