web.config conflicts in virtual directories

In IIS, I have two web applications configured as follows:

Website 1 (fixed IP)
Application A
page1.aspx
web.config

Application B
page1.aspx
web.config


each of the web.config files contain a connection strings block with
one connection string ("connection 1"). When I try to open
application B in my browser, I get the following error:

Entry Connection 1 has already been added

indicating that although I'm requesting Application B, both web.config
files are being read and a conflict has arisen. I can fix this by
running Application B in a separate application pool, but I'd like to
know what's causing it. I cannot seem to reproduce this problem in my
development environment.

Bill E.

RE: web.config conflicts in virtual directories

Are both Application A and Application B set as Applications in IIS? If not,
this would be the cause of your problem.
-- Peter
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
MetaFinder: http://www.blogmetafinder.com


"Bill E." wrote:

> In IIS, I have two web applications configured as follows:
>
> Website 1 (fixed IP)
> Application A
> page1.aspx
> web.config
>
> Application B
> page1.aspx
> web.config
>
>
> each of the web.config files contain a connection strings block with
> one connection string ("connection 1"). When I try to open
> application B in my browser, I get the following error:
>
> Entry Connection 1 has already been added
>
> indicating that although I'm requesting Application B, both web.config
> files are being read and a conflict has arisen. I can fix this by
> running Application B in a separate application pool, but I'd like to
> know what's causing it. I cannot seem to reproduce this problem in my
> development environment.
>
> Bill E.
>

Re: web.config conflicts in virtual directories

Peter,

Both are set as applications in IIS.

Bill

Peter Bromberg [ C# MVP ] wrote:
> Are both Application A and Application B set as Applications in IIS? If not,
> this would be the cause of your problem.
> -- Peter
> Site: http://www.eggheadcafe.com
> UnBlog: http://petesbloggerama.blogspot.com
> MetaFinder: http://www.blogmetafinder.com
>
>
> "Bill E." wrote:
>
> > In IIS, I have two web applications configured as follows:
> >
> > Website 1 (fixed IP)
> > Application A
> > page1.aspx
> > web.config
> >
> > Application B
> > page1.aspx
> > web.config
> >
> >
> > each of the web.config files contain a connection strings block with
> > one connection string ("connection 1"). When I try to open
> > application B in my browser, I get the following error:
> >
> > Entry Connection 1 has already been added
> >
> > indicating that although I'm requesting Application B, both web.config
> > files are being read and a conflict has arisen. I can fix this by
> > running Application B in a separate application pool, but I'd like to
> > know what's causing it. I cannot seem to reproduce this problem in my
> > development environment.
> >
> > Bill E.
> >

Re: web.config conflicts in virtual directories

This problem went away without explanation. I simply updated one of
the web.config files (without changing it) and now both sites are
working.

Bill

Bill E. wrote:
> Peter,
>
> Both are set as applications in IIS.
>
> Bill
>
> Peter Bromberg [ C# MVP ] wrote:
> > Are both Application A and Application B set as Applications in IIS? If not,
> > this would be the cause of your problem.
> > -- Peter
> > Site: http://www.eggheadcafe.com
> > UnBlog: http://petesbloggerama.blogspot.com
> > MetaFinder: http://www.blogmetafinder.com
> >
> >
> > "Bill E." wrote:
> >
> > > In IIS, I have two web applications configured as follows:
> > >
> > > Website 1 (fixed IP)
> > > Application A
> > > page1.aspx
> > > web.config
> > >
> > > Application B
> > > page1.aspx
> > > web.config
> > >
> > >
> > > each of the web.config files contain a connection strings block with
> > > one connection string ("connection 1"). When I try to open
> > > application B in my browser, I get the following error:
> > >
> > > Entry Connection 1 has already been added
> > >
> > > indicating that although I'm requesting Application B, both web.config
> > > files are being read and a conflict has arisen. I can fix this by
> > > running Application B in a separate application pool, but I'd like to
> > > know what's causing it. I cannot seem to reproduce this problem in my
> > > development environment.
> > >
> > > Bill E.
> > >