Software Deployment

G'Day Ogeccut,

Don't know the app, but just had a similar problem, a real tickler (TRIM Context 6) wouldn't open an offline folder correctly when clicked.

Try using technetinternals (previously sysinternals; although the new one sounds like a stomach problem; no offense Mark[;)]) regmon or process monitor when you click on the .sas file. Your probably looking for an extension CLSID in the HKCR. Maybe the .sas entry doesn't have the CLSID information specified? Have a look how another known app registers it's extensions.

Make sure you isolate the PC off the network and stop all unneccessary services (like antivirus) otherwise you'll get lots of data to wade through.

Good luck

Regards
Wayne

Thank you for reply. I Ran regmon. Checked CLSID and its trying to open correct SID. But failing to launch the app.
Still looking.
Any ideas?
Thank you.

There is a table inside an MSI that has to contain the correct extension of the file.

Try looking at the "Extension" table, if there is nothing in there then that is your problem, you will then need to populate the table with the required information.

Thank you for the reply.
I checked Extension table and it’s populated with correct data as far as I can tell.
When I check file association in explorer the .sas files are associated with proper application. However if application is not open it will not launch, but if app is open then by double clicking on .sas files the user can view them.
I think wise is not catching some registry keys on the snapshot. I tried running remon and comparing logs. Cant find anything yet.

Might also be worth checking the Verb table in that case, Ill include an example from the nero application I did:

Extension Table:
Extension: mp3
Component: showtime.exe_COM
ProgID: NeroShowTime.Files.mp3

Verb Table:
Extension: mp3
Verb: play
Sequence: 0
Command: &Play
Argument:"%1"

Hope the information is useful, does sound like your missing a registry key though!

Regards,
Paul

dont use the extension table and use plain registry.

this happens alot when you use advertised extensions and not standard registry as the application cannot interpret it.

therefore if you have extension table stuff setup remove it and add in the registry items which will be a little more difficult to find.