Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > 1 server, 2 web sites 1 asp.net app each, build one, other -> Server App Unavailable

Reply
Thread Tools

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

 
 
Dave Diehl
Guest
Posts: n/a
 
      08-05-2004
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
 
Reply With Quote
 
 
 
 
=?Utf-8?B?R3JlZyBIdXJsbWFu?=
Guest
Posts: n/a
 
      08-06-2004
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.

---
Greg Hurlman
ghurlman*AT*squaretwo*DOT*net
http://blogs.squaretwo.net

"Dave Diehl" wrote:

> 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
>

 
Reply With Quote
 
 
 
 
Dave Diehl
Guest
Posts: n/a
 
      08-06-2004
Yep. First thing I tried. Didn't work.

Thanks,
Dave

On Fri, 6 Aug 2004 05:45:02 -0700, Greg Hurlman
<ghurlman*AT*squaretwo*DOT*net> wrote:

> 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.
>
> ---
> Greg Hurlman
> ghurlman*AT*squaretwo*DOT*net
> http://blogs.squaretwo.net


Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
 
Reply With Quote
 
Dave Diehl
Guest
Posts: n/a
 
      08-10-2004
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/de...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


"Dave Diehl" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> 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



 
Reply With Quote
 
Dave Diehl
Guest
Posts: n/a
 
      08-11-2004
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.

"Dave Diehl" <vt.igsd@devad> wrote in message
news:(E-Mail Removed)...
> 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/de...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
>
>
> "Dave Diehl" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) om...
> > 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

>
>



 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
using python to visit web sites and print the web sites image to files imx Python 10 03-14-2007 02:19 PM
Visual Web Developer does not support creating Web sites on a SharePoint Web server William LaMartin ASP .Net 0 12-29-2005 04:17 PM
How do prevent sites to be loaded in other sites frames? Stefan Caliandro HTML 2 02-14-2005 06:05 PM
SWsoft Acronis Disk Director Suite 9.0 Build 508, Acronis OS Selector 8.0 Build 917, Acronis Partition Expert 2003 Build 292, Acronis Power Utilities 2004 Build 502, F-SECURE.ANTI vIRUS.PROXY v1.10.17.WINALL, F-SECURE.ANTI vIRUS v5.50.10260 for CITRI vvcd Computer Support 0 09-25-2004 01:38 AM
ISO: Web sites for images (pay sites preferred) Kevin Buchan ASP .Net 1 02-20-2004 09:34 AM



Advertisments