Infralution Support Forum Index Infralution Support
Support groups for Infralution products
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Translator edition behaving as Developer edition

 
Post new topic   Reply to topic    Infralution Support Forum Index -> Globalizer Support
View previous topic :: View next topic  
Author Message
andythevelein



Joined: 03 Jun 2010
Posts: 2

PostPosted: Thu Jun 03, 2010 2:03 pm    Post subject: Translator edition behaving as Developer edition Reply with quote

Hi,

One of our translators has a problem with the Translator edition of Globalizer.NET. He has installed TE, but it behaves like a non-registered Developer edition. The application title bar says "Developer Edition".

The translator was not able to open the workspace we sent him because it contains 20.000+ translations. This cannot be opened with an unregistered version of the Developer Edition.
Due to time constraints, we were forced to activate our Pro license on his version so he could continue to work. This is of course against license agreements.

Which steps do we need to take to make the Translator edition work?

Thanks for your reply,

Andy Thevelein
Back to top
View user's profile Send private message
Infralution



Joined: 28 Feb 2005
Posts: 5027

PostPosted: Thu Jun 03, 2010 10:35 pm    Post subject: Reply with quote

What version of Globalizer.NET are they using?

The simplest thing is probably to uninstall Globalizer.NET (both Translator and Developer). Then manually delete the Program Files\Infralution folder (if it still is there and has contents). Then reinstall Globalizer.NET Translator edition.

Before they do this you should get them to uninstall the Developer License (by running Globalizer.NET and selecting Tools->License)
_________________
Infralution Support
Back to top
View user's profile Send private message Visit poster's website
Hernan Martinez



Joined: 19 Nov 2009
Posts: 13

PostPosted: Thu Sep 16, 2010 4:12 pm    Post subject: Reply with quote

I'm having the same problem now. I downloaded the last version 2.3.5 and deleted everything as you said.
Can it be related to the operating system? This PC is using Windows Server 2003 SP2 in English. We don't normally use those OS for development around here but that is the only one that the locale is not Spanish and I want to test the translators environment and redact a document with our policies and workflow.
Back to top
View user's profile Send private message
Infralution



Joined: 28 Feb 2005
Posts: 5027

PostPosted: Thu Sep 16, 2010 11:50 pm    Post subject: Reply with quote

Some research reveals that this may be an bug with the way Windows Server 2003 handles .NET config files. The Globalizer.exe.config file (under the Program Files\Infralution\Globalizer.NET Translator Edition folder) contains the setting that indicates the mode Globalizer.NET should run in. It sounds like the config file is not loading correctly.

This post on MSDN indicates that under Server 2003 config files for executables don't work as they do on all other operating systems. Instead of being named App.exe.config they must be named App.config.

So the workaround may be to rename the "Globalizer.exe.config" file to "Globalizer.config". Let us know if this works for you - if so we will change the setup to include both files so that this issue doesn't occur.
_________________
Infralution Support
Back to top
View user's profile Send private message Visit poster's website
Infralution



Joined: 28 Feb 2005
Posts: 5027

PostPosted: Fri Sep 17, 2010 12:07 am    Post subject: Reply with quote

Another MSDN Blog we have found indicates that this is a bug in Server 2003. But it indicates a different fix. This would require some changes to the embedded manifest. If you want we could try this and then email you the modified exe to see if it fixes the problem. We would then include it in the next release.
_________________
Infralution Support
Back to top
View user's profile Send private message Visit poster's website
Infralution



Joined: 28 Feb 2005
Posts: 5027

PostPosted: Fri Sep 17, 2010 8:04 am    Post subject: Reply with quote

I have created a patched version of Globalize.exe (Version 2.3.5) that includes the workaround described in the MSDN article above. You can download this from:

www.infralution.com/downloads/GlobalizerPatch2-3-5.zip

Just unzip the exe and replace the existing exe in the Program Files\Infralution\Globalizer.NET Translator Edition folder. Let us know if this fixes the issue for you and we will then include the fix in the next release.
_________________
Infralution Support
Back to top
View user's profile Send private message Visit poster's website
Hernan Martinez



Joined: 19 Nov 2009
Posts: 13

PostPosted: Fri Sep 17, 2010 10:11 am    Post subject: Reply with quote

The exe inside the zip didn't work. Having two configs (Globalizer.exe.config and Globalizer.config) did though.
For me the last workaround is enough as we don't expect that our translators will be using Windows Server 2003.
Back to top
View user's profile Send private message
Infralution



Joined: 28 Feb 2005
Posts: 5027

PostPosted: Wed Sep 22, 2010 4:32 am    Post subject: Reply with quote

Version 2.3.6 of Globalizer.NET has now been released and includes a fix for this issue. It includes both Globalizer.exe.config and Globalizer.config files to enable support for running the Translator Edition on Windows Server 2003.
_________________
Infralution Support
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    Infralution Support Forum Index -> Globalizer Support All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group