NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

TestStand database logging problem: only the first character is put in the table.

Scott Richardson,
 
I can not install the new SQL Native Client SQL Provider. It asked  a newer service pack (my system is win2000 sp4 already).
 
I have a connection string in TestStand like this: "Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;Initial Catalog=pubs;Data Source=BDC2".
 
Right now I do not have other computers to test. But I have two win2000 computers having this problem still. I may try another XP or win2000 computer later when I have a chance.
 
Jaso
0 Kudos
Message 21 of 25
(1,634 Views)

Jaso -
I would like to contact you directly to try to speed up our communication. Can you contact our support and give them your contact information and ask them to send it to me in the TestStand group. I do not like to ask customers to post their contact information directly to the forums.

Scott Richardson
https://testeract.com
0 Kudos
Message 22 of 25
(1,614 Views)

Turns out that there is a known Microsoft bug where applications will be unable to read character data when the language of the server and the client are different. In this case they had a Chinese client and an English server. The Microsoft bug report describes how characters appear as "????" instead of the actual strings when read, http://support.microsoft.com/default.aspx?scid=kb;en-us;331999 . This was the result of an improper translation of single byte characters to two byte characters. It appears that the reverse can also happen in that the data sent to the server is translated from single byte to two byte characters but the extra bytes are zero, thus NULL terminated.

The suggested workaround is to add the bold text shown below to the connection string which tells the SQL OLEDB Provider to not autotranslate character data:

Provider=SQLOLEDB.1;Persist Security Info=False;Auto Translate=False

This fixed the reported problem.

Scott Richardson
https://testeract.com
Message 23 of 25
(1,576 Views)
Scott,

Found this forum while searching for a solution to the same error message only I'm using Windows XP. Funny thing, database logging has been working fine for the past (4) months or so and this happened with no apparent change to any windows regional settings. I have not tried your work around as of yet. I will keep you posted.

John


0 Kudos
Message 24 of 25
(1,484 Views)

John -
I would be interested in what you find. I would be interested in knowing if any updates from Microsoft were installed and what the regional settings for the local and server system.

Scott Richardson
https://testeract.com
0 Kudos
Message 25 of 25
(1,436 Views)