/build/static/layout/Breadcrumb_cap_w.png

New to MSI and got an error - please help!

Hi

Am new to all this MSI building and am doing my first one now, which I thought could be a nice simple one to do, except it has to be done by the middle of next week! Eeek.

Doing IBM Tivoli Enterprise COnsole 3.9, and after packaging and compiling am getting the following when trying to test it:
Internal Error 2714 jre_binljre/bin

Please could anyone hazard a guess as to where I've gone wrong and let me know! I got some ICE03 errors but cannot see what needs to be done to correct them either.

Sorry about this, new to it all and (most likely) being a complete muppet!

Jo

0 Comments   [ + ] Show comments

Answers (3)

Posted by: WiseUser 18 years ago
Fourth Degree Brown Belt
0
It's an easy one - you've got "jre_binljre/bin" in the "DefaultDir" column of your "Directory" table - which is incorrect (because "/" is not a valid character in a directory name).

What repackaging tool are you using?
Posted by: Jojo 18 years ago
Yellow Belt
0
Have just installed Wise 5.5 I think (sorry at home now and have forgotton which version it is!)
Is that an easy one to correct?
I did the Wise course 3 months ago and my company has only just bought the software, so it's a bit of a shock to the system trying to remember what we did in the lab environment.
Many thanks for the reply though [:)]
Posted by: WiseUser 18 years ago
Fourth Degree Brown Belt
0
I'm surprised this has happened at all if you're using WPS5.5 - I've never seen it do anything like that.

Although it's not a difficult problem to fix, it's not easy to explain either. It may be easier for you to start over? Each row in the "Directory" table represents a different level in the directory tree, and there is "parent-child" relationship between them. You can't condense several levels into a single row by using "\" or "/" as separators.

If your application needs a version of the Javasoft JRE, I'd definately recommend that you split that into a separate package. You (or your technical architect) should decide on which version of the JRE will become the "standard" within your environment, and try to make all applications adhere to that standard. Any applications that don't adhere become exceptions and should be dealt with accordingly.

And as a totally unrelated and irrelevant footnote, I'd just like to say... Congratulations Liverpool!!!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