Dear forum dwellers,

After creating an msi package for Matlab 7 (consuming considerable time with its 13.000+ files), the installation fails on computers other than the snapshot host. This is due to the License manager finding hw differences (License manager error -9). Has anyone had any luck in msi-packaging Matlab? Due to policy etc., it would be great if I could get this msi solution to work instead of calling the provided setup program.

Grateful for any tips.

Best regards,
Fredrik
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
As you rightly point out the licensing is locked to the hardware. However, the following links may offer some help :

[link]http://www.mathworks.com/support/tech-notes/1300/1311.html[/link]

Specifically, the following section extract :

Section 3: Checklist for PC Stand-Alone Installation
License Manager errors are not solely a network issue; it can happen on a stand-alone installation as well. Again, there are several things to check when you see this error:

Did you copy the MATLAB files from another machine? This will not work because of the MATLAB licensing scheme. This scheme cannot be changed, even in the license.dat file. The only way around this problem is to delete the MATLAB files on your machine and reinstall following the directions in the section titled Reinstalling the Stand-Alone Version.
Is MATLAB installed locally on your machine? If you are trying to run it from a machine with a mounted drive rather than from the machine it was actually installed on, MATLAB will fail. Again, this is because of the MATLAB licensing scheme, which cannot be changed. The only workaround is to delete the MATLAB files on your machine and reinstall following the directions in the section Reinstalling the Stand-Alone Version.

Check the license.dat file to make sure the serial number at the end of each INCREMENT line (DISK_SERIAL_NUM) matches the serial number of the hard drive of your computer.

In MATLAB version 6.x, the license.dat file can be found in the $MATLAB\bin\win32\directory. Prior to MATLAB version 6.x, this file can be found in the $MATLAB\bin\ directory.

To check this, run dir /p at the MS-DOS prompt at C:\. If the serial number outputed does not match the serial number in your license.dat file, then MATLAB will not run. You will need to reinstall MATLAB.



Also, the following link describes the -9 error :

[link]http://www.mathworks.com/support/solutions/data/1-17RCK.html?solution=1-17RCK[/link]

So you could, I guess, try manually editing the disk serial number in the license.dat file on one of the machines where you are seeing the error. If this works, you would need to find an automated way (Custom Action (?)) to modify this information on each workstation as the package is deployed - not that easy, but possible nonetheless

Regards,

Spartacus
Answered 06/07/2006 by: spartacus
Black Belt

Please log in to comment
0
i never got an MSI at the end of the day. Wot i actually did was to use the SETUP.INI to do the NONINTERACTIVE installation. Edit ur LICENSE.DAT and verify that all lincense servers are correctly listed.

Giz
Answered 06/08/2006 by: gizmolala
Third Degree Blue Belt

Please log in to comment
0
Spartacus & gizmolala: Thank you for your prompt and extensive replies.

As I see it, there are two possible (legal) solutions;
A) Run the setup silently afterwards with the option to only update license.
B) The quick & dirty way: Build your snapshot on a machine with the vol id. of your choice, then make sure clones are using the same vol. id. Since Matlab does not use any other input from hw or user settings to its license checksums, this works.

I went with A at first, succeeding in starting the setup with a rather few number of files. However, I later learned that the setup requires the zip-files to upgrade the license, making this approach rather bloated (furthermore, it is somewhat pointless, since I wanted to escape the setup programme to start with).

Solution B should work pretty well, since the majority of our clients are running a standard clone with identical vol.id:s anyway.

Anyways, just thought I should follow up.

Best regards,
Fredrik
Answered 06/08/2006 by: foo
Yellow Belt

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