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: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius Page:    1  2  Next Page Last Page  
New Topic Reply Printer Friendly
EOleSysError by .NET 4.6.1 - 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: Tue Mar 21st, 2017 05:59 pm
PM Private Upload Quote Reply
KingMichaelI
Member
 

Joined: Wed Oct 12th, 2011
Location:  
Posts: 43
Status: 
Offline
We upgraded the framework version from 4.0 to 4.6.1
Sisulizer fails to localize the project with error

EOleSysError: An attempt was made to load a program with an incorrect format.

Back To Top PM Private Upload Quote Reply

 Posted: Tue Mar 21st, 2017 07:45 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2903
Status: 
Offline
Where does the error show?

Sounds like your applicatian tries to load an OLE-file that is not registered in the system. Or perhaps it can't be registered and loaded since it is still .NET 4.0.

Did you compile your original in full and did a scan for changes in Sisulizer.

Markus



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

 Posted: Thu Mar 23rd, 2017 03:59 pm
PM Private Upload Quote Reply
KingMichaelI
Member
 

Joined: Wed Oct 12th, 2011
Location:  
Posts: 43
Status: 
Offline
It is shown in the Sisulizer output window

Back To Top PM Private Upload Quote Reply

 Posted: Thu Mar 23rd, 2017 04:00 pm
PM Private Upload Quote Reply
KingMichaelI
Member
 

Joined: Wed Oct 12th, 2011
Location:  
Posts: 43
Status: 
Offline
Something like this:

Attachment: Untitled.png (Downloaded 31 times)

Back To Top PM Private Upload Quote Reply

 Posted: Thu Mar 23rd, 2017 04:01 pm
PM Private Upload Quote Reply
KingMichaelI
Member
 

Joined: Wed Oct 12th, 2011
Location:  
Posts: 43
Status: 
Offline
I uploaded two files, old version which works and new which doesn't.

Back To Top PM Private Upload Quote Reply

 Posted: Fri Mar 24th, 2017 10:29 am
PM Private Upload Quote Reply
KingMichaelI
Member
 

Joined: Wed Oct 12th, 2011
Location:  
Posts: 43
Status: 
Offline
We have about 5 different projects with the same problem.

Back To Top PM Private Upload Quote Reply

 Posted: Thu Mar 30th, 2017 07:46 am
PM Private Upload Quote Reply
KingMichaelI
Member
 

Joined: Wed Oct 12th, 2011
Location:  
Posts: 43
Status: 
Offline
Are there any ideas where to look?

Back To Top PM Private Upload Quote Reply

 Posted: Thu Mar 30th, 2017 08:08 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2903
Status: 
Offline
Can you perhaps try to create a new Sisulizer project and import the translations into it. Perhaps somewhere is a leftover that causes to mix .NET versions.

Markus



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

 Posted: Fri Mar 31st, 2017 12:05 pm
PM Private Upload Quote Reply
KingMichaelI
Member
 

Joined: Wed Oct 12th, 2011
Location:  
Posts: 43
Status: 
Offline
We tried it with the same result. I have uploaded the bug report file.

Back To Top PM Private Upload Quote Reply

 Posted: Wed Apr 5th, 2017 12:35 pm
PM Private Upload Quote Reply
KingMichaelI
Member
 

Joined: Wed Oct 12th, 2011
Location:  
Posts: 43
Status: 
Offline
Hi Markus.

We are really under pressure right now (release in a week). Localization is suddenly one of the things which is stopping us. Is there anything we can do to assist you with troubleshooting?

Back To Top PM Private Upload Quote Reply

 Posted: Wed Apr 5th, 2017 01:30 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2903
Status: 
Offline
I asked R&D about the status.

Markus



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

 Posted: Wed Apr 5th, 2017 01:41 pm
PM Private Upload Quote Reply
KingMichaelI
Member
 

