Error - No InstallAnywhere location found: null

[dziants]

Am new to InstallAnywhere.
Have received an install application which was written For IA 2009, and am migrating it to IA 2011

I successfully loaded the iap_xml file to the new version of the tool, and through the advanced design it seems more-or-less OK.

Am still not able to do a build, and am receiving message:-

106: No InstallAnywhere location found: null

What do I need to do or check, to make the build successful?



The relevant portion of the build file is:

IALocation="C\:\\Program Files (x86)\\InstallAnywhere 2011 Enterprise"

IAProjectFile="${Server_Project_file}" 
Propertiesfile="src/main/resources/build.properties"   

/>
 

The uncommented properties in build.properties are:-

####Dont change this property file ######## 
###This is the property file being used by IA to build installers####

#######################################################
####    Author : ddd                                           ##############
####    ##########################################################

#Fri Nov 16 17:24:51 GMT+05:30 2007
com.zerog.ia.build.options.output.web=true
com.zerog.ia.build.options.output.location=C:\\build
com.zerog.ia.installer.options.stderr.redirect=C\:\\temp\\stderr.txt
com.zerog.ia.build.platform.windows.novm=true
com.zerog.ia.installer.options.platform.unix.ui.default=Console
com.zerog.ia.build.options.output.merge=false

I also tried (also options in comments) with property setting:-

IA_LOCATION=C\:\\Program Files (x86)\\InstallAnywhere 2011 Enterprise

in file Location.Properties and build code:-

IALocation="${IA_LOCATION}"

IAProjectFile="${Server_Project_file}" 
Propertiesfile="src/main/resources/build.properties"  
>

 

and received message, it seems indicating it would not accept a long path name:-

init:
[echo] Running installer build with C:\Program Files (x86)\InstallAnywhere 2011 Enterprise and ${env.IA_HOME} and DDM_Installer.iap_xml
[buildinstaller] Using Properties set in src\main\resources\build.properties
[buildinstaller] 'C:\Program' is not recognized as an internal or external command,
[buildinstaller] operable program or batch file.
[buildinstaller] Result: 1

MakeESD:
[echo] Installer Build is done

BUILD SUCCESSFUL
Total time: 0 seconds

[jerome_IA]

Hi,

don't you need to escape spaces like it is already done for backslashes?
IALocation="C\:\\Program\ Files (x86)\\InstallAnywhere\ 2011\ Enterprise"

--Jerome

[dziants]

jerome_IA wrote:
Hi,

don't you need to escape spaces like it is already done for backslashes?
IALocation="C\:\\Program\ Files (x86)\\InstallAnywhere\ 2011\ Enterprise"

--Jerome

Thank you, Jerome, for your reply.
I just tried this for the two tests both with and without using ${IA_LOCATION} property. It still didn't work, with the same error messages as before.

Actually I have a feeling that with using ${IA_LOCATION}, it resolved the path and so was able to complete the build. So why the 'C:\Program' is not recognized error in this case?

Tests using escapes on spaces:-

1) Results in build error - 106: No InstallAnywhere location found

IALocation="C\:\\Program\ Files\ (x86)\\InstallAnywhere\ 2011\ Enterprise"
IAProjectFile="${Server_Project_file}" 
Propertiesfile="src/main/resources/build.properties"  
/>

and

2) Does not result in build error but the 'C:\Program' is not recognized error.

 





IALocation="${IA_LOCATION}"

IAProjectFile="${Server_Project_file}" 
Propertiesfile="src/main/resources/build.properties"  
/>

Regards,
David

[dziants]

To clarify better my previous posting:-
With example 2, the path resolved to what can be considered a legal path so I assume because of that, the 106 error did not appear and the build with respect to ant succeeded.

Because it is, though, not the correct path due to the truncation till the first space character, the actual build of the installer iap_xml did not succeed. The normal solution of placing quotes around the path (at least using the possibilities I tried) or escaping the blanks causes the 106 error.

