I have followed all the action from
http://itninja.com/link/appdeploy->-package-knowledgebase->-msn-messenger

But the installer is running at the half, and then roll back itself without a pop up error.
I have checked the event viewer. It's only saying fail installation without error code.

What should i do?
Thanks.
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
Log the installation to get some more feedback regarding the error.
How are you installing/deploying the application?
Answered 11/06/2006 by: AngelD
Red Belt

Please log in to comment
0
Here is my step.

1. Copy the files (msnmsgs.msi....etc) from "temp" directory
2. Edit the msi by Orca, change the MsgrFeat attributes value from 24 to 16
3. Add "AdvtExecuteSequence" table from sequence.msi (from Windows installer SDK)
4. open Property table and Modify IAGREE to "Yes", Add ADDBHO = "No-ADDBHO", ADDLINKS = "No-AddLinks", SETHOMEPAGE = "No-SetMyHomePage"

Then i run it as a Dos batch file
msiexec /i \\Server\MsnMsgs.msi /qb-

I can see the process is going but roll back at the middle.
Answered 11/06/2006 by: mkali
Orange Belt

Please log in to comment
0
The error from event viewer


Event Type: Information
Event Source: MsiInstaller
Event Category: None
Event ID: 11708
Date: 11/7/2006
Time: 9:41:12 AM
User: TW1SR45BX\Administrator
Computer: TW1SR45BX
Description:
Product: Windows Live Messenger -- Installation failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 46 43 45 35 30 44 42 {FCE50DB
0008: 38 2d 43 36 31 30 2d 34 8-C610-4
0010: 43 34 32 2d 42 45 35 43 C42-BE5C
0018: 2d 31 39 33 46 34 36 43 -193F46C
0020: 36 46 38 31 32 7d 6F812}
Answered 11/06/2006 by: mkali
Orange Belt

Please log in to comment
0
Any other way to install successfully? Any suggestion?
Thanks.
Answered 11/08/2006 by: mkali
Orange Belt

Please log in to comment
0
Hi mkali,
call the setup with the following command: msiexec /i \\Server\MsnMsgs.msi /lvx* MsnMsgs.log /qb-
After that, open 'MsnMsgs.log', scroll to the end and do a 'page up' until where the lines, which begin with 'Property(S):', start.
From there going further up, you see lines with 'rollback' in it, go past them to find the lines with the error and return code of '3'.
Copy about 10 lines around the error to your next answer, so we can get a look at what's wrong.
Regards, Nick
Answered 11/09/2006 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
I had no issues with this. Once I'd got the MsnMsgs.msi file, I simply edited the Property table to reflect the command line options suggested by realgujju in the package post.
Answered 11/09/2006 by: dgdavis
Orange Belt

Please log in to comment
0
Is this?

MSI (s) (F0:64) [10:24:04:011]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI173.tmp, Entrypoint: RollbackInstall
DIFXAPP: Rollback failed with error 0x2
MSI (s) (F0:48) [10:24:05:570]: Error in rollback skipped. Return: 5
DEBUG: Error 2911: Could not remove the folder C:\Program Files\MSN Messenger\Device Manager\.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2911. The arguments are: C:\Program Files\MSN Messenger\Device Manager\, ,
Answered 11/09/2006 by: mkali
Orange Belt

Please log in to comment
0
MSI (s) (F0:48) [10:24:05:742]: Note: 1: 1708
MSI (s) (F0:48) [10:24:05:758]: Product: Windows Live Messenger -- Installation failed.

MSI (s) (F0:48) [10:24:05:758]: Cleaning up uninstalled install packages, if any exist
MSI (s) (F0:48) [10:24:05:758]: MainEngineThread is returning 1603
MSI (s) (F0:00) [10:24:05:867]: Destroying RemoteAPI object.
MSI (s) (F0:6C) [10:24:05:867]: Custom Action Manager thread ending.
=== Logging stopped: 11/10/2006 10:24:05 ===
MSI (c) (B0:8C) [10:24:05:882]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (B0:8C) [10:24:05:882]: MainEngineThread is returning 1603
=== Verbose logging stopped: 11/10/2006 10:24:05 ===
Answered 11/09/2006 by: mkali
Orange Belt

