Hi there,

I am pacakging an aplication called Paragon software. This is actually a setup driven MSI. If i run the setup it installs fine to c:\ Paragon.(calls msi-setup.log).
Issue here is, if i run the MSI directly with Issetupdriven=1 property it comes up with an error 1406 with a below message.

Product: Paragon Version 5.30.023 -- Error 1406.Could not write value AutoSaveUserSettings to key \SOFTWARE\Paragon Software Systems Plc. System error . Verify that you have sufficient access to that key, or contact your support personnel.

I have not got the exact solution for this. If this works i can change the MSI.
Also how do i incorporate both MSI & exe? In a MST? Please clarify.

Also the heirarchy of the files/folders installed by setup & MSI are different. Now the requirement is to change the install location from C:\ to D:\. I know i can edit this in a MST but there are lot of things to be changes like env variables and so on.

does this make sense? can i do these changes?

Suma
[font="times new roman"]
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
Using ProcMon will show what it is trying to do.

Might be the setup.exe installs few files --- cross check.
Yes, you can embed everything in a MST.
Answered 01/20/2010 by: mekaywe
Brown Belt

Please log in to comment
0
Error 1406.Could not write value AutoSaveUserSettings to key \SOFTWARE\Paragon Software Systems Plc. System error . Verify that you have sufficient access to that key, or contact your support personnel.
Prima Facie, it looks like it is related with previlage issue. Did u try to give permission to the registry? Sometimes the permission thru MSI does not work. Try using SubInACL tool.
Answered 01/20/2010 by: dnmech
Senior Purple Belt

Please log in to comment
0
This is a vendor MSI and i've not modified anything. I"ve not assigned any permissions.
FYI, I am installing it as an admin.
Answered 01/21/2010 by: sumarchana
Orange Senior Belt

Please log in to comment
0
Setup.exe installs few files under c:\Paragon. The same set of files being installed by MSI under c:\PSupport.
But with a log file i can confirm that the setup is calling a vendor MSI. In this case the folde rstructure is being different ans also some of the registries & its values.

Should i repacakge setup and capture changes and include it in MST? (This would have the MSI + exe changes)

Kindly suggest me..
Answered 01/21/2010 by: sumarchana
Orange Senior Belt

Please log in to comment
0
Clearly, since you end up with different INSTALLDIRs, the set-up stub is passing parameters to MSIExec. That should be easy enough to determine from the log. Check out the command line which appears in it and also the various properties which are different.
Answered 01/21/2010 by: VBScab
Red Belt

Please log in to comment
0
Thanks VBScab but i've decided to run the setup silently with setup.iss file. Thanks!!
Answered 01/25/2010 by: sumarchana
Orange Senior Belt

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