Error while runnning project in ASP.Net - aspnet_wp.exe

  • Thread starter Thread starter rsomasundar
  • Start date Start date
R

rsomasundar

Hi,

I got the following error while trying to run the project in ASP.Net 2003 to
one of my application in my machine. I think some where im loosing the IIS
configurations.

Error Detail: Auto-attach to process '[5488] aspnet_wp.exe' on machine
'<machine name>' failed. Error code 0x8004000e.

Could you help me to find resolution.

Thanks.

OS: Windows 2000 Prof.
Framwork: 1.1
Enabled settings in IIS:
* Integrated Windows Authentication
* HTTP keep-alives enabled

Results when running 'Check server extensions': (Listed only specific
project entries)

Web http://<machine name>/Project
Begin check 10/23/2008 3:53:54 PM
PROBLEM: There is no web named "/Project".
NOT CORRECTED
End check 10/23/2008 3:53:55 PM
Web http://<machine name>/project1
Begin check 10/23/2008 3:53:55 PM
PROBLEM: Content folder "project1" not found.
NOT CORRECTED
End check 10/23/2008 3:53:55 PM

----Probably it should be only one project. I have placed my project as open
in wwwroot itself (without creating folders within wwwroot).

Is there any professional way to delete the ASP.Net project from machine
instead of removing folders in wwwroot and mydocuments???
 
Because you are speaking of projects, I'm assuming your trying to
access the project through Visual Studio and are getting errors like
the following:

1. The default Web access mode for this project is set to file share,
but the project folder at http://LocalHost/ProjectName cannot be
opened with the path ‘filepath’. The error returned was:

Unable to open Web project projectname. The Web projectname located
on server http://localhost does not exist.

2. Unable to open Web project projectname. The file filepath does not
correspond to the URL http://Localhost/projectname. The two must map
to the same server location. HTTP Error 404: Object Not Found.

3. The project you are trying to open is a Web project. You need to
open it by specifying its URL path.

There are two categories of projects in Visual Studio .NET: Web
Projects, and local or non-Web Projects. These problems happen when
web projects are not properly configured for editing on your
workstation.

Web projects are created over the HTTP protocol while non-web projects
are created through the local file system. The HTTP protocol
specifies relative file paths that get converted into absolute file
paths by a webserver. If you do not define either the necessary
relative to absolute file path mappings in IIS, or the relative file
path to your sandbox for the project, you will experience opening
problems.

Right click a web project folder in windows explorer and select
properties from the popup menu. On the "Web Sharing" tab of the
properties dialog that opens, click "Share this folder".

On the Edit Alias dialog that appears, select all permissions. The
Alias textbox should be populated with the folder name. Click [OK] to
close the dialog, and then [OK] again to close the property sheet.
You have just created a virtual directory in IIS; you do not need to
file share the folder.

Next, change the project’s webinfo file to make it point to the
virtual directory you’ve just setup. The name of the file will be the
same as the project file with the exception that it has a .webinfo
suffix. Because the webinfo file isn’t checked into CVS, you may have
to create it.

Edit the webinfo file in a text editor outside of visual studio and
change the XML tag <Web> so that it’s URLPath attribute refers to the
project file using your virtual directory alias as follows:

<VisualStudioUNCWeb>
<Web URLPath = http://localhost/youraliasname/yourprojectname.??proj
/>
</VisualStudioUNCWeb>

where:

Server = Always localhost
Youraliasname = alias name that’s the same as the folder name
containing your project
Yourprojectname.??proj Project file for your project (ends in vbproj
for visual basic and csproj for CSharp)

Next, change the project paths in the solution file (.sln) to make
them all relative to the current directory.

Edit the solution file in a text editor outside of visual studio and
remove any http://server qualification from the path for a project
file so that only the project file name remains (without any
preceeding slashes).

This should now allow you to open the project in visual studio.
 
Back
Top