self healing problem:
My application name is MSDE 8.00.761. This is an exe, If u install this it will extract one msi, I have created mst for this, In the msi it is having command line shortcut, I have made this as advertised.
After installing my mst I launched the shortcut in admin mode and standard user mode.It has self healed in admin mode and launched the shortcut.But in standard user mode while self healing it is throwing one error ie,. Shortcut Error(Fatal Error).
I have given full permission to the user in folders and registreis.But still it is showing the same error.
Actually all the files and registries are created by merge modules. All the shortcuts and services are created through custom actions.

Can any one help on this.
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
I'm guessing but I'll bet you're installing per-user when installing as a vanilla user?

IIRC,MSDE contains at least one of the Visual C runtime merge modules which resolutely refuse to install in per-user mode. A verbose log will confirm that for you.
Answered 10/24/2008 by: VBScab
Red Belt

Please log in to comment
0
I have installed the application in Per Machine mode, But it is throwing the same error
Answered 10/24/2008 by: sanhivi
Second Degree Green Belt

Please log in to comment
0
OK, first, re-run the install with a verbose log. Then look at the Event Viewer and find the GUID of the component throwing the error. Armed with this information you should be able to track down the cause.
Answered 10/24/2008 by: VBScab
Red Belt

Please log in to comment
0
I have launched the shortcut and saw the eventviewer, In that it is showing "HKCU\SOFTWARE\Microsoft\Microsoft SQLServer\80\Tools\Service Manager" doesn't exist.
Now what should I do?

Here I want to give deep explanation of my application. Vendor MSI contains the non advertised shortcut in the component named "SvcMngrShortcut.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616". But its target dir is pointing to the component named "ServiceManager.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616". Because of this I was not able to make the shortcut advertised in that component .So I moved the shortcut to the "ServiceManager.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616" and made this one as advertised.
"SvcMngrShortcut.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616" component is having one HKCU entry which I mentioned in the begining.
Answered 10/27/2008 by: sanhivi
Second Degree Green Belt

Please log in to comment
0
Firstly, I would strongly advise against moving vendor's advertised shortcuts around.
Secondly, are you sure you are installing per-machine? What value does the log file you created have for the ALLUSERS property? What features did you select for installation?
Answered 10/27/2008 by: VBScab
Red Belt

Please log in to comment
0
Yes, We shouldn'g change the vendor msi, But according to Our project standards we need to change, that is the reason I changed the shorcut path.
I have taken a log for installation , In this it is showing ALLUSERS=1.
My application is Per machine installation.
It is having only one feature ie,. SqlRun.
Answered 10/27/2008 by: sanhivi
Second Degree Green Belt

Please log in to comment
0
I recalled that I created a bunch of MSTs for MSDE 2000 so I was able to open them up and take a look.

The shortcut is actually contained within the merge module with the signature 'SQLSVR.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616' which, I suspect, is the one listed as 'SQLSRV'. I say "I suspect" because my WPS implementation takes W A Y too long to show me lists of MMs and I can't be bothered to wait. so, because the s/c "lives" in that MM, I don't believe you can change that shortcut to advertised without extracting the MM in its entirety, re-working it and then putting it back. In doing so, you open yourself up to all kinds of support issues.
Answered 10/27/2008 by: VBScab
Red Belt

Please log in to comment
0
Unfortunately vendor supplied .msi files are very poor and will never follow any of the usual rules or best practices associated with application packaging.

You will probably find the thing was created as an after thought by a junior developer and is just a bunch of .dll driven custom actions that hardly even uses the windows installer.

My advice would be to forget about advertisement and simply create a transform that applies your company’s basic standards, properties and summery information.

You will be hard pressed getting a vendor supplied .msi to do anything a correctly authored .msi should do.
Answered 11/03/2008 by: DLL_HELL
Senior Yellow Belt

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