Error: 16955, Severity: 16, State: 2

Question

Error: 16955, Severity: 16, State: 2

marketwiz88

SSC-Addicted

Points: 406
More actions
August 10, 2004 at 8:45 pm

#163044

My application run fine without problem. When I turn profiler on to trace. I get the following exeption message. Is there a way I can find out what cause it or how to prevent it. I look up on BOL, it seem to be relate to some cursor.
Error: 16955, Severity: 16, State: 2
Error: 16945, Severity: 16, State: 1
These two errors message seem to appear randomly all over the place. Any help on trouble shootinsg this problem will be greatly appreciate it. I am using SQL Server 2000 SP3 on Windows 2000 server.
August 13, 2004 at 8:00 am

This was removed by the editor as SPAM

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Patrick Dalton SSC Rookie Points: 27 More actions · Answer 1

This is caused by incorrect params being sent to SQL to open a cursor... check your code and see what type of recordset and what options are being used.

The common cause I have seen is a updatable recordset with SUM(),COUNT(*) etc... when it should be read only

Not a lot of documentation on this, and this is just an example of what I have seen at a customer site.

Hope this helps.

Patrick

Kelly Kramer Valued Member Points: 67 More actions · Answer 2

I am getting a SQL Server 2000 error:

The following SQL Server error(s) occurred while accessing the MobileUnit_BinLayOver table:

16963,"42000",[Microsoft][ODBC SQL Server Driver][SQL Server]You cannot specify scroll locking on a cursor that contains a remote table.

16945,"42000",[Microsoft][ODBC SQL Server Driver][SQL Server]The cursor was not declared.

Please can you shed some light on this.

Thanks

Kelly(UserID=442345)

Antares686 SSC Guru Points: 125444 More actions · Answer 3

Sounds like you application is trying to create an invalid cursor for the data on the server side. Does the database you connect to get some data from a remote source, if so you app may need to use a client side cursor to acheive your goal.

Sugesh Kumar One Orange Chip Points: 27311 More actions · Answer 4

I hope you are using a SCROLL SURSOR remove the scroll keyword and check if the sql executes to success.

Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com