Unix forward slashes or using progra~2 , also did not help.

The iap_xml build does succeed through the advanced designer, and the problem is just with this ant build.

David

[jerome_IA]

In fact, the path should be set like this:

IALocation="C:\Program Files (x86)\InstallAnywhere 2011 Enterprise"

Check this thread http://community.flexerasoftware.com/showthread.php?t=192624

--Jerome

[dziants]

jerome_IA wrote:


In fact, the path should be set like this:

IALocation="C:\Program Files (x86)\InstallAnywhere 2011 Enterprise"

Check this thread http://community.flexerasoftware.com/showthread.php?t=192624

--Jerome

Hi Jerome,
Tried this exactly. If in Location.properties, then I receive error:-

105: No InstallAnywhere location found: null

If in createInstaller.xml, then I receive error (as before):-

[buildinstaller] 'C:/Program' is not recognized as an internal or external command,
[buildinstaller] operable program or batch file.
[buildinstaller] Result: 1

Regards,
David

[dziants]

jerome_IA wrote:
In fact, the path should be set like this:

IALocation="C:\Program Files (x86)\InstallAnywhere 2011 Enterprise"

Check this thread http://community.flexerasoftware.com/showthread.php?t=192624

--Jerome

I am reposting my reply from yesterday as I do not see that it reached the forum.


Hi Jerome,
Tried this exactly. If in Location.properties, then I receive error:-

105: No InstallAnywhere location found: null

If in createInstaller.xml, then I receive error (as before):-

[buildinstaller] 'C:/Program' is not recognized as an internal or external command,
[buildinstaller] operable program or batch file.
[buildinstaller] Result: 1

Regards,
David

[SunnyBoy]

Usually, this would be because the IA Installation is not successful.

Re-install and Register your IA. The issue might be solved.

[dziants]

I am using a Fully Functional LICENSED Edition of IA 2011. 🙂
Maybe I should uninstall, and then re-install on a pathname that does not contain blanks.

A number of questions:-
a) If I reinstall to a different directory on the same machine, will there be any ramifications to my current license key, or will I need a new one?

b) After a reinstall of IA, will there be any problems in using the existing iap_xml (as I have successfuly been making modifications using GUI, and I don't want to loose these) ? I notice that in that file at the beginning, there is essential authorization and configuration data, and I don't know what effect a reinstall of IA will have on this.

c) Will I also need to reinstall the SP ?

I would much prefer not to do a reinstall, and leave IA in this location

C:\Program Files (x86)\InstallAnywhere 2011 Enterprise

, but if I have no choice, that is what I might have to do.

Am happy for any other ideas.
Many thanks in advance,
David

[jmishra]

Hi,

Path should be "< IALocation="C:\\Program Files (x86)\\InstallAnywhere 2011 Enterprise"> .

Can you try this ?

[dziants]

jmishra wrote:

Hi,

Path should be "< IALocation="C:\\Program Files (x86)\\InstallAnywhere 2011 Enterprise"> .

Can you try this ?

Thank you for your response. This is one of the scenarios I tried, but without the in the property definition, and without an extraneous " (open quote). I.E. I did

IALocation="C:\\Program Files (x86)\\InstallAnywhere 2011 Enterprise"

This did not work. Did you mean I should actually put angled brackets there, or is this to show a quote in the posting?

A few days ago, I received a notfication for sp3 (I downloaded and installed sp2 when installing after the purchase). I saw that sp3 was a new installaion (as it did not allow me to override my current installation), and so I installed in a new directory (not default) which was without blanks in the path name and directly under C disk.

Continued to work successfuly using the GUI designer, after reentering my license file details.

Also, in the line interface, the path name is now resolved as I do not use blanks in the path name. Maybe SP3 would have been enough to solve the issue and I could have kept the default path. Have no idea, but this is (hopefully) no longer relevant now.

I have now jumped this hurdle, but I do have another problem with the command line mechanism build, and this I will present in a separate thread.