Valery,
Are you running this new ASP.NET application on the same virtual server as
your SharePoint site? If so, that's exactly what your problem is, and
here's why.
Windows SharePoint Services 2.0 doesn't serve content out of your content
root (i.e. c:\inetpub\wwwroot). Instead, it stores all content in SQL
Server and serves it from there. When you request an ASPX page in your
SharePoint site, that request is parsed through the SharePoint ISAPI filter
and redirected to SQL Server. After installing SharePoint on your server,
you will not be able to create new apps with VS.NET against that same
virtual server because VS.NET doesn't know anything about this ISAPI
filter. VS.NET places your content in c:\inetpub\wwwroot\<project>. When
you request one of those ASP.NET pages, the SharePoint filter grabs the
request and tries to find your content in SQL Server. Since it's not
there, you get a 404.
Yes, the solution is to either uninstall Windows SharePoint Services 2.0 or
create a new virtual server for your Visual Studio .NET ASP.NET
applications.
Jim Cheshire [MSFT]
Developer Support
ASP.NET
ja******@online.microsoft.com
This post is provided as-is with no warranties and confers no rights.
--------------------
From: "Valery Bulash" <vb*****@msn.com>
References: <Oj*************@tk2msftngp13.phx.gbl>
<RR**************@cpmsftngxa06.phx.gbl>
<eN**************@TK2MSFTNGP11.phx.gbl>
<Hq**************@cpmsftngxa06.phx.gbl>Subject: Re: ASP.NET on IIS 6.0
Date: Fri, 17 Oct 2003 10:47:29 +0300
Lines: 142
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.3790.0
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Message-ID: <u7**************@tk2msftngp13.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: 195.222.95.138
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftn gp13.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:184850
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
Unfortunately it didn't help.
Some guys on gotdotnet.ru advice me to kill STS 2.0 -- they've faced with
similar problem and just removing of SharePoint Team Service 2.0 helped
them.
Maybe it will help?
"Jim Cheshire [MSFT]" <ja******@online.microsoft.com> wrote in message
news:Hq**************@cpmsftngxa06.phx.gbl... Valery,
Are you running this in the default app pool? Will it run in a different
app pool?
Again, your error clearly indicates that IIS is not allowing the ASP.NET
ISAPI filter to process the request. That is usually because ASP.NET is
not allowed. If the problem is still happening after doing that, I would
try running an aspnet_regiis -i at a VS.NET command prompt to see if
re-registering the ISAPI DLL and repairing the ASPNET account resolves
the issue.
Jim Cheshire [MSFT]
Developer Support
ASP.NET
ja******@online.microsoft.com
This post is provided as-is with no warranties and confers no rights.
-------------------- >From: "Valery Bulash" <vb*****@msn.com>
>References: <Oj*************@tk2msftngp13.phx.gbl>
<RR**************@cpmsftngxa06.phx.gbl> >Subject: Re: ASP.NET on IIS 6.0
>Date: Thu, 16 Oct 2003 20:14:39 +0300
>Lines: 85
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.3790.0
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Message-ID: <eN**************@TK2MSFTNGP11.phx.gbl>
>Newsgroups: microsoft.public.dotnet.framework.aspnet
>NNTP-Posting-Host: 195.222.95.138
>Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP11.phx.gbl
>Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.aspnet:184699 >X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
>
>Not so clear
>As I wrote before:
>> >3) Web Server Extensions allowed in IIS configuration. No results.
>It means that ASP.NET was allowed.
>
>"Jim Cheshire [MSFT]" <ja******@online.microsoft.com> wrote in message
>news:RR**************@cpmsftngxa06.phx.gbl...
>> Valery,
>>
>> A 404 error when requesting an ASP.NET page on IIS6 is a clearindication >> that ASP.NET is not allowed in IIS.
>>
>> Open Internet Information Services. Click once on the Web Server
>> Extensions node and then select ASP.NET in the right-hand pane. Clickon >> the Allow button and then try again.
>>
>> Jim Cheshire [MSFT]
>> Developer Support
>> ASP.NET
>> ja******@online.microsoft.com
>>
>> This post is provided as-is with no warranties and confers no rights.
>>
>>
>> --------------------
>> >From: "Valery Bulash" <vb*****@msn.com>
>> >Subject: ASP.NET on IIS 6.0
>> >Date: Thu, 16 Oct 2003 19:07:39 +0300
>> >Lines: 33
>> >X-Priority: 3
>> >X-MSMail-Priority: Normal
>> >X-Newsreader: Microsoft Outlook Express 6.00.3790.0
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >Message-ID: <Oj*************@tk2msftngp13.phx.gbl>
>> >Newsgroups: microsoft.public.dotnet.framework.aspnet
>> >NNTP-Posting-Host: 195.222.95.133
>> >Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftn gp13.phx.gbl
>> >Xref: cpmsftngxa06.phx.gbl
>microsoft.public.dotnet.framework.aspnet:184666
>> >X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
>> >
>> >Please help to make ASP.NET applications running on IIS 6.0 (Windows
>Server
>> >2003 Standard Edition).
>> >None of ASP.NET applications work at this system -- even starter kits
and >> >.NET Framework ASP.NET samples. Special thanks to Microsoft! :-(.
>> >
>> >The system is almost pure after installation. Just SharePoint Team
>Services
>> >2.0 and VS.NET 2003 installed.
>> >
>> >The VS.NET 2003 reports during ASP.NET solution opening:
>> >
>> >The default Web access mode for this project is set to file share,
but >the
>> >project folder at 'Project URL' cannot be opened with the path'Physical >> >Project path'. The error returned was:
>> >Unable to create Web project 'Project Name'. The file path 'Physical
>> project
>> >path' does not correspond to the URL 'Project URL'. The two need tomap >to
>> >the same location. HTTP Error 404: Not Found
>> >
>> >Internet Explorer reports during any ASP.NET application opening
error >404
>> >"Page not found".
>> >
>> >1) Microsoft (PRB 817264) advices to create additional MIME-type
.tmp. >> >Done -- without any results
>> >2) Full rights for ASP.NET applications added for user NETWORKSERVICE. >No
>> >results
>> >3) Application Server (IIS, ASP.NET) configured (in Configure Your
Server >> >Wizard). No results.
>> >3) Web Server Extensions allowed in IIS configuration. No results.
>> >4) Few reboots done to fix configuration changes. No results
>> >What else?
>> >
>> >Is the deinstalling of Windows Server 2003 only one way?
>> >
>> >
>> >
>>
>
>
>
