This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: Can't register "build" version of install anywhere
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
Feb 21, 2011
12:08 PM
Can't register "build" version of install anywhere
Hi all -
I've tried registering via the command line my installation of IA 2010 but to no avail, I keep getting the "This evaluation has expired" messages.
Any suggestions?
I've tried registering via the command line my installation of IA 2010 but to no avail, I keep getting the "This evaluation has expired" messages.
Any suggestions?
(3) Replies
Feb 22, 2011
01:47 PM
I had some trouble with my command line build installation which required reregistering it. It had not expired, but perhaps this will help your situation too. Here's what I was told:
1. Please rename/delete the file named ‘IAKey.class’ from “C:\Documents and Settings\\InstallAnywhere\110\Enterprise\info” location.
2. Then in command prompt, go to the directory where you have installed the IA and which has build.exe file. Use build.exe -register license_number to register IA. E.g. build.exe -register abcd-12345-uvwxyz. Then launch the IDE again
1. Please rename/delete the file named ‘IAKey.class’ from “C:\Documents and Settings\
2. Then in command prompt, go to the directory where you have installed the IA and which has build.exe file. Use build.exe -register license_number to register IA. E.g. build.exe -register abcd-12345-uvwxyz. Then launch the IDE again
Feb 24, 2011
01:32 PM
I foolishly thought that if I registered as my user on the build machine, that the build user would also have access.
Apparently not (at least in the windows world).
I re-ran the registration steps as the build user and the problem went away.
Apparently not (at least in the windows world).
I re-ran the registration steps as the build user and the problem went away.