Windows Messenger 8.0
Hi,
Hopefully someone can help. I have gone through all the posts regarding Windows Messenger 8.0 and have taken onboard all the tips on repackaging this application. All the posts have been extremely helpful in getting me to this point but I still cannot get the application to install from an advertised state.
I have
1. extracted the msnmsgs.msi from the Install_Messenger.exe
2. made all my changes in a MST Using Orca.
3. changed the attributes value of the MsgrFeat feature from 24 to 16
4. imported the AdvtExecuteSequence table
5. set the IAGREE property to "Yes"
6. removed "CacheSourceMsi'" from the InstallExecuteSequence table
Note: I am installing the application silently so I do not need to worry about the properties that appear in the UI sequence
Once I make all these changes I can install the MSI\MST to a local machine from a network location using the command line "msiexec /i .....\msnmsgs.msi /t ....\msnmsgs.mst /qb!" and the application will work as expected. The application will also advertise to the local machine using a "msiexec /ju ........\msnmsgs.msi /t ....\msnmsgs.mst /qb!" command line but when I click on the advertised shortcut the installation fails about 3/4 of the way through giving me a "Problem with shortcut - Fatal error during installation" error and the install roles back.
The plan is to deploy this application to a number of users using Active Directory/Group Policy. Unfortunately,
1. I cannot advertise the application to users accounts as it behaves in the same way as it does when I advertise it using a command line.
2. I cannot publish the application to users accounts as although the application will appear in the Add New Programs section of the control panel it fail about 3/4 of the way through the install giving a "Windows Live Messenger Setup Failed" error
3. I cannot set the application to install as the user logs on as again this fails
Has anyone got any ideas on this? Has anyone taken a different approach to deploying this application?
Thanks in advance.
AD.
Hopefully someone can help. I have gone through all the posts regarding Windows Messenger 8.0 and have taken onboard all the tips on repackaging this application. All the posts have been extremely helpful in getting me to this point but I still cannot get the application to install from an advertised state.
I have
1. extracted the msnmsgs.msi from the Install_Messenger.exe
2. made all my changes in a MST Using Orca.
3. changed the attributes value of the MsgrFeat feature from 24 to 16
4. imported the AdvtExecuteSequence table
5. set the IAGREE property to "Yes"
6. removed "CacheSourceMsi'" from the InstallExecuteSequence table
Note: I am installing the application silently so I do not need to worry about the properties that appear in the UI sequence
Once I make all these changes I can install the MSI\MST to a local machine from a network location using the command line "msiexec /i .....\msnmsgs.msi /t ....\msnmsgs.mst /qb!" and the application will work as expected. The application will also advertise to the local machine using a "msiexec /ju ........\msnmsgs.msi /t ....\msnmsgs.mst /qb!" command line but when I click on the advertised shortcut the installation fails about 3/4 of the way through giving me a "Problem with shortcut - Fatal error during installation" error and the install roles back.
The plan is to deploy this application to a number of users using Active Directory/Group Policy. Unfortunately,
1. I cannot advertise the application to users accounts as it behaves in the same way as it does when I advertise it using a command line.
2. I cannot publish the application to users accounts as although the application will appear in the Add New Programs section of the control panel it fail about 3/4 of the way through the install giving a "Windows Live Messenger Setup Failed" error
3. I cannot set the application to install as the user logs on as again this fails
Has anyone got any ideas on this? Has anyone taken a different approach to deploying this application?
Thanks in advance.
AD.
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
spartacus
17 years ago
I think you'll need to rerun the advertised installation (which generates the fatal error) but this time with verbose logging enabled (see this FAQ)
Once the failure has occurred again, you can look through the verbose log file and locate the error. In particular, inspect the lines immediately leading up to the error for clues.
If you're still stuck, you could post an extract from the log (preferably not the whole file !) here for further assistance.
Also, do you see any additional information in the Application Event log after the failure has occurred which may help the troubleshooting ?
Regards,
Spartacus
Once the failure has occurred again, you can look through the verbose log file and locate the error. In particular, inspect the lines immediately leading up to the error for clues.
If you're still stuck, you could post an extract from the log (preferably not the whole file !) here for further assistance.
Also, do you see any additional information in the Application Event log after the failure has occurred which may help the troubleshooting ?
Regards,
Spartacus
Posted by:
AD
17 years ago
Thanks Spartacus,
I enabled the verbose logging as you suggested and on inspecting the log file that was produced I found this:
WriteBinarySID(): Cannot open target key (HKCR\AppID\{F07EFF1B-88F7-4076-ADAC-185F393785E9}).
MSI (s) (AC:BC) [15:41:00:097]: User policy value 'DisableRollback' is 0
MSI (s) (AC:BC) [15:41:00:097]: Machine policy value 'DisableRollback' is 0
Action ended 15:41:00: InstallFinalize. Return value 3.
I simply manually added the HKCR\AppID\{F07EFF1B-88F7-4076-ADAC-185F393785E9} registry key to the test machine on which the advertised install was failing and it worked!! I have tested it on a few test machines since and this seems to fix the issue. I guess the next step is to add it to my MST and see if that works.
Thanks again for your help.
AD.
I enabled the verbose logging as you suggested and on inspecting the log file that was produced I found this:
WriteBinarySID(): Cannot open target key (HKCR\AppID\{F07EFF1B-88F7-4076-ADAC-185F393785E9}).
MSI (s) (AC:BC) [15:41:00:097]: User policy value 'DisableRollback' is 0
MSI (s) (AC:BC) [15:41:00:097]: Machine policy value 'DisableRollback' is 0
Action ended 15:41:00: InstallFinalize. Return value 3.
I simply manually added the HKCR\AppID\{F07EFF1B-88F7-4076-ADAC-185F393785E9} registry key to the test machine on which the advertised install was failing and it worked!! I have tested it on a few test machines since and this seems to fix the issue. I guess the next step is to add it to my MST and see if that works.
Thanks again for your help.
AD.
Posted by:
nheim
17 years ago
Hi AD,
try to add to add the following lines to the AdvtExecuteSequence table :
SetUSNAccessSIDLegacy 1601
SetUSNAccessSIDSecure 1601
SetUSNLaunchSIDLegacy 1601
SetUSNLaunchSIDSecure 1601
Use Orca, go to the InstallExecuteSequence table, select this rows in there and press Ctrl+Shift+C. Then change to the AdvtExecuteSequence table and press Ctrl+Shift+V.
Let us know, if this gives a different behaviour.
Regards, Nick
try to add to add the following lines to the AdvtExecuteSequence table :
SetUSNAccessSIDLegacy 1601
SetUSNAccessSIDSecure 1601
SetUSNLaunchSIDLegacy 1601
SetUSNLaunchSIDSecure 1601
Use Orca, go to the InstallExecuteSequence table, select this rows in there and press Ctrl+Shift+C. Then change to the AdvtExecuteSequence table and press Ctrl+Shift+V.
Let us know, if this gives a different behaviour.
Regards, Nick
Posted by:
AD
17 years ago
Hi Nick,
Thanks for your post. That was actually the first thing I tried yesterday afternoon as I am convinced that there must be a cleaner/nicer way around this issue than adding HKCR\AppID\{F07EFF1B-88F7-4076-ADAC-185F393785E9} to my MST. Unfortunately it did not work. The advertised install behaves in exactly the same way as my original post. I got a little side tracked this morning but I hope to get back to the issue this afternoon. I will post the solution should I find an alternative one.
Cheers,
AD.
Thanks for your post. That was actually the first thing I tried yesterday afternoon as I am convinced that there must be a cleaner/nicer way around this issue than adding HKCR\AppID\{F07EFF1B-88F7-4076-ADAC-185F393785E9} to my MST. Unfortunately it did not work. The advertised install behaves in exactly the same way as my original post. I got a little side tracked this morning but I hope to get back to the issue this afternoon. I will post the solution should I find an alternative one.
Cheers,
AD.
Posted by:
nheim
17 years ago
Hi AD,
do you log the installs? If not, please do so.
Open the log and search for the names of the Custom Actions. Check, if they are really executed or if the condition is preventing it.
Regards, Nick
do you log the installs? If not, please do so.
Open the log and search for the names of the Custom Actions. Check, if they are really executed or if the condition is preventing it.
Regards, Nick
Posted by:
AD
17 years ago
Just in case anyone has been following this thread.........this issue only occurs on XP SP2. For whatever reason, it does not occur on XP SP1 at all.[&:]
Posted by:
bwcook0
17 years ago
i have the same problem. I have a a log available but it says i don't have permisison to attach files. Here's the relevant portion (i think)
Thanks, BC
Thanks, BC
SI (s) (EC:50) [16:55:15:845]: Executing op: RegAddValue(Name={671D06C8-9BDE-9194-C01F-C8B3B9A1E18E},Value=C:\WINDOWS\winsxs\Policies\x86_policy.8.0.Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_x-ww_77c24773\[~]{671D06C8-9BDE-9194-C01F-C8B3B9A1E18E},)
MSI (s) (EC:50) [16:55:15:860]: Executing op: RegAddValue(Name={671C201F-9C28-9195-C01F-C8B3B9A1E18E},Value=C:\WINDOWS\winsxs\Policies\x86_policy.8.0.Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_x-ww_77c24773\[~]{671C201F-9C28-9195-C01F-C8B3B9A1E18E},)
MSI (s) (EC:50) [16:55:15:860]: Executing op: ActionStart(Name=WriteUSNLaunchSID,,)
MSI (s) (EC:50) [16:55:15:860]: Executing op: CustomActionSchedule(Action=WriteUSNLaunchSID,ActionType=3073,Source=BinaryData,Target=WriteBinarySID,CustomActionData=HKCR\AppID\{F07EFF1B-88F7-4076-ADAC-185F393785E9}\LaunchPermission|O:LSG:LSD:(A;;CCDCSW;;;AU))
MSI (s) (EC:A0) [16:55:15:860]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI6F.tmp, Entrypoint: WriteBinarySID
WriteBinarySID(): Cannot open target key (HKCR\AppID\{F07EFF1B-88F7-4076-ADAC-185F393785E9}).
MSI (s) (EC:50) [16:55:15:876]: User policy value 'DisableRollback' is 0
MSI (s) (EC:50) [16:55:15:876]: Machine policy value 'DisableRollback' is 0
Action ended 16:55:15: InstallFinalize. Return value 3.
MSI (s) (EC:50) [16:55:15:876]: Executing op: Header(Signature=1397708873,Version=301,Timestamp=898533094,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (EC:50) [16:55:15:876]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (ECs
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.