All,
As anyone successfully snapshotted Sage Line 50 (2009)?

The application has an MSI which unfortunatly is nothing more than a box containing files and custom actions, even to the point whereby the entire Dialog table is empty.

Personally I dont see the point of using MSI if you dont actually use it and the engineers in Sage should be shot for the work done.

Regardless of that, the end MSI after a snapshot doesnt work so I was wondering if anyone had touched this product? The MSI does install, everything looks good, but it wont launch so im assuming that there is some protection on it to prevent it from being re-packaged.

P
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
Hi, Paul.

What possessed you to capture an MSI? And once you had, you could see exactly what it's going to do with your build so, provided it's well-behaved, why not use it as-is?

Baffled...
Answered 06/19/2009 by: VBScab
Red Belt

Please log in to comment
0
you to capture an MSI

have gapcapture anf find if anything is missing
Answered 06/19/2009 by: mekaywe
Brown Belt

Please log in to comment
0
Huh?
Answered 06/19/2009 by: VBScab
Red Belt

Please log in to comment
0
VBScab,
I am well aware that we shouldnt capture MSI's however when said MSI is nothing more than a container for files, doesnt have advertised shortcuts or shortcuts for that matter, doesnt have proper directory tables, doesnt use COM tables, uses custom actions to run exe's and doesnt have any dialogs to populate as they are handled by their custom setup im sort of stuck, oh and doesnt run without the setup.exe :)

Basically the setup.exe does everything and the MSI is useless and should be nothing more than files run and used by the setup rather than putting them into an MSI.

mekaywe
Your comment doesnt make sense :)

P
Answered 06/19/2009 by: Inabus
Second Degree Green Belt

Please log in to comment
0
:)

What am trying to say is the captured MSI may be missing something what exactly the setup.exe if delivering, if we can find those entries add them to captured MSI and give a try
Answered 06/19/2009 by: mekaywe
Brown Belt

Please log in to comment
0
I should point out that I have taken the virgin snapshotted MSI, without cleaning, and attempted to use that and it doesnt work. Yes it could be something that Installshield has missed and that is the avenue im heading down now, but wanted to know if anyone had succesfully packaged this to try and identify if its a problem with my MSI or a vendor introduced machine specific style install.

P
Answered 06/19/2009 by: Inabus
Second Degree Green Belt

Please log in to comment
0
I tried to capture VendorMSI of some other application and had same type of problem.
Picture Taker is the tool which saved me at the point of time
Answered 06/19/2009 by: mekaywe
Brown Belt

Please log in to comment
0
An update on this, I have a working MSI now which fully works when deploying as an admin however when deploying as a user I have issues where-by the app says that the password is incorrect for the default account the install set's up. If I log off as a user, on as an admin and execute the app it works with that username and password and if I then log back on as a test user the app will function 100% correctly so this problem only manifests itself when I install and launch the app as a user without running it at all as an admin!

Clearly something is being registered, updated, customized or tweaked but opening up the HKLM and file system for full control for the user doesnt fix the issue. Anyone run across something like this for this app before?

P
Answered 07/02/2009 by: Inabus
Second Degree Green Belt

Please log in to comment
0
I take it by everyones silence in this post that noone else has attempted to snapshot this package? :0

P
Answered 07/08/2009 by: Inabus
Second Degree Green Belt

Please log in to comment
0
I have not had any dealings with this application before

but how did you capture the installation

did you install the application first then extract the msi

then go back to your clean snapshot install the msi first then the setup.exe and test it as a user and see if it works


is your application creating files in appdata or commonappdata folders


with the way things are now install your app with an admin account

run installrite and launch your application to see what files / regkeys are added or deleted

you can also run procmon, filemon and regmon to see any access denied permissions
Answered 07/08/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
Dont worry panic over problem resolved :)

The link that set me down the right path is:

http://www.sageforum.co.uk/viewtopic.php?t=4420&highlight=crypto

Creating and opening up the permissions on the MachineKeys folder fixed the issue.

P
Answered 07/08/2009 by: Inabus
Second Degree Green Belt

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