1 server, 2 web sites 1 asp.net app each, build one, other -> Server App Unavailable

D

Dave Diehl

Has anyone heard of a problem with a rebuild of one application
causing a problem with another app on the same server?

I have two asp.net applications on the same Win2000 server, each with
it's own web site (i.e. IP, root folder, etc.). Each accesses it's
own SQL Server 2000 database. Let's call them App A and App B.

If I open a page in App A that starts a long-running process...so it's
sitting there in perpetual "loading page" state until the processing
is finished...it works fine. However, if I build a new copy of App B
while the page in App A is open -- boom. "Server Application
Unavailable".

Here's the kicker. App B is a copy of App A, created using the "Copy
Project..." wizard. I created the App B web site from scratch in IIS
Admin, opened App A using VS.Net, then used the wizard to copy the all
files to App B.

I thought it might be an duplicate assembly name or namespace issue,
but I've changed both on both apps to be unique to no avail. I've
also rebuild App A as a release build. App B is still a debug build.

So...anyone have any suggestions?

Thanks in advance,
Dave Diehl
 
G

Guest

Have you tried running both applications in "High" Isolation mode? If
they're both in the same application pool, there may be some resource
contention, depending on what it is that your app is actually doing.
 
D

Dave Diehl

Yep. First thing I tried. Didn't work.

Thanks,
Dave

Have you tried running both applications in "High" Isolation mode? If
they're both in the same application pool, there may be some resource
contention, depending on what it is that your app is actually doing.

Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
 
D

Dave Diehl

Ok...problem solved.

The application had a registered copy of expired trial version of some
software. Since it wasn't used, I didn't think about it until I read the
best practices white paper at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/dbgrm.asp.
The fourth chapter discussed "debugging unexpected process termination" and
started talking about COM threading in ASP.NET. That made me wonder about
third party software...which lead me to the expired license...which lead me
to the solution. Remove the references and, voila, it works.

This was a hard nut to crack because while I could find a lot of references
to the "aspnet_wp.exe (PID: ???) stopped unexpectedly." error message, very
little was mentioned about the message event ID (1000) that didn't also
mention that subsequent event messages that would indicate the real issue.
I didn't get any other messages. I'm not sure whether the third-party
software was managed or unmanaged code...sorry.

Thanks to Greg for at least giving it a try.

Dave
 
D

Dave Diehl

Ok...I spoke to soon. Problem's still there.

The only things I know the two projects share are:
- references to two custom controls: (skmMenu and WebChart)
- reference to the Microsoft Data ApplicationBlock.

They have different project names, namespaces, access different databases,
work in high-isolation thread pools, etc.

One was created using the Copy Project and both projects reside on the web
servers.

I'm stumped.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,743
Messages
2,569,478
Members
44,898
Latest member
BlairH7607

Latest Threads

Top