Repackaged Hyperion EPM 11.1.1.2 (just the client; i.e., desktop version) with InstallShield. Tried to install my resulting MSI, but I keep getting a 1606 error: "could not access network location %HYPERION_HOME%\common\config\9.5.0.0."

From what I've read on AppDeploy and elsewhere, the issue is that the installer thinks %HYPERION_HOME% is a network location rather than the local PC (I think). There are only two tables in the MSI that reference the path %HYPERION_HOME%\common\config\9.5.0.0: the Property table and the Registry table.

Here's what the verbose log looks like when it gets to the 1606 error:

MSI (c) (58:54) [13:34:27:748]: PROPERTY CHANGE: Adding _ property. Its value is 'C:\WINDOWS\system32\spool\drivers\w32x86\3\'.
MSI (c) (58:54) [13:34:27:779]: Note: 1: 1314 2: %HYPERION_HOME%\common\config\9.5.0.0
MSI (c) (58:54) [13:34:27:779]: Note: 1: 1606 2: %HYPERION_HOME%\common\config\9.5.0.0
MSI (c) (58:5C) [13:34:31:578]: Note: 1: 2731 2: 0
Error 1606.Could not access network location %HYPERION_HOME%\common\config\9.5.0.0.
MSI (c) (58:54) [13:34:55:777]: Product: Hyperion EPM -- Error 1606.Could not access network location %HYPERION_HOME%\common\config\9.5.0.0.
MSI (c) (58:54) [13:34:55:793]: Note: 1: 1606 2: %HYPERION_HOME%\common\config\9.5.0.0
Error 1606.Could not access network location %HYPERION_HOME%\common\config\9.5.0.0.
MSI (c) (58:54) [13:35:51:446]: Product: Hyperion EPM -- Error 1606.Could not access network location %HYPERION_HOME%\common\config\9.5.0.0.
Action ended 13:35:51: CostFinalize. Return value 3.


Can anyone suggest what I could try to troubleshoot? Thanks.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
What is %HYPERION_HOME%?
Answered 09/09/2009 by: AngelD
Red Belt

Please log in to comment
0
It SHOULD be C:\Hyperion. But since that isn't defined anywhere in the MSI, then no wonder the install doesn't know what %HYPERION_HOME%\common\config\9.5.0.0 is. Or anything beneath %HYPERION_HOME%, right?

So if that's right, then I reckon my next task is to go do some reading so I can learn how to add %HYPERION_HOME% as the default directory, rebuild my MSI, and retest.
Answered 09/09/2009 by: RonW
Green Belt

Please log in to comment
0
Still getting the same error 1606. I thought maybe because there wasn't a TARGETDIR specified in the Directory table, I should add one, so I added this:

Directory Directory Parent DefaultDir
TARGETDIR SourceDir

Then added this to the Proprty table:
Property Value
SourceDir Hyperion

But still got the same error.

Also discovered when I do the install manually, it spits out a batch file that contains these two lines:
set HYPERION_HOME=C:\Hyperion
set HYPERION_HOME_ID=1

When looking at my verbose installation log, I don't see any reference to that batch file having run.

I also tried running my initial version of the MSI, the one where I didn't modify any of the tables. First I ran the batch file, then the initial MSI, but got the same error.

So I'm not sure if I haven't set the table entries correctly for TARGETDIR, or if I need to add the batch file to the MSI, or what to try next.
Answered 09/10/2009 by: RonW
Green Belt

Please log in to comment
0
Also discovered when I do the install manually, it spits out a batch file that contains these two lines:
set HYPERION_HOME=C:\Hyperion
set HYPERION_HOME_ID=1
In all likelihood, the batch file is being run by a Custom Action in the UserInterface sequence. If you run a command line with a 'quiet' argument, the UI sequence doesn't run, thus no batch file, no environment variables get set and the install is broken. You can test that easily enough by just setting the variables yourself before running the install.
Answered 09/11/2009 by: VBScab
Red Belt

Please log in to comment
2
You might want to search through your repackaged MSI for references to that environment variable and replace them with a property or the actual path. Apps that spawn custom actions that run scripts and create/leverage env variables are tough to repackage. Are you sure you can't get the vendor installer to go silent?
Answered 09/11/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
0
VBScab:
I've been trying the install without any quiet arguments, and I still get the error message.
I've also tried running the batch file manually, then verifying the variables were added as they appear if I install the vendor's package manually, and then installing my packaged MSI, and I get the same error message.

turbokitty:
No luck so far with a silent install. I posted to the Oracle forums to ask if anyone had any info, but no responses yet.
I'll try replacing those env variable references in the MSI with an actual path and see what happens.
Answered 09/11/2009 by: RonW
Green Belt

Please log in to comment
0
Turbokitty, replacing that variable with a hard-coded path worked. Thanks for the tip.
Answered 09/11/2009 by: RonW
Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity