Can you post the code that is causing the error?
Are you using Transactions in your queries? SQL Server CE has a limit of 5
nested transactions.
Kevin Boske
(
[email protected])
SQL Server CE Team
Microsoft
----------------------------------------------------------------------------
----------------------------------------
Everything you need to know about SQL Server CE:
http://www.microsoft.com/sql/ce/techinfo/default.asp
----------------------------------------------------------------------------
----------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.
----------------------------------------------------------------------------
----------------------------------------
--------------------
From: (e-mail address removed) (David Webb)
Newsgroups:
microsoft.public.sqlserver.ce,microsoft.public.dotnet.framework.compactframe
work
Subject: The SqlCeCommand is currently busy 5
Date: 3 Oct 2003 04:36:17 -0700
Organization:
http://groups.google.com
Lines: 15
Message-ID: <
[email protected]>
NNTP-Posting-Host: 150.101.188.98
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1065180977 32757 127.0.0.1 (3 Oct 2003 11:36:17
GMT)
X-Complaints-To: (e-mail address removed)
NNTP-Posting-Date: Fri, 3 Oct 2003 11:36:17 +0000 (UTC)
Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onlin
e.de!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!sn-xit-03!sn-xit-01!sn-
xit-09!supernews.com!postnews1.google.com!not-for-mail
Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.compactframework:35076
microsoft.public.sqlserver.ce:9543
X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
Hi,
I keep getting the above error on my VB.NET CF app. I'm ensuring that
I close the data readers each time I use them and I'm using a global
command object. I'm wondering if this problem is happening during
tight processing loops and perhaps the command object is closing
quickly enough. Has anyone experienced similar problems? I'm not sure
what the significance of the 5 is at the end of the message. It is
being raised by a normal exception and not a SQLSERVERCE Exception.
Any help would be greatly appreciated.
Kind Regards,
David.
