Translation Engine MS SQL Server - duplicate key error - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ...

Support forum of the software localization tool Sisulizer

.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Not logged in - Login | Register

.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Translation Engine MS SQL Server - duplicate key error

Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius

New Topic

Printer Friendly

Translation Engine MS SQL Server - duplicate key error - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support

Author

Post

Posted: Wed Jun 16th, 2010 10:31 am

Private Upload

Quote

SRehorek
Member

Joined:	Tue Jun 15th, 2010
Location:
Posts:	1
Status:	Offline

Hi,

I am trying to use MS SQL Server as translation engine storage.
Every time I start the action "save to translation engine" the following error is trown:

The statement has been terminated.
Cannot insert duplicate key row in object 'dbo.SLSOURCE' with unique index 'SLSOURCE1Idx'.

A second thing I noticed is (maybe couses the error?)
All special charaters in the table SLSOURCE column ValueTm are corrupted.
For Example...
Application shows: Ausführung
Database shows: AusfÃ¼hrung

Which SQL Server Codepage does Sisulizer expect?

(Sisulizer Enterprise-Edition 1.6.28)

Best regards
Stefan

Last edited on Wed Jun 16th, 2010 10:43 am by SRehorek

Private Upload

Quote

Posted: Wed Jun 16th, 2010 11:13 am

Private Upload

Quote

Markus.Kreisel
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Monschau, Germany
Posts:	2115
Status:	Offline

Hi Stefan,

The data in your database is encoded in UTF-8. Ã¼ stands for ü. It can be easily decoded while reading. This is probably not causing your problem.

The main problem is that Sisulizer 1.x is more than 2 years old. Sorry, but we can not support it anymore.

Can you please try the V2010 evaluation and see if the problem still exists. There had been many bug fixes and improvements since 2008.

Hope this helps

Markus

____________________
http://www.sisulizer.com - Three simple steps to localize

Private Upload

Quote

Current time is 08:46 am
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Translation Engine MS SQL Server - duplicate key error

Sisulizer software localization tool - Three simple steps to localize