-2147217885 "Cursor Operation Conflict" kept occuring on save_new_post_data in new_post.asp.  No one could post new messages.

 

I'm not quite sure why this error started popping up, but I my initial guess was that "no count" was unchecked in the SQL Server Configuration (Connections).  This was not the case.  It was checked as being on, so my search continued....

 

Based on some knowledgebase articles, it seems like the server might be using a server-side cursor instead of a client side cursor, yikes!

 

So after some testing I added specific code to set the cursor type to client.  (See Below) 

 

Ultimately I added to new_post.asp as an experiment:

 

With rsCommon

  'Set the cursor type property of the record set to Dynamic so we can navigate through the record set
  .CursorType = 2

 

...

...

 

It fixed the problem!

 

Then I looked at setting this globally in the database_connection.asp page, which also seems to work:

 

 adoCon.connectionstring = strCon
 adoCon.CursorLocation = 3

 

Any thoughts on what may have happened?

 

Thanks,

Jason Walters