I will look into this. Do you or anyone else know how I can check to see how
"Steven Cheng[MSFT]" <v-schang@online.microsoft.com> wrote in message
news:R90hQqpeEHA.740@cpmsftngxa06.phx.gbl...
> Hi Warren,
>
> From the callstacks and error infos you provided, especially the following
> lines
> ==============================
> Error message: There is already an open DataReader associated with
> this Connection which must be closed first.
> ==============================
>
> I think there are two possible causes(since your SQLSERVER is MSDE rather
> than server version)
> 1. There is any code in your web app which doesn't close and release the
> opened connection correctly after finish the db maniplulation. For
example,
> when you're not using the
> try{...}catch(){..}finally{release db conn}
> or
> using(conn = new connection)
> {
>
> }
>
> to ensure the release of connection resource, when there is exception
occur
> during the code, the connection may be locked. this is a potential cause.
> So please check this in your code first.
>
> 2. Since the MSDE version is a desktop engine, it has its limited
> concurrent connections , not sure whether the problem is caused when there
> is too many concurrent request on the db manipulate page, you can also
have
> a check. And here is a tech article discussing on using MSDE in web
> application:
>
> #Using MSDE 2000 in a Web Application
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmsde2kwrk
> /html/msde2000webapp.asp
>
> You can have a look to see whether it helps. Also, if you have any new
> findings, please feel free to post here. Thanks.
>
> Regards,
>
> Steven Cheng
> Microsoft Online Support
>
> Get Secure!
www.microsoft.com/security > (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
> Get Preview at ASP.NET whidbey
>
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
>
>
>