An ODBC error occurred, but no error information

Sog

SLQ 2008 R2
NAV 4.0 SP3
Scenario: Sales-post is called by a document, in codeunit 22, the insertitemledgerentry function is going into error on a random document line when it is called by itemqtyposting function. (although it's always the same line in a document, no relation between the different lines that give the error is detected)

Error:
"An ODBC error occurred, but no error information could be retrieved.
Contact your system manager."

And I can't find anything that might give me more information, no erors in eventvwr or sqllog.

client montior shows me this:

Item ledger entry:[??][item ledger entry no][item no.],[date],[sourcetype (customer) ],[Source No],[location code],[quantity],[quantity remaining], ...

This one works: previous lines aswell that are applied (this one isen't, see remaining quantiyt -6.0000)
exec sp_execute 99,20831957,'B7167','2012-06-13 00:00:00',1,'12270','SH212009290','','NEWWHS',-6.00000000000000000000,-6.00000000000000000000,0,0,1,'','',0,1,0,'','','FR','','2012-06-13 00:00:00','A1223-0166','','','S-SHPT','','',1.00000000000000000000,'PC',0,'','','',0,'203',0,'','','',0,'1753-01-01 00:00:00',0,0,0,0,'','','','1753-01-01 00:00:00','1753-01-01 00:00:00',''

This one does not work, 
exec sp_execute 99,20831958,'B7189','2012-06-13 00:00:00',1,'12270','SH212009290','','NEWWHS',-1.00000000000000000000,0,0,0,0,'','',0,1,0,'','','FR','','2012-06-13 00:00:00','A1223-0166','','','S-SHPT','','',1.00000000000000000000,'PC',0,'','','',0,'203',0,'','','',0,'1753-01-01 00:00:00',0,0,0,0,'','','','1753-01-01 00:00:00','1753-01-01 00:00:00',''

Steps taken:
Compile everything again and synchronise users.

I'm at a loss, has anyone seen a similar error and/or behaviour, or does anyone have suggestions to try some steps?

davmac1

do you have any custom code that is adding item ledger entries? Possibly you have duplicate primary keys because the entry no. is being used twice in some circumstances.

Sog

No custom code has been added in cu 22.
The ledger entry no. is unique, but it probalby has something to do with the sbs problems we had.
We're currently rebuilding the indexes, we hope that that might resolve the issue.

postsaurav

Hi @Sog ,
Were you able to solve the issue?
Please update how you resolved it.

Sog

Hi @postsaurav ,
It's been years since I've had this issue. Unfortunately, I can't recall if and how we've solved this issue. But the last attempt I've mentioned may be the solution, since I didn't respond/update the topic after this.