|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Problem running translated exe
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Problem running translated exe
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Problem running translated exe - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
YukonPete Member
|
Using Sisulizer Pro Version 3 Build 325. Programming Language: Delphi XE2 Application is 32 bit English to Serbian When I build the application in Delphi and run it, all is well. When I build the translated application and attempt to run it, I get the following error: "The application has failed to start because its side-by-side configuration is incorrect." If I compile the same application in Delphi XE and then build the translated exe it runs correctly. Any thoughts? Thanks, Lee
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator 
|
Can you zip both original English EXEs (build by XE and build by XE2) and both Serbian EXEs into a zip file and send zip to us. Click Private Upload to send the file. Edit: Can you please add your Sisulizer project file (.slp) into the zip as well. Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
YukonPete Member
|
I will try and send them to you yet tonight. It may not be until tomorrow. Thanks, Lee
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Lee, despite the fact that we did not get your sample data we googled for that error message, and we found it is a problem related to the so called DLL hell. Microsoft invented a new system in Windows 7 that should prevent you from using outdated DLLs. So if you have installed two or more DLLs with the same version and file name but different binary data you will see that error message. The message text is a bit misleading but can happen anytime to end users. This is not related to Sisulizer but any development tool. The first step to overcome this is to un-install the other instances of the DLL. Leave the creating of the language resource DLLs only to Sisulizer and do not create localized DLLs (create only the ones in the original language) with your development tool in parallel. This should remove the error message. Btw: Even sending your files will not help us to remove the problem from your system while it will not happen on our systems where the other conflict DLLs do not exist. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
YukonPete Member
|
Markus; If that is the problem then why this? I took the same exe file and translated it using one of your competitor's products. It runs fine. Also, tell me why I do not get the error message when I run the English version? Both exe's use the same DLLs. Lee
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
YukonPete Member
|
Also, I need some clarification with this: "Leave the creating of the language resource DLLs only to Sisulizer and do not create localized DLLs (create only the ones in the original language) with your development tool in parallel. This should remove the error message." I am not creating resource DLL's with Sisulizer. But then again, I am not sure what you mean when you refer to resource Dll's. I am having Sisulizer create a new exe, not Dll's. So if that is what you mean by resource DLL's, I am not doing it. Also I do not understand what you mean by "do not create localized DLL's with your development tool in parallel". Lee
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
YukonPete Member
|
I too googled the 'dreaded dll hell". I have 2 DLL's that are used by my application. Neither of them is registered with Windows. They are used for licensing my application. Would I get this same error message on every computer I attempt to execute it on? Would that mean that every computer I execute it on has the same problem? Lee
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Lee, You are the first person we heard about that problem at all. If you Google for that problem you will find many places where users and developers report about that error message. We also do not have more info about that. It seems to be clear that the message is shown if two or more DLLs of the same name with a different in binary are loaded at the same time. It is to avoid that an application calls a DLL function that is not available. Sample: Application A uses utility.dll 1.0 Application B uses utility.dll 1.1 If A is started it loads utility.dll 1.0 into memory. Since there can be only one utility.dll at once in memory Application B can not load utility.dll 1.1. If B calls a function new in version 1.1 it will crash. The error you have seen is to avoid that crash. Since we did not have sample data from you I was wild guessing that you perhaps generated language DLLs with Delphi that conflicted with some created by Sisulizer. It also may be about other DLLs in your system. Of course we would be interested in finding out the reason. Perhaps there is something we can do to avoid that problem. Btw: What option did you choose under Project - Edit Source - <your source> - File? If you have chosen Resource DLLs or Embedded resource DLLs Sisulizer creates language DLLs (what is the recommended way by Embarcadero). Does it also happen if you create Localized Files or Multilingual File? Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
YukonPete Member
|
Why does the exe file created by your competitor run perfectly fine? I believe I am creating what you call a Localized File. What a Localized file means to me is this: I can my English exe file. I then right click the exe file included in the project and select "Build in Selected Language". This creates the new exe file of the translated language (Serbian). When I run this exe file is when I get the error. If you want, I can send you everything including an install so that you can actually run the program in English and attempt to run it in Serbian. Lee
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
YukonPete Member
|
I also have looked up the error in Windows Event Viewer: I go to Windows Event Viewer. I locate the Side-by-side error. Here is what it says: Activation context generation failed for "C:DairyQuest Main\source\DQWin.exe".Error in manifest or policy file "C:DairyQuest Main\source\DQWin.exe" on line 8. The value "" of attribute "processorArchitecture" in element "assemblyIdentity" is invalid If I interpret this correctly, the attribute "processorArchitecture" should be "win32". Instead, it is empty. Lee
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Lee, If you use "Build in Selected Language" the settings from the Project - Edit Source - <your source> - File are used. I guess that the default settings of the other tool are different. By default Sisulizer uses the method Embarcadero recommends to localize Delphi apps. Please send us your sample data. Please also include you .slp so we can see what setting you used. Please use the "Private Upload" button right above this post. It helps us to keep track of uploads and forums posts. Please remember to zip your files before you upload them. We try to reproduce the problem. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Thanks for the additional input. With your sample data we will be able to look into this. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Ilkka.Salmenius Administrator
|
There was a bug in Sisulizer. It localized the manifest file incorrectly. I will fix this soon. A workaround is to turn off manifest localization. 1) Right click you EXE file in the project tree and choose Properties. A source dialog appears. 2) From the source dialog select Resources sheet and uncheck Manifest resource. 3) Rebuild the project and your Serbian EXE should work. Thank you for the report and I am sorry about the inconvience this bug caused to you. Best regards, Ilkka Attachment: Untitled.png (Downloaded 7 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator
|
I fixed this. The fix will be in the next build (329). In the meantime do not check manifest resource in the resource list. Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 10:15 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Problem running translated exe | |
Sisulizer software localization tool - Three simple steps to localize
