Hey there, I'm pulling my hair out trying to get JMP 7.0.1 from SAS Institutes to build into an MSI correctly for deployment via group policy. We have built JMP 6.x.x just fine in the past but it seems that the new requirement wizard that you have to run prior to installing 7.0.1 is causing problems.

Before I go into the problems though, has anyone else tackled this guy and been successfull yet?

Thanks,

Brian
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
Find out what the requirements wizard does, and any prerequisites you'll need to install JMP. Divide and conquer.
I'd defiinitely get support on this from SAS and not try to wing it. It's a pretty big expensive product, isn't it?
Answered 10/16/2007 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
I wouldn't call it big, but I imagine it is expensive. I don't pay the bills, just deploy the software if you know what I mean. Anyway, what the requirement wizard seems to be doing is installing Microsoft Runtime Components 7.1 and a SAS specific version of Java called "SAS Private Java Runtime Environment 1.4.2_09. I haven't tried packaging this up seperately yet though I may give that a shot.

I did package up JMP w/o including the requirements and it runs fine on a manual install of the resulting msi, though I have no idea what functionality may be missing doing it that way.

I've contacted JMP support and pretty much got a bit "Well, we don't support that, good luck!" So I doubt they will be much use. However, they did say that I could manually install the SAS Java and then create a package for JMP on Windows XP systems.
Answered 10/17/2007 by: rignes
Senior Yellow Belt

Please log in to comment
0
Vendors like that drive me nuts and, I'm afraid, I tend to deal with them pretty ruthlessly.

Send that guy an email and have him reply to that effect. Then forward his reply along with a scan of the product invoice to the MD/CEO with a carefully-worded promise of internet infamy for the crappy support people can expect for an $x,000 product. Remind him about WOMM - Word Of Mouth Marketing, i.e. the old adage that "One satisfied customer tells one other person, but a dissatisfied customer tells ten." That always goes down well. Sit by the phone. They will call. If they don't, then let loose the dogs of war and follow through on your promise. That won't help you solve your problem but it might just mean people avoid dealing with deadbeats like this mob.
Answered 10/17/2007 by: VBScab
Red Belt

Please log in to comment
0
What version of SAS are you packaging?
And what components of SAS?
I took the snapshot after requirement wizard ran and REBOOTED. I don’t think its a good practice to install multiple applications in one msi. However i had a problem with file association. SAS would not launch when users double clicked on msi, but when it was open everything is fine. Called SAS adn didn’t get anywhere.
Answered 10/17/2007 by: ogeccut
Black Belt

Please log in to comment
0
Hey there. I'm trying to package up SAS JMP 7.0.1. I'm doing a default installation of JMP so it would be whatever components are selected by default.

Are you saying you got it built and deployed correctly? If so can you give a brief summary of how you did it? I'd really appreciate it.

Thanks,

Brian
Answered 10/17/2007 by: rignes
Senior Yellow Belt

Please log in to comment
0
I am in the same boat as well, and pretty much get the same useless answer from JMP as well regarding the support..

I did not convert to an MSI install, but automated it this way:

echo - Installing SAS Java Runtime
start /wait /d"%~dp0sasjre" jresetup -silent
echo - Installing Visual C++ 7.0 Pre-Reqs
start /wait /d"%~dp0vcredist" %~dp0vcredist\setup
echo - Installing Visual C++ 7.1 Pre-Reqs
start /wait /d"%~dp0VCREDST71" %~dp0"VCREDST71\setup
echo.
echo Installing JMP 7
start /wait /d"%~dp0JMP" %~dp0JMP\setup
echo - Applying JMP 7.01 Patch Release
start /wait /d"%~dp07.01" %~dp07.01\setup

Interesting enough when I do it this way, the uninstall doesn't work.. I have an open case with SAS to try and fix but I am not optimistic.. It seems to have something to do with the fact that I recorded the setup (setup.iss) and use that to deploy.. If I don't do the -s when installing and do the steps manually it works fine..

Any other suggestions?
Answered 10/24/2007 by: jpkishere
Yellow Belt

Please log in to comment
0
I've had a suggestions that perhaps when the msi is installed via AD that there may be a permission issue or something similar since the package gets installed via the computer account.

The reason this makes sense is that when the MSI Icreate is installed directly by running it as a logged in user it seems to install fine, yet when it's done through AD the user is prompted for the location of their preferences file on the first run.

I'm not sure how to deal with this, does anyone have a suggestion on a method or tool I could use to see what is going on under the hood at that moment?

Thanks,

Brian
Answered 10/30/2007 by: rignes
Senior Yellow Belt

Please log in to comment
0
[left]Problem: [/left][left]>>While installation, one of the pre-requisite "jre-1_5_0_15-windows-i586-p.exe" its trying to connect to internet to download extra files. It asks proxy ID and password as we are behind Proxy.[/left][left]>> If we create an .iss file it will not capture a dialogue box i.e. for providing the proxy ID and password.[/left][left]>> Is there any way we can suppress the Proxy connection? I have checked the SUN site and it has silent switch for installing JRE silently but it need to be integrated into the software itself.[/left][left]>> Even if all the pre-requisite are installed on my machine then also the installation kicks of the pre-requisite installation.[/left][left]>> Is there any way we can remove this pre-requisites installation from JMP 8 source. Instead we will manually install the pre-requisite and that may solve our problem.[/left]
Answered 08/05/2009 by: sanjaymgr
Yellow Belt

Please log in to comment
0
It sounds like it's trying to use the 'Lite' installer but, in any event, you should never capture apps which use a JRE without first having installed whatever flavour of JRE it requires.

Download the full 1.5.0_15 installer, install it first, snapshot your VM/VPC/VirtualBox (to save the pain of doing that again), THEN start your capture. The legacy installer you're capturing will see the JRE and skip installing it.

The same goes for the Visual C++ runtimes.
Answered 08/05/2009 by: VBScab
Red Belt

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