Newbie problem -- VB.NET and IIS

[Stuff]

Hi,

I have been doing ASP for awhile now, and am just starting to use Visual
Studio/VB .NET.with a local IIS 5.1 server. (Using XP-PRO with all the
latest updates, and Framework 1.1 {although, I just noticed, Framework
(original) is still listed as being on the shard drive))

I can get a simple VB.NET application to build, but when I go to run it
using F5, IE comes up with an error (listed a bottom).

I do not have enough knowledge to find the problem...can you please help
this newbie with some detailed instructions or MS links to the solution? I
do not know where to locate the logs the error message speaks about.

Does this have to do with debug?

thanX for your help
Howie
---------------- Error from IE ---------------

Server Application Unavailable

The web application you are attempting to access on this web server is
currently unavailable. Please hit the "Refresh" button in your web browser
to retry your request.

Administrator Note: An error message detailing the cause of this specific
request failure can be found in the application event log of the web server.
Please review this log entry to discover what caused this error to occur.

 

[Cowboy \(Gregory A. Beamer\)]

Apologies for the long post, but some others may get something out of this,
as the issue is rather common. I have divided this into sections for ease of
finding information.

First suggestions
-----------------
Read http://support.microsoft.com/default.aspx?scid=kb;en-us;811320
It details a problem that sometimes happens with aspnet_wp.exe to throw the
error in question. It is the most common reason I have seen for this
problem. Open event viewer and you should see this error:
aspnet_wp.exe could not be started. HRESULT for the failure: 80070005

While not as common, there is also this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;323292
This one throws this error in Event Log (application log):
aspnet_wp.exe could not be started. HRESULT for the failure: 80004005

Wow! That looks familiar!!!

Other ideas
------------
This one does not apply, as you are on XP:
http://support.microsoft.com/default.aspx?scid=kb;en-us;315158
NOTE: that is is there, however, if you ever get this error on a server OS
that happens to be a Domain Controller
This one throws:
aspnet_wp.exe could not be launched because the username and/or password
supplied in the processModel section of the config file are invalid.
aspnet_wp.exe could not be started.
HRESULT for the failure: 80004005

Very unlikely you are using Response.WriteFile, but here is one for that:
http://support.microsoft.com/default.aspx?scid=kb;en-us;812406

As you are debugging, this one is way out there (very, very unlikely):
http://support.microsoft.com/default.aspx?scid=kb;en-us;326366
Event log messages (one of two):
aspnet_wp.exe (PID: 3644) stopped unexpectedly.
(or)
The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event: .NET
Runtime version 1.0.3705.0- aspnet_wp.exe - Common Language Runtime
Debugging Services: Application has generated an exception that could not be
handled.


Final options
-------------
What version of Visual Studio .NET are you using?

If VS.NET 2003, run the following from a Visual Studio .NET 2003 command
prompt:

aspnet_regiis -i

This should solve the problem.

If VS.NET 2002, you will have to ground the web you are working on with the
1.0 Framework. Read this:
http://msdn.microsoft.com/library/en-us/dnhcvs03/html/vs03f6.asp

I had the same problem on my Whidbey box (Visual Studio .NET 2004 PDC alpha)
working with Visual Studio .NET 2003 and the instructions for my web made it
so I can debug. The basic command is:

aspnet_regiis.exe -sn W3SVC/1/ROOT/{Name of your virtual root}

Make sure you run the version of aspnet_regiis from the correct version. If
you use the command prompt installed with .NET, it will be linked to the
version installed, which is why I suggest you use it.

As this is unlikely to be your problem, it makes for a good brief on using
multiple versions of the Framework, and you should take note, as it is
possible you will see this in the future, as you go to VS.NET 2004 next
year.



--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

**********************************************************************
Think Outside the Box!
**********************************************************************

 

[Stuff]

Hey Greg ... than-X ... will make use of what you suggested! And than-Q for
being so thorough!!!!!!!