Answered by:
Install returns error: (80072F78)

Question
-
I know the notes say this is a connectivity/proxy issue. I have connectivity, and don't use a proxy. The software seems to install, churns on preparinf for use, and then throws the error and uninstalls. Win7 Pro. Any suggestion?Friday, December 4, 2009 9:13 PM
Answers
-
Hi Steve,
Had the same problem on my system.
See if your folders are Encrypted, if they are un Encrypt.
You may not need to do it to all folders but that is what worked for me.
Hope this helps.
Freespace442- Proposed as answer by Stephen BootsMVP, Moderator Tuesday, January 19, 2010 4:13 PM
Saturday, January 16, 2010 12:51 AM
All replies
-
I am having the same message.
I have no proxy either and no connectivity problem.
I have it installed in the same machine under another NT and Live ID, and it works correctly.
When I try to install it in another machine is when I have the error.
My system is a windows 7 professional x64.
I just post to add up to your problem and specify the OS and circunstances, if that can help.Saturday, December 5, 2009 7:05 PM -
This error typically means that bits of Live Mesh are already on the machine, either running or left over from a prior install that didn't get removed.
Is this a reinstall or a new install?
If it is a reinstall, have a look here: http://social.microsoft.com/Forums/en-US/LiveMesh/thread/e22e0115-98d1-47eb-b495-ff3e10acb0a6
-steve
~ Microsoft MVP Windows Live ~ Windows Live OneCare| Live Mesh|MS Security Essentials Forums Moderator ~Monday, December 7, 2009 2:23 PMModerator -
It was a new install for me. Win7 Pro, same error message. Tried both with and without proxy, with and without antivirus. Something's wrong...Tuesday, December 8, 2009 2:53 PM
-
It was a new install for me. Win7 Pro, same error message. Tried both with and without proxy, with and without antivirus. Something's wrong...
I wonder if you're hitting a leftover issue from the 12/3-4 problems. They were all supposedly resolved, but there may still be some residual issues.
Can you submit a bug report with your install logs?How to Submit Bugs and Live Mesh Logs
Note that you may not receive a response to the bug report, though. It will be transferred to the internal system to be assigned to the appropriate development group.
-steve
~ Microsoft MVP Windows Live ~ Windows Live OneCare| Live Mesh|MS Security Essentials Forums Moderator ~Tuesday, December 8, 2009 4:00 PMModerator -
Steve - All my attempts were new installs.
The problem with your log submittal instructions, is that there is no program group in which to enable logging.
Steps the install goes through are:
0 Installing Live Mesh Software
0 Preparing for use
0 Uninstalling Live Mesh Software...
Presumably this final step deletes the program group. Is there a residual reg key (left behind after uninstall) where I can enable it?
RegardsTuesday, December 8, 2009 4:16 PM -
There should be a servicing log. Sorry, I didn't provide that before!
If you run into an error during the installation of the Live Mesh software, a Servicing.log will be created. To get this log:
1. Click Start
2. If you are using Vista, type Servicing* in the search bar. If you are using XP, click Search and then type Servicing*
3. In the search results you will see Servicing.log or Servicing[0000].log depending on where the installation failed.
To go directly to the file, the Servicing log is in INSTALLDIR\Setup\Servicing.log or %temp%\Live Mesh\Servicing[0000].log if Live Mesh was uninstalled/rolled back during a failed installation.
-steve
~ Microsoft MVP Windows Live ~ Windows Live OneCare| Live Mesh|MS Security Essentials Forums Moderator ~Tuesday, December 8, 2009 5:14 PMModerator -
Steve - I uploaded the log earlier today. RegardsWednesday, December 9, 2009 9:53 PM
-
Thanks, Tom.
Hopefully it will reveal the cause and you'll hear back...
Can you post the bug report link here?
-steve
~ Microsoft MVP Windows Live ~ Windows Live OneCare| Live Mesh|MS Security Essentials Forums Moderator ~Thursday, December 10, 2009 2:01 PMModerator -
Steve - Just looked in the feedback section and it doesn't show I even submitted it. So here's the log:
Regards
========================================
Live Mesh Servicing Log
========================================
4392.8292{12/8/2009 11:09:44 AM}[tmarsh] logfile.cpp(184): CLogFile::CopyToTemp() Copied 'Servicing.log' to TEMP
4392.8292{12/8/2009 11:09:44 AM}[tmarsh] package.cpp(611): CPackage::Pend() PendUser Update=[Live Mesh: Windows Bootstrap x86 v0.9.4014.7]
4392.8292{12/8/2009 11:09:44 AM}[tmarsh] manager.cpp(414): CManager::UpdateApply() There are 1 updates in queues
4392.8292{12/8/2009 11:09:44 AM}[tmarsh] package.cpp(710): CPackage::Apply() Install Update=[Live Mesh: Windows Bootstrap x86 v0.9.4014.7]
4392.8292{12/8/2009 11:09:46 AM}[tmarsh] package.cpp(800): CPackage::Apply() Installed Update=[Live Mesh: Windows Bootstrap x86 v0.9.4014.7]
4392.8292{12/8/2009 11:09:46 AM}[tmarsh] packages.cpp(391): CPackages::Search() Online=Yes Scope=CurrentUser Criteria=IsHidden=0 and CategoryIDs contains '2a915f9b-a782-4101-8d33-61fde7bb9e4c' and IsInstalled=0
4392.8292{12/8/2009 11:10:19 AM}[tmarsh] manager.cpp(1204): CManager::LaunchSelf() Launching 'C:\Users\tmarsh.DFMLLC.000\AppData\Local\Microsoft\Live Mesh\Bin\Servicing\0.9.4014.7\MoeMonitor.exe' -Embedding
4392.8292{12/8/2009 11:10:19 AM}[tmarsh] manager.cpp(189): CManager::Shutdown() 0x80070005 AllowSetForegroundWindow(6708)
6708.12584{12/8/2009 11:10:21 AM}[tmarsh] notifywnd.cpp(630): CNotifyWnd::OpenNotifier() 0x80040154
4392.8292{12/8/2009 11:10:48 AM}[tmarsh] manager.cpp(871): CManager::Install() 0x80040154 Product did not install.
4392.8292{12/8/2009 11:10:48 AM}[tmarsh] manager.cpp(874): CManager::Install() 0x80072F78
4392.8292{12/8/2009 11:10:49 AM}[tmarsh] package.cpp(611): CPackage::Pend() PendUser Update=[Live Mesh: Windows Bootstrap x86 v0.9.4014.7]
4392.8292{12/8/2009 11:10:51 AM}[tmarsh] manager.cpp(414): CManager::UpdateApply() There are 1 updates in queues
4392.8292{12/8/2009 11:10:51 AM}[tmarsh] processes.cpp(265): CProcess::Shutdown() Shutdown(PID=6708 Name='MoeMonitor.exe')
4392.8292{12/8/2009 11:10:51 AM}[tmarsh] package.cpp(710): CPackage::Apply() Uninstall Update=[Live Mesh: Windows Bootstrap x86 v0.9.4014.7]
4392.8292{12/8/2009 11:10:51 AM}[tmarsh] logfile.cpp(184): CLogFile::CopyToTemp() Copied 'Servicing.log' to TEMP
4392.10640{12/8/2009 11:10:51 AM}[tmarsh] manager.cpp(1163): CManager::LatestModule() 0x8000FFFF
4392.8292{12/8/2009 11:10:52 AM}[tmarsh] package.cpp(800): CPackage::Apply() Uninstalled Update=[Live Mesh: Windows Bootstrap x86 v0.9.4014.7]
4392.8292{12/8/2009 11:10:52 AM}[tmarsh] logfile.cpp(184): CLogFile::CopyToTemp() Copied 'Servicing.log' to TEMP
4392.8292{12/8/2009 11:10:53 AM}[tmarsh] manager.cpp(1163): CManager::LatestModule() 0x8000FFFF
4392.8292{12/8/2009 11:10:53 AM}[tmarsh] logfile.cpp(184): CLogFile::CopyToTemp() Copied 'Servicing.log' to TEMP
4392.8292{12/8/2009 11:10:53 AM}[tmarsh] manager.cpp(893): CManager::Install() Setup returning 0x80072F78
7284.10092{12/8/2009 11:10:53 AM}[tmarsh] bootstrap.cpp(495): CBootstrap::MSIExec() 0x80072F78Thursday, December 10, 2009 3:20 PM -
I'm no expert on the logs, Tom, but it sure looks like the problem is with the Windows Update part of the install process.
You get a return code of 80070005 which generally points to a permissions problem when updates fail to install. The second error listed, 80040154, usually points to registry corruption. I believe it translates as "class not registered" - however, I'm not sure if it is in the log as part of the roll-back or a cause of the issue. The error you get displayed, 80072578, suggests the connectivity issue. Basically, it sees that there is something available to download, but the response from the server was not presented properly - invalid response.
Ken may be able to provide more help when he has a look at this, but I'm thinking that there's registry corruption in your user profile on Windows.
-steve
~ Microsoft MVP Windows Live ~ Windows Live OneCare| Live Mesh|MS Security Essentials Forums Moderator ~Thursday, December 10, 2009 4:23 PMModerator -
I'm getting a similar error:
========================================
Live Mesh Servicing Log
========================================
3676.1144{12/17/2009 6:30:31 PM}[Rhett] module.cpp(266): CComModuleEx::LockInstance() 0x800700B7
3676.1144{12/17/2009 6:30:31 PM}[Rhett] bootstrap.cpp(92): CBootstrap::Run() 0x80070652
3676.1144{12/17/2009 6:30:31 PM}[Rhett] logfile.cpp(184): CLogFile::CopyToTemp() Copied 'Servicing.log' to TEMP
3676.1144{12/17/2009 6:30:31 PM}[Rhett] main.cpp(98): wWinMain() 0x80070652
2556.3872{12/17/2009 6:30:41 PM}[Rhett] logfile.cpp(184): CLogFile::CopyToTemp() Copied 'Servicing.log' to TEMP
2556.3872{12/17/2009 6:30:42 PM}[Rhett] package.cpp(611): CPackage::Pend() PendUser Update=[Live Mesh: Windows Bootstrap x86 v0.9.4014.7]
2556.3872{12/17/2009 6:30:42 PM}[Rhett] manager.cpp(414): CManager::UpdateApply() There are 1 updates in queues
2556.3872{12/17/2009 6:30:42 PM}[Rhett] package.cpp(710): CPackage::Apply() Install Update=[Live Mesh: Windows Bootstrap x86 v0.9.4014.7]
2556.3872{12/17/2009 6:30:56 PM}[Rhett] package.cpp(800): CPackage::Apply() Installed Update=[Live Mesh: Windows Bootstrap x86 v0.9.4014.7]
2556.3872{12/17/2009 6:30:56 PM}[Rhett] packages.cpp(391): CPackages::Search() Online=Yes Scope=CurrentUser Criteria=IsHidden=0 and CategoryIDs contains '2a915f9b-a782-4101-8d33-61fde7bb9e4c' and IsInstalled=0
2556.3872{12/17/2009 6:30:58 PM}[Rhett] manager.cpp(267): CManager::UpdateScan() 0x80004002
2556.3872{12/17/2009 6:30:58 PM}[Rhett] manager.cpp(843): CManager::Install() 0x80004002
2556.3872{12/17/2009 6:30:59 PM}[Rhett] package.cpp(611): CPackage::Pend() PendUser Update=[Live Mesh: Windows Bootstrap x86 v0.9.4014.7]
2556.3872{12/17/2009 6:31:08 PM}[Rhett] manager.cpp(414): CManager::UpdateApply() There are 1 updates in queues
2556.3872{12/17/2009 6:31:08 PM}[Rhett] package.cpp(710): CPackage::Apply() Uninstall Update=[Live Mesh: Windows Bootstrap x86 v0.9.4014.7]
2556.3872{12/17/2009 6:31:08 PM}[Rhett] logfile.cpp(184): CLogFile::CopyToTemp() Copied 'Servicing.log' to TEMP
2556.2748{12/17/2009 6:31:08 PM}[Rhett] manager.cpp(1163): CManager::LatestModule() 0x8000FFFF
2556.3872{12/17/2009 6:31:09 PM}[Rhett] package.cpp(800): CPackage::Apply() Uninstalled Update=[Live Mesh: Windows Bootstrap x86 v0.9.4014.7]
2556.3872{12/17/2009 6:31:09 PM}[Rhett] logfile.cpp(184): CLogFile::CopyToTemp() Copied 'Servicing.log' to TEMP
2556.3872{12/17/2009 6:31:09 PM}[Rhett] manager.cpp(1163): CManager::LatestModule() 0x8000FFFF
2556.3872{12/17/2009 6:31:09 PM}[Rhett] logfile.cpp(184): CLogFile::CopyToTemp() Copied 'Servicing.log' to TEMP
2556.3872{12/17/2009 6:31:09 PM}[Rhett] manager.cpp(893): CManager::Install() Setup returning 0x80004002
3172.2060{12/17/2009 6:31:14 PM}[Rhett] bootstrap.cpp(495): CBootstrap::MSIExec() 0x80004002Friday, December 18, 2009 12:46 AM -
12056, what happens when you go to Windows Update to install updates? Does that work? Does the account you are installing under have Admin rights?
Have you tried updating the WU Agent? http://social.microsoft.com/Forums/en-US/LiveMesh/thread/1335008b-4f69-44d5-8544-2dc25771295e
See if this helps:
http://support.microsoft.com/kb/956708
-steve
~ Microsoft MVP Windows Live ~ Windows Live OneCare| Live Mesh|MS Security Essentials Forums Moderator ~Friday, December 18, 2009 1:17 PMModerator -
Morning, Steve - Happy New Year. Any more info on my error? Has Ken taken a look at it? I happened to try installing again today (just in case!) and it still fails. RegardsTuesday, January 5, 2010 2:20 PM
-
Morning, Steve - Happy New Year. Any more info on my error? Has Ken taken a look at it? I happened to try installing again today (just in case!) and it still fails. Regards
Morning and Happy New Year to you, Tom. I haven't heard anything. Let me ping Ken and see if can have a look and comment. I suspect that he's been swamped with the server issues encountered in December...
-steve
~ Microsoft MVP Windows Live ~ Windows Live OneCare| Live Mesh|MS Security Essentials Forums Moderator ~- Proposed as answer by Freespace442 Saturday, January 16, 2010 12:48 AM
- Unproposed as answer by Stephen BootsMVP, Moderator Monday, January 18, 2010 1:38 PM
Tuesday, January 5, 2010 3:54 PMModerator -
Hi Steve,
Had the same problem on my system.
See if your folders are Encrypted, if they are un Encrypt.
You may not need to do it to all folders but that is what worked for me.
Hope this helps.
Freespace442- Proposed as answer by Stephen BootsMVP, Moderator Tuesday, January 19, 2010 4:13 PM
Saturday, January 16, 2010 12:51 AM -
Hi Steve,
Had the same problem on my system.
See if your folders are Encrypted, if they are un Encrypt.
You may not need to do it to all folders but that is what worked for me.
Hope this helps.
Freespace442
Which folders were Encrypted, Freespace442? I don't see how this would be an issue with install, though Sync could sure be impacted by encrypted folders.
-steve
~ Microsoft MVP Windows Live ~ Windows Live OneCare| Live Mesh|MS Security Essentials Forums Moderator ~- Proposed as answer by Freespace442 Monday, January 18, 2010 6:33 PM
- Unproposed as answer by Stephen BootsMVP, Moderator Monday, January 18, 2010 6:50 PM
Monday, January 18, 2010 1:40 PMModerator -
Hi Steve,
It was the folders under Libraries aa well as the downloads directory.
Note: this is in windows 7 and under my user account. I was able to complete the process with the Admin account.
This also helped when installing an evaluation copy of MS Office PRO 2007.Monday, January 18, 2010 6:38 PM -
Ah! I see! So, your download/installer files were located within an encypted folder....
-steve
~ Microsoft MVP Windows Live ~ Windows Live OneCare| Live Mesh|MS Security Essentials Forums Moderator ~Monday, January 18, 2010 6:49 PMModerator -
Yes, and being I left the default selection when downloading, this may be what is effecting others.
Every site I went to had the same error codes and descriptions that I was receiving.
Nice thing, it's easy to try.Monday, January 18, 2010 10:17 PM -
i got the same error, and tried messing with windows firewall (like suggested in other threads). for me what fixed the problem was:
i had windows updates turned off, once turned on it installed just fine.
i hope this works for more people getting this error.
greets,
y0Sunday, January 24, 2010 3:19 PM