Unable to open webproject...The two need to map to the same server location

[anToNIcHeN]

Hi All,
I am getting this frustating error message when i try to open my
project using VS.NET 2003.

OS: Windows 2003 Standard Edition with SP2
S.W Installed : VS.NET 2003, VS.NET 2005, Sharepoint Portal Server
2003.

In my IIS, I have created a website under port 111. And i have created
a virtual site under the website and correctly pointed out the path to
my project file.


I have tried the following things:
1. Check permissions.
2. Use mapped drive
3. Double check web paths in the webinfo and solution files
4. Removed frontpage extensions
5. Setup MIME type for .tmp extension


Does anyone have any other ideas?

Also, When I tried to create the same virtual site under default
website (ofcourse, i changed the url in both webinfo and sln file), it
opened fine... but this is not what i require... i need to make it work
under port 111.


regards,
Antony.

 

[anToNIcHeN]

Also, when I am trying to browse any aspx page by right clicking a file
from IIS manager and select 'browse', I am getting the error...
----------------------------------------------------------------------------------------
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.
------------------------------------------------------------------------------------------

I looked into the event log and couldnt find anything....

regards,
Antony

PS: this (browsing) worked fine from the default website....

 

[anToNIcHeN]

Success atlast...
This was the problem.....
I had created a Sharepoint PortalSite under port 111. So it was
sharepoint that was blocking the VS.NET 2003 to open the virtual site
that was created under port 111.

How I found out?...
I deleted the portal site (dont ask me who told me this... did out of
intuition...) and i opened the solution file and it started working
fine....

So concluded that, it was sharepoint which was creating the
problems....so did some googling and later found this solution....

Go to "Include / Exclude Sites" (In Define Managed Sites) in the
Sharepoint Central Administration page....
And Excluded the virtual site from the SharePoint managed Sites...

and it worked like a charm....