Please log in to comment
0
Hi mkali,
good start. But scroll further up, there will be more errors. Look for an action with error and return code 3.
You have to find the initial error, which caused all the mess.
Regards, Nick
Answered 11/10/2006 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Thanks.

But, actucally i cannot find which sentence contain Error & 3.
I copy all sentences with "error" to here.



MSI (s) (A8:A4) [11:47:49:842]: PROPERTY CHANGE: Adding LocalAppDataErrorReporting.D0DF3458_A845_11D3_8D0A_0050046416B9 property. Its value is 'C:\Documents and Settings\Administrator\Local Settings\Application Data\PCHEALTH\ERRORREP\'.
MSI (s) (A8:A4) [11:47:49:842]: PROPERTY CHANGE: Adding WatsonUQSignoffFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 property. Its value is 'C:\Documents and Settings\Administrator\Local Settings\Application Data\PCHEALTH\ERRORREP\QSIGNOFF\'.
MSI (s) (A8:A4) [11:47:49:842]: PROPERTY CHANGE: Adding WatsonUQRegularFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 property. Its value is 'C:\Documents and Settings\Administrator\Local Settings\Application Data\PCHEALTH\ERRORREP\QREGULAR\'.
MSI (s) (A8:A4) [11:47:49:842]: PROPERTY CHANGE: Adding WatsonUQHeadlessFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 property. Its value is 'C:\Documents and Settings\Administrator\Local Settings\Application Data\PCHEALTH\ERRORREP\QHEADLES\'.
MSI (s) (A8:A4) [11:47:49:842]: PROPERTY CHANGE: Adding WindowsErrorReporting.D0DF3458_A845_11D3_8D0A_0050046416B9 property. Its value is 'C:\WINDOWS\PCHEALTH\ERRORREP\'.
MSI (s) (A8:A4) [11:47:49:842]: PROPERTY CHANGE: Adding WatsonAQSignoffFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 property. Its value is 'C:\WINDOWS\PCHEALTH\ERRORREP\QSIGNOFF\'.
MSI (s) (A8:A4) [11:47:49:842]: PROPERTY CHANGE: Adding WatsonAQHeadlessFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 property. Its value is 'C:\WINDOWS\PCHEALTH\ERRORREP\QHEADLES\'.
MSI (s) (A8:A4) [11:47:49:874]: Dir (target): Key: LocalAppDataErrorReporting.D0DF3458_A845_11D3_8D0A_0050046416B9 , Object: C:\Documents and Settings\Administrator\Local Settings\Application Data\PCHEALTH\ERRORREP\
MSI (s) (A8:A4) [11:47:49:874]: Dir (target): Key: WatsonUQSignoffFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 , Object: C:\Documents and Settings\Administrator\Local Settings\Application Data\PCHEALTH\ERRORREP\QSIGNOFF\
MSI (s) (A8:A4) [11:47:49:874]: Dir (target): Key: WatsonUQRegularFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 , Object: C:\Documents and Settings\Administrator\Local Settings\Application Data\PCHEALTH\ERRORREP\QREGULAR\
MSI (s) (A8:A4) [11:47:49:874]: Dir (target): Key: WatsonUQHeadlessFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 , Object: C:\Documents and Settings\Administrator\Local Settings\Application Data\PCHEALTH\ERRORREP\QHEADLES\
MSI (s) (A8:A4) [11:47:49:874]: Dir (target): Key: WindowsErrorReporting.D0DF3458_A845_11D3_8D0A_0050046416B9 , Object: C:\WINDOWS\PCHEALTH\ERRORREP\
MSI (s) (A8:A4) [11:47:49:874]: Dir (target): Key: WatsonAQSignoffFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 , Object: C:\WINDOWS\PCHEALTH\ERRORREP\QSIGNOFF\
MSI (s) (A8:A4) [11:47:49:874]: Dir (target): Key: WatsonAQHeadlessFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 , Object: C:\WINDOWS\PCHEALTH\ERRORREP\QHEADLES\
MSI (s) (A8:A4) [11:47:49:967]: Component: MsgrCoreErrorResponse; Installed: Absent; Request: Local; Action: Local
MSI (s) (A8:A4) [11:48:06:054]: Dir (source): Key: LocalAppDataErrorReporting.D0DF3458_A845_11D3_8D0A_0050046416B9 , Object: \\server\APSOFTWARE\Microsoft\WLM\8.0\ , LongSubPath: PFiles\MSN Messenger\Application Data\PCHEALTH\ERRORREP\ , ShortSubPath: PFiles\MsnMsgr\APPDATA\PCHEALTH\ERRORREP\
MSI (s) (A8:A4) [11:48:06:054]: Dir (source): Key: WatsonUQSignoffFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 , Object: \\server\APSOFTWARE\Microsoft\WLM\8.0\ , LongSubPath: PFiles\MSN Messenger\Application Data\PCHEALTH\ERRORREP\QSIGNOFF\ , ShortSubPath: PFiles\MsnMsgr\APPDATA\PCHEALTH\ERRORREP\QSIGNOFF\
MSI (s) (A8:A4) [11:48:06:054]: Dir (source): Key: WatsonUQRegularFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 , Object: \\server\APSOFTWARE\Microsoft\WLM\8.0\ , LongSubPath: PFiles\MSN Messenger\Application Data\PCHEALTH\ERRORREP\QREGULAR\ , ShortSubPath: PFiles\MsnMsgr\APPDATA\PCHEALTH\ERRORREP\QREGULAR\
MSI (s) (A8:A4) [11:48:06:054]: Dir (source): Key: WatsonUQHeadlessFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 , Object: \\server\APSOFTWARE\Microsoft\WLM\8.0\ , LongSubPath: PFiles\MSN Messenger\Application Data\PCHEALTH\ERRORREP\QHEADLES\ , ShortSubPath: PFiles\MsnMsgr\APPDATA\PCHEALTH\ERRORREP\QHEADLES\
MSI (s) (A8:A4) [11:48:06:054]: Dir (source): Key: WindowsErrorReporting.D0DF3458_A845_11D3_8D0A_0050046416B9 , Object: \\server\APSOFTWARE\Microsoft\WLM\8.0\ , LongSubPath: PFiles\MSN Messenger\WINDOWS\PCHEALTH\ERRORREP\ , ShortSubPath: PFiles\MsnMsgr\WINDOWS\PCHEALTH\ERRORREP\
MSI (s) (A8:A4) [11:48:06:054]: Dir (source): Key: WatsonAQSignoffFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 , Object: \\server\APSOFTWARE\Microsoft\WLM\8.0\ , LongSubPath: PFiles\MSN Messenger\WINDOWS\PCHEALTH\ERRORREP\QSIGNOFF\ , ShortSubPath: PFiles\MsnMsgr\WINDOWS\PCHEALTH\ERRORREP\QSIGNOFF\
MSI (s) (A8:A4) [11:48:06:054]: Dir (source): Key: WatsonAQHeadlessFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 , Object: \\server\APSOFTWARE\Microsoft\WLM\8.0\ , LongSubPath: PFiles\MSN Messenger\WINDOWS\PCHEALTH\ERRORREP\QHEADLES\ , ShortSubPath: PFiles\MsnMsgr\WINDOWS\PCHEALTH\ERRORREP\QHEADLES\
MSI (s) (A8:A4) [11:48:06:383]: The file represented by File table key 'ErrorResponse' has no eligible binary patches
MSI (s) (A8:A4) [11:48:07:228]: Executing op: ComponentRegister(ComponentId={FCD4CBCF-47FA-4E30-BE7D-DA19CA77891F},KeyPath=C:\Program Files\MSN Messenger\ErrorResponse.xml,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
MSI (s) (A8:A4) [11:48:07:964]: Executing op: FileCopy(SourceName=errorr~1.xml|ErrorResponse.xml,SourceCabKey=ErrorResponse,DestName=ErrorResponse.xml,Attributes=0,FileSize=1834,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPart1=1256987230,HashPart2=-90548051,HashPart3=431321206,HashPart4=2074562796,,)
MSI (s) (A8:A4) [11:48:07:964]: File: C:\Program Files\MSN Messenger\ErrorResponse.xml; To be installed; Won't patch; No existing file
MSI (s) (A8:A4) [11:48:07:964]: Source for file 'ErrorResponse' is compressed
MSI (s) (A8:A4) [11:48:08:089]: Note: 1: 2318 2: C:\Program Files\MSN Messenger\ErrorResponse.xml
MSI (s) (A8:A4) [11:48:14:771]: Executing op: ServiceInstall(Name=usnsvc,DisplayName=Messenger Sharing USN Journal Reader service,ImagePath="C:\Program Files\MSN Messenger\usnsvc.dll",ServiceType=16,StartType=3,ErrorControl=1,,Dependencies=rpcss[~]eventlog[~][~],,,Password=**********,Description=Service installed by Messenger to enable sharing scenarios)
DIFXAPP: Rollback failed with error 0x2
DEBUG: Error 2911: Could not remove the folder C:\Program Files\MSN Messenger\Device Manager\.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2911. The arguments are: C:\Program Files\MSN Messenger\Device Manager\, ,
MSI (s) (A8:A4) [11:48:27:994]: Executing op: FileRemove(,FileName=C:\Program Files\MSN Messenger\ErrorResponse.xml,,)
MSI (s) (A8:A4) [11:48:28:651]: Error in rollback skipped. Return: 5
Property(S): ErrorDialog = ErrorDialog
Property(S): WindowsErrorReporting.D0DF3458_A845_11D3_8D0A_0050046416B9 = C:\WINDOWS\PCHEALTH\ERRORREP\
Property(S): WatsonAQHeadlessFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 = C:\WINDOWS\PCHEALTH\ERRORREP\QHEADLES\
Property(S): WatsonAQSignoffFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 = C:\WINDOWS\PCHEALTH\ERRORREP\QSIGNOFF\
Property(S): LocalAppDataErrorReporting.D0DF3458_A845_11D3_8D0A_0050046416B9 = C:\Documents and Settings\Administrator\Local Settings\Application Data\PCHEALTH\ERRORREP\
Property(S): WatsonUQHeadlessFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 = C:\Documents and Settings\Administrator\Local Settings\Application Data\PCHEALTH\ERRORREP\QHEADLES\
Property(S): WatsonUQRegularFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 = C:\Documents and Settings\Administrator\Local Settings\Application Data\PCHEALTH\ERRORREP\QREGULAR\
Property(S): WatsonUQSignoffFolder.D0DF3458_A845_11D3_8D0A_0050046416B9 = C:\Documents and Settings\Administrator\Local Settings\Application Data\PCHEALTH\ERRORREP\QSIGNOFF\
Answered 11/10/2006 by: mkali
Orange Belt

Please log in to comment
0
Hi mkali,
you're allmost there :-)
Please post the portion of the log between the following lines:
MSI (s) (A8:A4) [11:48:14:771]: Executing op: ServiceInstall(Name=usnsvc,DisplayName=Messenger Sharing USN Journal Reader service,ImagePath="C:\Program Files\MSN .....

and:

DIFXAPP: Rollback failed with error 0x2 .....

Regards, Nick
Answered 11/10/2006 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Action ended 11:48:19: InstallFinalize. Return value 3.
Answered 11/12/2006 by: mkali
Orange Belt

Please log in to comment
0
Hi mkali:

Seems that its not able to install a service or driver read error:

DIFXAPP: Rollback failed with error 0x2

I would suggest one thing, it would be good if you run the installation without /qb param, this way it would show you the error box, try doing that and I hope you have the admin priviledges on this machine (just curious to know).
Answered 11/12/2006 by: wiseapp
Second Degree Green Belt

Please log in to comment
0
Thanks. I tried. But it did not prompt up any error screen for me.
Just rollback and said it have not installed to my machine.........[:@]

I have 1 more questions. Did i download wrong version?
I download it from http://get.live.com/messenger/overview.
Then copy the msi from temp file during running the exe.

[:(]
Answered 11/12/2006 by: mkali
Orange Belt

Please log in to comment
0
I am trying the same thing at my end... let me find out whats bothering your installation.
Answered 11/12/2006 by: wiseapp
Second Degree Green Belt

Please log in to comment
2
Hi mkali,
didn`t know, this would be that big.:-)
The problem lies here:
CacheSourceMsiDeferred:CopyFile (\\hkgcsm01.twi.hk\APSOFTWARE\Microsoft\WLM\8.0\MsnMsgs.msi, C:\WINDOWS\Installer\MSN Messenger 8.0.0812\MsnMsgs.msi) failed (1603)
MSI (s) (A8:A4) [11:48:19:340]: User policy value 'DisableRollback' is 0
MSI (s) (A8:A4) [11:48:19:340]: Machine policy value 'DisableRollback' is 0
Action ended 11:48:19: InstallFinalize. Return value 3.

Somehow the copy of the MSI file to the cached source fails.
Do you have any idea, why?
If you don`t need a local cache, you could disable it for the moment.
Hope this helps.
Regards, Nick
Answered 11/13/2006 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
O....Thanks.

No idea.....

How to disable local cache? & re-enable it after that?
Answered 11/13/2006 by: mkali
Orange Belt

Please log in to comment
1
Hi mkali,
load the MSI in ORCA again and set condition that solves to false to the CacheSourceMsiDeferredb action in the InstallExecuteSequence table.
And check the rights on your source, you most likely have a rights issue here. Maybe there is not enough space on the target machine to cache the MSI.
And please delete the messages above which contain useless log entries. This would make the thread readable again. :-)
Regards, Nick
Answered 11/14/2006 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Thanks. i have deleted some logs.

But the MSI does not contain CacheSourceMsiDeferredb action in the InstallExecuteSequence table....Even i added it manually, it's still fail.....

I don't know why if i run the original Setup.exe at the same place. It installed successfully.

But if i run the Msi, it will fail......[:(]

I check the share drive, it's everyone full control....

Any other thing i can do?
Thanks.
Answered 11/14/2006 by: mkali
Orange Belt

Please log in to comment
0
Hi Mkali:

I tried it at my end with the same things that you have done, it runs absolutely smooth. However reading your logs the rollback is failing at Difx function thats the function which is doing something with either the drivers or the services check this out.
Answered 11/14/2006 by: wiseapp
Second Degree Green Belt

Please log in to comment
0
Hi wiseapp,

Thanks your information. So which actions/procedure i should take?
Answered 11/14/2006 by: mkali
Orange Belt

Please log in to comment
0
Even i test it at my clean WinXP SP2 VM, it still fail. [&:][X(]
Answered 11/14/2006 by: mkali
Orange Belt

Please log in to comment
4
Got it Mkali! This problem is comin only when you try running the msi from a mapped or network share try running the msi from your local harddrive it wont give you any errors, I tried it on the local drive and it worked but when i created a mapped share then it failed. My suggestions:

1. Try to create a mechanism wherein you copy this MSI to a local temp folder and after that you delete, do not run the same from the share directly.

2. I created a batch file which copies this msi to the local directory and after completion it deletes it,

I know this looks weird but its not running directly from the server share I had to copy it first on my local drive and then execute the same with a deletion in the end.

Try doing the above, do let me know when ur done with it...
Answered 11/15/2006 by: wiseapp
Second Degree Green Belt

Please log in to comment
0
O.......YES. IT WORKS NOW!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
THANK YOU VERY MUCH~ [:)][:)]

Will you add this extra information to the package?
Answered 11/15/2006 by: mkali
Orange Belt

Please log in to comment
0
mkali,

Don't you think mr. wiseapp deserve a point for helping you to solve this annoying problem ;)
If so hit the "Rate post" link at the end of this last post.
Answered 11/15/2006 by: AngelD
Red Belt

Please log in to comment
0
RATED!! [:D]
Answered 11/15/2006 by: mkali
Orange Belt

Please log in to comment
4
Hi mkali,
to get it working without the workaround, you have to drop the line:
'CacheSourceMsi' from the 'InstallExecuteSequence' table.
Then it installs ok as far as i can tell.
Was close in my previous post, but the CA is called indirectly by the line above
Hope this helps.
Regards, Nick
Answered 11/15/2006 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Thanks Angel and Mkali for appreciating my efforts. It sounds good that we finally got it cracked and its all set to rollout.

Angel may be you or Bob can approve my information, I have added this but it shows pending, kindly approve it so that the same can be added to the package information.

Thanks once again Angel and mkali for the acknowledging my efforts!
Answered 11/15/2006 by: wiseapp
Second Degree Green Belt

Please log in to comment
0
Thanks nheim

Remove 'CacheSourceMsi' from the 'InstallExecuteSequence' table is also works for me.

GREAT!! [:)]

I think it should be included to the package, too.

Thanks all!!
Answered 11/15/2006 by: mkali
Orange Belt

Please log in to comment
0
leman
Answered 01/07/2007 by: leman42
Yellow Belt

Please log in to comment
0
I've tried all of the above steps and am still experiencing problems when assigning via GPOs.

1. Set MsgrFeat attribute to 16 (from 24)
2. Imported AdvtExecuteSequence to package
3. In Property table set IAGREE to Yes
4. Added ADDBHO = "No-ADDBHO", ADDLINKS = "No-AddLinks", SETHOMEPAGE = "No-SetMyHomePage"
5. Dropped the table CacheSourceMSI from InstallExecuteSquence table

All input is appreciated. I've also tried installing from network share and it works.

msiexec /i \\Server\MsnMsgs.msi /lvx* MsnMsgs.log /qb-
Answered 03/21/2007 by: Caveman
Senior Yellow Belt

Please log in to comment
0
Hi Peter,
'experiencing problems' is not exactly a helpfull description of your issues.
Please tell us what you are getting back from the system.
Make sure you log the installation (the log goes to %windir%\temp).
Check the Event Viewer Application section for entries.

Regards, Nick
Answered 03/22/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Event ID 102
Application Manager
The installation of Windows Live Messenger from policy Live Messenger failed. The error was: Fatal error during installation

Event ID 1085
Userenv
The group policy client-side extension Software Installation failed to execute. Please look for any errors reported earlier by that extension

MSI (s) (94:EC) [11:24:26:730]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI60.tmp, Entrypoint: InstallWLPhoneINF
MSI (s) (94:84) [11:24:30:137]: Executing op: ActionStart(Name=WriteUSNLaunchSID,,)
MSI (s) (94:84) [11:24:30:137]: Executing op: CustomActionSchedule(Action=WriteUSNLaunchSID,ActionType=3073,Source=BinaryData,Target=WriteBinarySID,CustomActionData=HKCR\AppID\{7178B45D-568D-4024-95FC-BC564C34542E}\LaunchPermission|O:LSG:LSD:(A;;CCDCSW;;;AU))
MSI (s) (94:D0) [11:24:30:152]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI61.tmp, Entrypoint: WriteBinarySID
WriteBinarySID(): Cannot open target key (HKCR\AppID\{7178B45D-568D-4024-95FC-BC564C34542E}).
MSI (s) (94:84) [11:24:30:293]: User policy value 'DisableRollback' is 0
MSI (s) (94:84) [11:24:30:293]: Machine policy value 'DisableRollback' is 0
Action ended 11:24:30: InstallFinalize. Return value 3.
Answered 03/22/2007 by: Caveman
Senior Yellow Belt

Please log in to comment
0
Hi Peter,
the problem isn't that new at all. See:
http://itninja.com/question/how-do-you-roll-out-new-machines?2151&mpage=1&key=嚇

this looks to me, as if we do have some kind of permission problem here.
On which OS are you trying to install? Looks like XP SP2?
Are you doing the install with an admin account?
Do you have locked down the machine with extra policies?
One try could be to change the TARGET of the Custom Action SetUSNLaunchSIDSecure like this:
HKLM\SOFTWARE\Classes\AppID\{F07EFF1B-88F7-4076-ADAC-185F393785E9}\LaunchPermission|O:LSG:LSD:(A;;CCDCSW;;;AU)
or this:
HKCR\AppID\{F07EFF1B-88F7-4076-ADAC-185F393785E9}\LaunchPermission|O:LSG:LSD:(A;;CC;;;AU)
Regards, Nick
Answered 03/23/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Using Windows XP SP2, the install is assigned via GPO so the login account shouldn't matter? The machine is not locked down with any extra policies.

I've tried both the options you suggested and this is the log. Also i can install Skype 3.1 Business via GPO with the installer file in the same shared folder so I believe the file permissions are correct.

MSI (s) (D8:7C) [08:34:22:821]: Executing op: ActionStart(Name=InstallWLPhoneINF.4A20E693_103A_461B_B815_41F28630AA26,,)
MSI (s) (D8:7C) [08:34:22:821]: Executing op: CustomActionSchedule(Action=InstallWLPhoneINF.4A20E693_103A_461B_B815_41F28630AA26,ActionType=3137,Source=BinaryData,Target=InstallWLPhoneINF,)
MSI (s) (D8:18) [08:34:22:852]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI53.tmp, Entrypoint: InstallWLPhoneINF
MSI (s) (D8:7C) [08:34:25:805]: Executing op: ActionStart(Name=WriteUSNLaunchSID,,)
MSI (s) (D8:7C) [08:34:25:805]: Executing op: CustomActionSchedule(Action=WriteUSNLaunchSID,ActionType=3073,Source=BinaryData,Target=WriteBinarySID,CustomActionData=HKLM\SOFTWARE\Classes\AppID\{F07EFF1B-88F7-4076-ADAC-185F393785E9}\LaunchPermission|O:LSG:LSD:(A;;CCDCSW;;;AU) )
MSI (s) (D8:D0) [08:34:25:852]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI54.tmp, Entrypoint: WriteBinarySID
WriteBinarySID(): Cannot open target key (HKLM\SOFTWARE\Classes\AppID\{F07EFF1B-88F7-4076-ADAC-185F393785E9}).
MSI (s) (D8:7C) [08:34:26:399]: User policy value 'DisableRollback' is 0
MSI (s) (D8:7C) [08:34:26:399]: Machine policy value 'DisableRollback' is 0
Action ended 8:34:26: InstallFinalize. Return value 3.

Edit - PS, thanks your help thus far. I never though installing a Microsoft application over GPOs would be so involved.
Answered 03/24/2007 by: Caveman
Senior Yellow Belt

Please log in to comment
0
Hi Peter,
was a long shot i know.
Could you please look again at the log. The crashing CA is located right after the writing of the registry values. Can you make sure that these actions do not overlap (action start/end).
Another one would be to write the 'HKLM\SOFTWARE\Classes\AppID\{F07EFF1B-88F7-4076-ADAC-185F393785E9}' key through the registry table.
A session with registry monitor could also help to see to which locations this CA tries to write.

Your right: One of the worst setups, MS ever released, IMHO!
Regards, Nick
Answered 03/25/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Sorry, my experience with troubleshooting deployed applications is next to none. It might be easier if I give you the entire log to browse over rather than me posting the wrong snippets back and forth.

Link to install log is here.

Can I get you to clarify what you mean by writing the 'HKLM\SOFTWARE\Classes\AppID\{F07EFF1B-88F7-4076-ADAC-185F393785E9}' to the registry table? Thanks and excuse the ignorance.
Answered 03/25/2007 by: Caveman
Senior Yellow Belt

Please log in to comment
0
Hi Peter,
will need to deploy this app this week also.
So, i did a GPO install today (computer assigned) with then newest version (8.1). Did the suggested changes to the MSI.
And it Installed just perfect.
This must definitely be a permission problem, you got here.
Please try the following thing:
Go to the client and start a session with the system account (at <time+1Min> /interactive cmd)
Install it with: msiexec /i \\Server\MsnMsgs.msi /qn and log it.
If you get the same problem as with the GPO, start RegMon and do it again. Search the RegMon output for 'access denied' entries.
Regards, Nick
Answered 03/26/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
I've decided to throw in the towel with Assigning the install via GPO, Microsoft wins this one. Thanks for all of your help, i'm sure given time we could have gotten to the bottom of it but for the sake of a messenger program for 80 staff it's just not worth my time.

Below is the vbscript i've used to install messenger based on the computer account. It'll do..

Set msi = CreateObject("WindowsInstaller.Installer")
' set the UI level to basic
msi.UILevel = 2
' launch the installer
msi.InstallProduct "\\server\share\MsnMsgs.msi", ""
' clean up
Set msi = Nothing

When i get time i will look at how i can do a check to see whether Live Messenger is installed before running the update again but this'll do for now.
Answered 04/22/2007 by: Caveman
Senior Yellow Belt

Please log in to comment
0
Hi Caveman

I am experencing the same problem ; can you tell me how you got it to work i use the vbs script that you posted and it worked great for me but i will like to know how to get windows live mesenger to work if group policy so that in the future i will use this method instead
Answered 09/21/2007 by: cstewart
Yellow Belt

Please log in to comment
0
I think it should be included to the package, too. Well that would be best directed at MS, since it's their package. And the very best of luck with THAT! :) MS is SO responsive to feedback like this.
Answered 09/24/2007 by: VBScab
Red Belt

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