Hi,
we are using nav 5.0 sp1 with sql server 2005 sp3.. client build number is 30488.. system gives ODBC sql server driver "string data, right truncation" error when posting documents or journals.but there is no possible reason behind it. this error raises sometimes.. the only solution to post document is closing and re opening nav client.
the worse thing in this scnerio is corrupted data. when user A gets this error and try to post again again, If user B post something different at the same time, corrupted data exists. for example, purchase invoice without G/L entries.. bank account ledger entries without G/l entries etc.
i am sure that there is not possible cause for this. no commit in anywere or commented code lines for inserting data. ( G/L entries are inserted on in cu 12.. there is no problematic chnages in cu 12.).
anyone see this problem before?
best regards.
0
Comments
client build number 32083
I know that this is an old post, but I am facing the same issue these days and I was unable to find solution. Recently we have upgraded one of our customer servers from SQL Server 2005 Express to SQL Server 2008 R2 Standard Edition. Version of Nav client is 5.0 SP1. There are no specific steps to reproduce error, but sometimes when user tries to enter journal or post document - transaction is rolled back and message pops up:
Error: [Microsoft][ODBC SQL Server Driver] String data, right truncation. ID state: 22001
After message is closed and same line is re-entered again, posting or entering data to journal goes without any warning or error. I have found some hotfix referring to this error but the files inside are older then files that are installed on customer machines.
https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?scid=kb;en-us;940043
So far I was unable to figure out what causing this behavior. Any help would be appreciated.
Thank you
Same thing here. Less than two weeks ago, we switched from SQL Server 2005 to a more recent version.
Same error message pops up randomly when posting whatever. The message does not show up when you try again.
Just like the post prior to this one, I have checked Microsoft's KB, and the files listed are older than the ones we currently are using.
Does anyone have a solution to this ?!
Regards,
PM