Joined: Wed Oct 12th, 2011
Location:  
Posts: 43
Status: 
Offline
I did some debugging with Process Monitor and other tools and found that the problem is in the temporary .res file which is not found by al.exe
If I run all the steps manually and put the res file in the right location - everything works like it should. Zip with details is uploaded.

Back To Top PM Private Upload Quote Reply

 Posted: Wed Apr 5th, 2017 01:44 pm
PM Private Upload Quote Reply
KingMichaelI
Member
 

Joined: Wed Oct 12th, 2011
Location:  
Posts: 43
Status: 
Offline
Here is the call to al.exe without and with correct res file in the temp location.

Attachment: Untitled.png (Downloaded 15 times)

Back To Top PM Private Upload Quote Reply

 Posted: Wed Apr 5th, 2017 01:46 pm
PM Private Upload Quote Reply
KingMichaelI
Member
 

Joined: Wed Oct 12th, 2011
Location:  
Posts: 43
Status: 
Offline
Here is a call from al.exe

Attachment: Untitled.png (Downloaded 15 times)

Back To Top PM Private Upload Quote Reply

 Posted: Thu Apr 6th, 2017 03:44 am
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1937
Status: 
Offline
I tried to compile you files by using the Compile.bat found in the zip file you sent. The satellite compiled without errors. Then I tried the situation where the output directory "en" did not exist. Then I got the same error message:

ALINK: error AL1019: Metadata failure while creating assembly -- The system cannot find the path specified.

Sisulizer tries to create the output directory before calling Al.exe. Maybe it is so that there is no access rights to create the en directory:

".\Release\Localization\en"

Check if that directory is created after the build process.

If it not then try to put the output directory to default an try again.

Ilkka



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

 Posted: Thu Apr 6th, 2017 07:53 am
PM Private Upload Quote Reply
KingMichaelI
Member
 

Joined: Wed Oct 12th, 2011
Location:  
Posts: 43
Status: 
Offline
Hi Ilkka.
I had the same problem with en directory, had to create it manually. After this correction I had one more problem with res file, had to put it in the expected path and then everything went well. The en directory does not exist before localization. It should be created by Sisulizer as an output directory, and it seems that Sisulizer creates it, but not in ".\Release\Localization". It creates it directly in the .\Release directory. Could that be a reason for the failure?

Back To Top PM Private Upload Quote Reply

 Posted: Thu Apr 6th, 2017 01:23 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1937
Status: 
Offline
Can you send your Sisulizer project file (.slp). I need to see the settings you have in your .NET source.

Ilkka



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

 Posted: Thu Apr 6th, 2017 03:24 pm
PM Private Upload Quote Reply
KingMichaelI
Member
 

Joined: Wed Oct 12th, 2011
Location:  
Posts: 43
Status: 
Offline
Done

Back To Top PM Private Upload Quote Reply

 Posted: Wed Apr 12th, 2017 11:18 am
PM Private Upload Quote Reply
KingMichaelI
Member
 

Joined: Wed Oct 12th, 2011
Location:  
Posts: 43
Status: 
Offline
Hi Ilkka, any news?

Back To Top PM Private Upload Quote Reply

 Posted: Wed Apr 12th, 2017 01:52 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1937
Status: 
Offline
I tested scanning and building localized files. it worked just fine. I noticed that your assembly uses .NET 4.6.1. However the error report files you sent did use .NET 4.0.

Is it possible that the machine where you use Sisulizer does not have .NET 4.6.1 but still uses .NET 4.0.

Can you do this.
1) Open you .slp
2) Go to Output sheet and right click
3) Choose Properties
4) Check Detailed
5) Build your project again. Now you should get a lot more in the output log
6) See from the log what .NET version Sisulizer uses.

If .NET is NOT 4.6.1 check if it is installed. If it is please copy that text, save to a file and send to me.

Ilkka



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

Current time is 09:06 pm Page:    1  2  Next Page Last Page    
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > EOleSysError by .NET 4.6.1



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