I am trying to wrap the SAS 9.1.3 installer in an MSI, as the perceived wisdom is that it is a PITA to re-package.

I have, after many attempts, got command lines for silent install and uninstall and they work flawlessly on my packaging box (VM). However, when I log in as a user with appropriate group membership, nothing gets installed, although the log would suggest that the EXE has run:

MSI (s) (08:B8) [16:05:48:677]: Doing action: InstallSAS
Action ended 16:05:48: InstallFinalize. Return value 1.
Action start 16:05:48: InstallSAS.
MSI (s) (08:B8) [16:06:19:068]: Doing action: RemoveExistingProducts
Action ended 16:06:19: InstallSAS. Return value 1.

I've tried everything I can think of: calling the Setup.EXE directly from a CA; setting the EXE as a property and calling that and finally, simply creating a command file and calling that. In each case the MSI (which only exists to run the SAS installer) and the command file live on a network share.

My question is, does the GP install have access to UNC resources? Surely it must do if the source media is there? If so, then, why does it not run my command file/EXE/whatever? PLEASE don't tell me I've got to copy this junk locally and run it from there - it's 840Mb-worth. Of course, if anyone *has* a SAS 9.1.3 MSI already, I'm begging...
0 Comments   [ + ] Show 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.


i package sas about 6 months ago or more, i had to snap it and it was pretty straight forward after that.
Answered 07/25/2007 by: linstead
Blue Belt

Please log in to comment
Yes, I'm snapping right now...
Answered 07/25/2007 by: VBScab
Red Belt

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