Dynamics 365 Outlook Client Install Error 8.2 KB3205084

Question Status

Verified
Henry B. Hickman asked a question on 19 Feb 2017 12:03 PM

We have workstations running Dynamics CRM 2016 Outlook Client version 8.0 and trying to update to Dynamics 365 8.2 and getting the following errors then rolls everything back. Anybody run across this? We've even uninstalled the Outlook client but it won'f this in searching for the latest updates.

06:58:22| Error| Setup did not complete successfully.

06:58:22|Verbose| Method exit: Microsoft.Crm.UpdateWrapper.UpdateSetup.RunInternal
06:58:22|Verbose| Update Not Completed
06:58:22|Verbose| Update Not Completed
06:58:22| Info| Dynamics 365 for Outlook Update 2.0 (KB3205084) was not completed successfully because of the following problems:

Action Microsoft.Crm.UpdateWrapper.SetPatchToUnremovableAction failed.
Couldn't find Registry Key: SOFTWARE\Microsoft\MSCRM\
Couldn't find Registry Key: SOFTWARE\Microsoft\MSCRM\

Reply
Scott Durow (MVP) responded on 19 Feb 2017 3:11 PM

I suggest following instructions on how to fully uninstall the add in blogs.msdn.microsoft.com/.../step-by-step-to-uninstall-the-dynamics-crm-outlook-client-successfully

Then re-install it and then use windows update.

Reply
ChocoTof responded on 20 Feb 2017 6:02 AM

I had the same problem this morning.

I found this on the internet, maybe this helps:

http://www.toplinestrategies.com/blogs/net/error-installing-crm-2013-outlook-client-service-pack-1

Anyway, let me know please?

TIA.

Reply
Henry B. Hickman responded on 20 Feb 2017 11:02 AM

We have tried the gamut and neither of the two recommendations, which we had reviewed before, worked. Station has been stripped down and Outlook client 2016 installed twice, any patch Update 1 or 8.2 is actually giving the same error. No answers and just to see if MS could solve it, opened up an incident ticket.

Reply
Suggested Answer
ilgy responded on 21 Feb 2017 9:52 AM

Just had the same issue. The recommendation for adding the software key worked.  I added a new key called "MSCRM"  at this location "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\" and the update completed. It added 2 new values under the key after completion.

Reply
Suggested Answer
Paul Craven responded on 22 Feb 2017 3:18 AM

Thanks ilgy - worked for me too.

Reply
Henry B. Hickman responded on 22 Feb 2017 6:35 AM

Even adding the registry keys didn't let it complete the update.

Reply
Verified Answer
Henry B. Hickman responded on 22 Feb 2017 8:30 AM

Had to come back and say yes, after adding it to another registry section, it worked. Thanks

Reply
hvillanueva responded on 16 Mar 2017 10:10 AM

Hi Henry H,  can you please specify which "another" registry section did you add it to?  I'm having the same issue after adding it to the specified section above.

Thanks,

Henry V

Reply
Vincent Verheijen responded on 30 Mar 2017 7:37 AM

@hvillanueva

het original was KEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\

note the wow6432Node. 

so they are probably running 32bit office, while you're running 64bit office.

you're key would probably be  KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\

so the same but without the wow6432node.

Reply
hvillanueva responded on 30 Mar 2017 8:39 AM

Thank you Vincent!

Reply
İsmail Tutumluer responded on 23 Oct 2017 9:53 AM

it's ok now.Thanks

Reply
Verified Answer
Henry B. Hickman responded on 22 Feb 2017 8:30 AM

Had to come back and say yes, after adding it to another registry section, it worked. Thanks

Reply
Suggested Answer
ilgy responded on 21 Feb 2017 9:52 AM

Just had the same issue. The recommendation for adding the software key worked.  I added a new key called "MSCRM"  at this location "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\" and the update completed. It added 2 new values under the key after completion.

Reply
Suggested Answer
Paul Craven responded on 22 Feb 2017 3:18 AM

Thanks ilgy - worked for me too.

Reply