Hi

Everytime I go to create a new .msi using SetupCapture (windows installer) I get through to Grouping files with registration and it chokes and says a particular java version is not installed properly.

Any hints on getting rid of it?
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
Hello Luke.
Depending on version of java I think it already is a MSI so (usually) no need make a setupcapture on it.
Check out the Package Knowledge Base:
http://www.appdeploy.com/packages/browse.asp?cat=alpha&str=j

/Mackan
Answered 08/04/2008 by: Mackan75
Orange Belt

Please log in to comment
0
Hi, Marcus. I think you misunderstand. I don't think the OP is trying to capture JRE, rather the app he's capturing requires JRE.

@Blade2 - ALWAYS install pre-requisites first BEFORE you start the capture process. Typical 'gotchas' are JRE, MDAC, InstallShield engines...I'm sure I'll think of others as the day progresses. I'm afraid only experience will show you what pre-reqs a package has. In the meantime, be prepared to abandon captures when you realise that the package is putting down pre-reqs.
Answered 08/05/2008 by: VBScab
Red Belt

Please log in to comment
0
Hi Ian, well yes, I probably misunderstood, read the question to fast and wanted to help [;)]

/Mackan
Answered 08/05/2008 by: Mackan75
Orange Belt

Please log in to comment
0
NP, Marcus. We've all been there, me perhaps more than most :) Keep your posts coming.
Answered 08/05/2008 by: VBScab
Red Belt

Please log in to comment
0
Thanks for the posts guys, not entirely sure it is a pre-requisite as this one showed up in my Last three attempts at a package job, one of which was FireFox3. But the first time this showed up, I installed what it said was missing and several more flavours of Java even the very latest version to no avail.

Any further musings?
Answered 08/05/2008 by: blade2
Blue Belt

Please log in to comment
0
ORIGINAL: blade2
not entirely sure it is a pre-requisite
There's an easy way to find out: just monitor the Javasoft folder, normally 'C:\Program Files\Java'. If a new folder appears there, a new JRE is being installed. It ain't rocket science! :)
Answered 08/05/2008 by: VBScab
Red Belt

Please log in to comment
0
Cheers, will have a look at that, i am off to sleep.

Thanks
Answered 08/05/2008 by: blade2
Blue Belt

Please log in to comment
0
I think it is caused by the application that installs some java runtime file in its own folder. I am assuming here that you are using Wise, Wise checks for the registration flag inside the dlls and tries to register these files to extract the com registration which then fails, hence the popup. You should turn off Enhanced File and Registry Key Association in the setupcapture configuration screen if you get the popups and try again, or just learn to live with the ghost of java as this Wise option can be usefull.
Answered 08/05/2008 by: pgiesbergen
Orange Belt

Please log in to comment
0
I see this message a lot when capturing the Hyperion System 9 applications, such as the excel addin, Hyperion Reports, and Hyperion Essbase Administration Services. Reports was basically unpackageable for a lot of reasons, but I was able to get around this with the excel addin and EAS.
Basically i just clicked ok on these, and let it finish.

Don't know if this is related, but in both cases, when trying to install the msi, it gives you an Internal Error 2714 - referencing a strange looking path like ZZ lib\ etc.
If you open your msi, you will probably see a bunch of folders on the root that look like "lib" and "bin" and "zz" etc.
I've found that the only way to address this is to go to the Directory table and remove all the strange INSTALLDIR entries - usually with lib and bin and zz in them - but be careful not to delete necessary ones. I found about 90 INSTALLDIR directories, only 2 were necessary.
Step two would be to then go to the CreateFolder table and get rid of those folders there "they should be hightlighted in red now because of what you did in step 1)
In both cases, the msi installs fine now.
Answered 08/05/2008 by: DevilsArcade
Senior Yellow Belt

Please log in to comment
0
That nailed it.

Thanks pgiesbergen.

and thanks to everyone else for the inputs.
Answered 08/05/2008 by: blade2
Blue Belt

Please log in to comment
0
ORIGINAL: pgiesbergen

You should turn off Enhanced File and Registry Key Association in the setupcapture configuration screen if you get the popups and try again, or just learn to live with the ghost of java as this Wise option can be usefull.

I would recommend having this option turned off always, more hassle then happy-endings.
Answered 08/05/2008 by: AngelD
Red Belt

Please log in to comment
0
ORIGINAL: DevilsArcade
I see this message a lot when capturing the Hyperion System 9 applications, <snip>

Don't know if this is related, but in both cases, when trying to install the msi, it gives you an Internal Error 2714 - referencing a strange looking path like ZZ lib\ etc.
No, it's not related, but SNAP! I found every Hyperion MSI I've encountered to need fixing up in some way or other. Their packaging is a joke and what QA do they do?!? I don't believe they even test their packages before sending them out.
Answered 08/06/2008 by: VBScab
Red Belt

Please log in to comment
0
Cheers or the tip about turning that off and keeping it off. And I will keep a wary eye out for Hyperion msi's.
Answered 08/06/2008 by: blade2
Blue Belt

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