Cannot connect to the configuration database.

Ok in IIS we have 3 "Websites": Default Website, SharePoint Central
Administration & Team Foundation Server. I created a new virtual directory
under the Default Website and copied up the new website files. When I try to
access the new virtual directory, it gives me the error above. The Default
Website is using it's own AppPool and the new virtual directory is also using
the same AppPool. The new website is NOT a SharePoint website, just a regular
ASP.Net 2.0 website. I read the KB article but it I don't htin kit applies.

--
Nick Koier
Senior .Net Developer
Budget Finance Company

Re: Cannot connect to the configuration database.

On Dec 5, 12:08 pm, nickster wrote:
> Ok in IIS we have 3 "Websites": Default Website, SharePoint Central
> Administration & Team Foundation Server. I created a new virtual directory
> under the Default Website and copied up the new website files. When I try to
> access the new virtual directory, it gives me the error above. The Default
> Website is using it's own AppPool and the new virtual directory is also using
> the same AppPool. The new website is NOT a SharePoint website, just a regular
> ASP.Net 2.0 website. I read the KB article but it I don't htin kit applies.
>
> --
> Nick Koier
> Senior .Net Developer
> Budget Finance Company


Just adding new Virtual Directory or new Application Pool is
insufficient when you have Sharepoint installed because it takes over
the entire server.

That error is not from IIS nor ASP.Net. You need to go to Sharepoint
and "exclude" your new virtual directory from the namespace of
Sharepoint. Only then will its ISAPI filter stop hijacking your
requests and returning that error.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: Cannot connect to the configuration database.

Dude, you rock thanks!

--
Nick Koier
Senior .Net Developer
Budget Finance Company


"David Wang" wrote:

> On Dec 5, 12:08 pm, nickster wrote:
> > Ok in IIS we have 3 "Websites": Default Website, SharePoint Central
> > Administration & Team Foundation Server. I created a new virtual directory
> > under the Default Website and copied up the new website files. When I try to
> > access the new virtual directory, it gives me the error above. The Default
> > Website is using it's own AppPool and the new virtual directory is also using
> > the same AppPool. The new website is NOT a SharePoint website, just a regular
> > ASP.Net 2.0 website. I read the KB article but it I don't htin kit applies.
> >
> > --
> > Nick Koier
> > Senior .Net Developer
> > Budget Finance Company
>
>
> Just adding new Virtual Directory or new Application Pool is
> insufficient when you have Sharepoint installed because it takes over
> the entire server.
>
> That error is not from IIS nor ASP.Net. You need to go to Sharepoint
> and "exclude" your new virtual directory from the namespace of
> Sharepoint. Only then will its ISAPI filter stop hijacking your
> requests and returning that error.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>