Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Replication / November 2005

Tip: Looking for answers? Try searching our database.

queue reader agent reports ODBC Error: Invalid cursor state

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
John T - 29 Nov 2005 19:40 GMT
Hello,

SQL Server verison on Publisher: 8.00.970
SQL Server verison on Subscriber: 8.00.970

An update proc containing two statements was issued on the subscriber. The
queue reader reports ODBC Error: Invalid cursor state.

I do not believe that Q831997 Applies here, because the symptoms published
under this article say:

"After you apply post-Microsoft SQL Server 2000 Service Pack 3 (SP3) hotfix
build versions between 8.00.0859 and 8.00.0875, applications that execute a
stored procedure that uses a SET NOCOUNT ON statement and that return one or
more result sets following an informational message, a RAISERROR statement,
or a PRINT statement, may have various failures in processing results....."

1) Is this assumption wrong?  My curent sql version is greater than .0875.  
SET NOCOUNT was OFF, no RAISERROR statement was present in the proc, and no
PRINT statement was present in the proc.

2) I have tried restarting the queue reader multiple times, and even
stopped/restarted the distribution agent.

3) Can I clean up the queue by running sp_MSreset_queue, and then mark the
article for resyncing via snapshot?  Does sp_MSreset_queue mark the whole
publication for resyncing via snapshot?

4) Is there a simple fix for this if Q831997 does not apply?

Thanks,

John T
John T - 29 Nov 2005 21:06 GMT
BTW, if it is not obvious this is Transactional Replication with 1 Queued
Updating subscriber.  The distributor is on the same server as the Publisher.

> Hello,
>
[quoted text clipped - 29 lines]
>
> John T
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.