Software Deployment

How does the entry in the shortcut table look like in the Shortcut table?
Seems that the file association reference is missing for launching the file in the Target column.

Original shortcut (non advertised):
"LAUNCH1.EXELaunchApplication.exe","PCSuiteStartFolder","NOKIAP~1|Nokia PC
Suite","LaunchApplication.exe","LaunchApplication","","","0","NewShortcut1_6
86D32A3E0BF41B1A4513B59D52466AB.exe","0","1",""

New shortcut (advertised):
"NokiaPCSuite","PCSuiteStartFolder","NOKIAP~1|Nokia PC
Suite","LaunchApplication_SC","[PCSUITE]LaunchApplication.exe","","","","New
Shortcut1_686D32A3E0BF41B1A4513B59D52466AB.exe","0","1",""

As you can see I nicked the old icon straight off, but that isn't the problem (tested without it, still the same).

The entry should look like:
NokiaPCSuite PCSuiteStartFolder NOKIAP~1|Nokia PC Suite LaunchApplication.exe LaunchApplication NewShortcut1_686D32A3E0BF41B1A4513B59D52466AB.exe 0 1

Target column must be set to "LaunchApplication" to make the shortcut advertised as this is the feature holding the "LaunchApplication.exe" component.

The "New shortcut" is a non-advertised shortcut, "Original shortcut" is already an advertised shortcut.

Sorry, I mixed up the entries.

"LAUNCH1.EXELaunchApplication.exe","PCSuiteStartFolder","NOKIAP~1|Nokia PC
Suite","LaunchApplication.exe","LaunchApplication","","","0","NewShortcut1_6
86D32A3E0BF41B1A4513B59D52466AB.exe","0","1",""

This was the modified one. So the target is entirely correct.

The strange thing is that it repairs the missing components from the LaunchApplication feature but is unable to launch the exe-file.
Will do some script that shoots in the keys instead but still, would like to know a solution to it..

How is the added HKCU registry entries connected to the application?
What does the msi log say during the repair?

At the moment the company standard defines that no shortcuts are to be placed on the desktop so I have removed them. Since the Nokia PC Sync and PC Suite main application both give remarks about that they will be minimized to the application tray and that you can reach them from either the apptray or from the shortcut on the desktop the customer wanted the entries to be "preticked" in the "do not display again" dialog so the end-user won't be bothered by it.

The MSI-log gives me no errors at all and that's why I'm confused. It looks like everything is 100% ok, the component is repaired correctly. Going with the VB-script solution putting the entries into HKCU on launching the shortcut instead.

Btw, always nice to see swedes on this forum.. Stockholm-based myself, you? :D

Hi Martin,

Do ya get the same problem not adding the new registry entries?

My self is located in göteborg, what do ya say... the front of Sweden ;)

Hmm wasn't looking close enuf on the image.

You got a ProgID pointing to exefile, seems that this are missing Extension, Verb, ProgID or Class table info in the package or another package is overwriting these registry entries for the exefile

Well, as we say in Stockholm.. If we are the bellybutton of Sweden, that makes Gothenburg.. Well.. Ehrm.. The a-hole.. :D Just kidding.. hehe.

Get the same problem just advertising the shortcut without adding the HKCU keys.

Very very strange, I've never stumbled upon one of these problems before during the 3 years I've been packaging..
Ohwell, it works now anyway.. The lazy way! :D

Did you search for the "exefile" entry in the package?

hehe nice reflection of the bellybutton ;)

No exe-file entry in the package at all..
Very weird, probably some custom action that doing something.

Thanks for the help anyway!

// Martin - stockholm, belly button of sweden - we are full of lint!

I don't recall getting any such problem during my time with NOKIA PC SUITE 6.80.

Well good luck mate!

Hi Martin,
have you got a look at logfile, which is produced during self healing (lies normally in the Users temp folder)?
I mess around quite a lot with self healing and most of the time the problem can be found in there.
Regards, Nick