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.

Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 

 Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
Errors: TM backup and Access violation (importing .xls files) - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Wed Jun 27th, 2007 02:01 am
PM Private Upload Quote Reply
adi
Member
 

Joined: Sun Jun 17th, 2007
Location: New Zealand
Posts: 16
Status: 
Offline
I have had a few problems importing .xls files (Microsoft Excel 2002) into sisulizer, I get some error messages (see attached). I've managed to get around it by saving them as .txt but it's a bit of a pain. This also happens when exporting a sisulizer project as an excel file, then importing back, get a Access violation error.
Another problem I've had is that I can't roll back to a backup version of my translation memory (see error image attached). This also happens when I try to clear the TM.
Is there an easy way to edit an existing TM? I can't seem to figure out how to.

Attachment: errors.zip (Downloaded 3 times)

Last edited on Wed Jun 27th, 2007 02:12 am by adi

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 27th, 2007 03:03 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
adi wrote: I have had a few problems importing .xls files (Microsoft Excel 2002) into sisulizer, I get some error messages (see attached). I've managed to get around it by saving them as .txt but it's a bit of a pain. This also happens when exporting a sisulizer project as an excel file, then importing back, get a Access violation error.
I could not reproduce this. Can you send me .slp and .xls that you tried to import to

support (at) sisulizer.fi

Regards,
Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 27th, 2007 03:05 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
adi wrote: Is there an easy way to edit an existing TM? I can't seem to figure out how to.

Currently there is not easy way to edit existing TM. You can use the editing tool os the database to modify it but it is quite difficult.

We are currently working on TM Editor and it will be included to Sisulizer 2.0

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 27th, 2007 03:09 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
adi wrote: Another problem I've had is that I can't roll back to a backup version of my translation memory (see error image attached). This also happens when I try to clear the TM.

What is the TM database that you use? DBISAM, Access, or ?

Can you send the TM backup file (.stm) to me

support (at) sisulizer.fi

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 27th, 2007 08:10 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
I found a bug.  .XLS was mapped to be using XML parser. There was a mistake. I should have been .xsl (style sheets) and not .xls (Excel).

Sisulizer can only import and export Excel (.xls) files. It can not localize them. So you can not include them to SL project. The above bug allowed to choose them and that cause the error message. I added checking to XML parser that it will raise an exception if the file is not in XML (as in this case).

I am working on TM case now.

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 27th, 2007 08:22 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
It seems that the DBISAM table of your TM is corrupted. Try this

1) Choose Tools | Translation Engines
2) Select Tools sheet and click Clear the selected translation memory
3) Click Replace the current content ... as import the backup file

If this does not help delete, close Sisulizer, delete all files from <sldir>\TM directory (if you have the default TM location) and start Sisulizer again.

Jaakko

 



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 27th, 2007 10:39 pm
PM Private Upload Quote Reply
adi
Member
 

Joined: Sun Jun 17th, 2007
Location: New Zealand
Posts: 16
Status: 
Offline
I tried clearing the TM in the tools dialog, but it wont. Gives:
"DBISAM Engine Error #11013 Access denied to table or backup file 'SLTARGET'"
Sometimes gives 'SLUSER'/'SLINFORMATION'/'SLSOURCE'
Deleting the TM directory doesn't seem to change much. When I open the Translation engine dialog from the tools menu I get:
"Cannot perform this operation on a closed dataset"
The Translation engines are still displayed, but without any translations. If I try and remove a translation engine I get both of the above errors about 5 times each, and it wont delete.

Same thing happens when I 'Add new engine' using the "+" button. I can't remove it afterwards. So now I have about 5 different translation engines that have nothing in them, but can't remove them, clear them, or "replace the current content of the selected translation memory with a backup file".

I'm thinking it might just be a buggy build...
Are there any Stable releases of this software?

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 27th, 2007 11:17 pm
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
For some reason Sisulizer can not access or open the DBISAM tables.

What is your OS?

Where does your DBISAM TM locate? is it the default location (e.g. <sldir>\TM) or is it on some other localizaiton?

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 27th, 2007 11:20 pm
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
Can you send <sldir>\Sisulizer.slo file to

support (at) sisulizer.fi

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 27th, 2007 11:23 pm
PM Private Upload Quote Reply
adi
Member
 

Joined: Sun Jun 17th, 2007
Location: New Zealand
Posts: 16
Status: 
Offline
I'm running Windows XP SP2
Sisulizer 1.5.13
It's installed in the default location: "C:\Program Files\Sisulizer 1"
The TM saves to the default location "C:\Program Files\Sisulizer 1\TM"

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 27th, 2007 11:30 pm
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
DBISAM uses some hidden files. Try to remove the following directory
"C:\Program Files\Sisulizer 1\TM"

Start Sisulizer again. SL recreates the directory and creates new TM tables. After that import the TM backup file.

If this does not help check that you have write access to "C:\Program Files\Sisulizer 1\TM".

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 27th, 2007 11:39 pm
PM Private Upload Quote Reply
adi
Member
 

Joined: Sun Jun 17th, 2007
Location: New Zealand
Posts: 16
Status: 
Offline
----------"DBISAM uses some hidden files. Try to remove the following directory
"C:Program Files\Sisulizer 1TM"

Start Sisulizer again. SL recreates the directory and creates new TM tables. After that import the TM backup file."------------
Tried that, didn't work.

-------If this does not help check that you have write access to "C:Program Files\Sisulizer 1\TM".----------
This worked!!!!!! managed to delete the TM engines.
But every time I open Sisulizer.exe the TM folder becomes read-only again.

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 27th, 2007 11:57 pm
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
OK. This is because the access rights. When SL create the TM directory OS gives read only access rights.

You need to create the TM on a directory where you have full rights.

1) Choose Tools | Translation Engines
2) Press +
3) In the Database directory enter a directory where you have full access rights.
4) Press OK
5) Select Embedded and click -

This create a new TM and removed the current one. Now there might be problem removing the TM because read only access.

In that case open <sldir>\Sisulizer.slo into notepad. Locate the following element

  <translationengines>
    <engine kind="TDbisamTranslationMemory">
      <database type="dtDbisam" directory="TM"/>
    </engine>
  </translationengines>

Modify directory="TM" to contain the new directory. For example

directory="D:\MyFiles\TM"

Save the file and restart SL.

I am wondering if the default access right of the <sldir> is read only why could you install SL without problems.

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Thu Jun 28th, 2007 12:11 am
PM Private Upload Quote Reply
adi
Member
 

Joined: Sun Jun 17th, 2007
Location: New Zealand
Posts: 16
Status: 
Offline
That seems to have worked. Was even able to restore from my backup.
Thanks heaps

Back To Top PM Private Upload Quote Reply

 Posted: Thu Jun 28th, 2007 12:18 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
I try to figure out why the TM directory became read only. Does you login id has "Computer Administator" or "Limited" access rights?

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Thu Jun 28th, 2007 12:23 am
PM Private Upload Quote Reply
adi
Member
 

Joined: Sun Jun 17th, 2007
Location: New Zealand
Posts: 16
Status: 
Offline
I'm logged in to XP as a Computer Administrator with unrestricted access

Back To Top PM Private Upload Quote Reply

 Posted: Thu Jun 28th, 2007 12:37 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
Thanks. I start testing this.



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

Current time is 07:42 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Errors: TM backup and Access violation (importing .xls files)



WowUltra modified by Sisulizer Copyright © 2007-09 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize