Archive for the ‘MS Office Solutions’ Category

Error code 80090016 TPM has malfunctioned

Every once in a while you will encounter this error message when trying to activate a users’ office 365 license. The window that pops up doesn’t always point you in the right direction.

Typical Error message when entering creds to activate o365 license.

Researched many sites and each had many different solutions. However it seems one hit the nail on the head. First though here are other options I tried:

  1. Rename this folder to something else – have to first logon (after reboot) with admin account to machine. Rename C:\users\$dir\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy to same folder with .old at end of it. Note – doing this didn’t work for me but it did for others.
  2. Get access to this folder and clear the NGC folder: C:∖Windows∖ServiceProfiles∖LocalService∖AppData∖Local∖Microsoft∖; Link for this:; However in my case, there wasn’t anything in NGC folder – so yeah well not a solution.
  3. Reset – and or Clear TPM from windows. Did this and while it didn’t fix, for a time I couldn’t reboot the computer into windows. Removed UEFI boot/set to legacy boot – No joy. Multiple tries, shutdowns, unplug device, drain all power from system and then booting back and setting UEFI boot back and boom goes the dynamite!! – it booted back into Windows. Some days… Link for doing this procedure:
  4. Last and final attempt which happened to solve this riddle. Tried this one after performing #3. This link – under 3 post by Binod Shrestha, he shows to just open Device Manager, open Security Devices and Uninstall the “Trusted Platform Module 2.0 (or 1.1.2) from the PC.

After that reboot, log back in as the user with o365 issues, try opening up any Office app and now it just works, Office is activated and user config for OneDrive is all correct and no further problems. That’s just crazy!!

Hope this helps you the next time you run into such an error. Frustrating!!! again, thank you Microsoft!! <Rant>Seriously have to disconnect Office licensing from TPM and from Hotmail/live accounts </Rant).


Windows Server 20xx Essentials cannot connect to O365.

I found this cheat to reset the connection between the Essentials Server Dashboard and O365.

First check the log to find out why it’s failing.  Log file is found here:

C:\ProgramData\Microsoft\Windows Server\Logs\SharedServiceHost-EmailProviderServiceConfig.log

If log looks something like the below, then follow steps to fix:

BecWebServiceAdapter: Connect to BECWS failed due to known exception : System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. —> System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused


To fix:

Open Regedit and navigate to the following key:

HKEY_Local_Machine\Software\Microsoft\Windows Server\Productivity\O365Integration\Settings

Delete the BecEndPointAddress key.

Close Regedit and re-open the Essentials Dashboard.  Re-attempt to integrate with O365 and this time it should work.

Reference Link:;

Outlook 2007 slow performance

Had client that reported he was seeing very slow performance within his outlook 2007 profile. When he switched folders between Inbox and Sent folders, the top of the email window would show “loading” and pause for a bit before displaying the emails in the folder. Hmmm. well this could arise from a number of things and here is what I did to attempt to fix it:

Per some other blogs and newsgroup items I did the following:
1. Disabled some add-ons that I knew my client would never use
2. Compacted the PST database files – this helped a lot actually with performance.

3. Finally found a link on a news group that had article published by Microsoft that indicated they released a patch in December of 2010 that ended up causing more harm than good – causing performance issues etc. The patch was KB2412171. The link to Microsofts publication of the problem is here:

Here’s an excerpt from the article:
On Tuesday, December 14, we released an update (KB2412171) for Microsoft Outlook 2007. We have discovered several issues with the update and want to inform you about problems you might encounter and what corrective steps we recommend. As of December 16, this Outlook 2007 update has been removed from Microsoft Update

2.Noticeable performance issues are experienced when switching between folders if you do not have a Microsoft Exchange Server account configured in Outlook. Switching folders might take several seconds depending on the performance of your computer. This issue only applies when you use an IMAP, POP3, or Outlook Live Connector account, such as Windows Live Hotmail, and do not have an Exchange Server account configured in the same Outlook profile.

The article has a few other items and then explains how to remove the patch from your system.

After doing all of the above, Outlook now performs like a charm.
I still recommended to my client to run routine datafile compacting as it will speed up the overall performance for the user experience.

Adobe 8.1 has stopped working on Windows 7 & Outlook 2010

Had a client with a problem saving Adobe PDF files from within Outlook. Every time she tried to save a pdf the program would hang and close with the following error:
Adobe Acrobat 8.1 has stopped working.

I searched high and low on the internet via BING but couldn’t find anything that would finally work.
I disabled the antivirus, uninstalled all the extras with the full version – like outlook, IE and Access integration – all to no avail.

Then I remembered.. hmmm. maybe it needs to be set up for Compatibility with XP.
So I worked my way down into Program Files, went to properties of Acrobat.exe and clicked on the Compatibility tab. Set the compatibility to XP SP3…and also set it to run always as the administrator… The short end of the story is that the last option – Run as Administrator is the only setting that was necessary to get it to work properly :).

Whew… Sure wish someone at Adobe would get their troubleshooting docs updated to help customers out with this issue.

This solution solved it for my client. She can now open Adobe documents and save them without the program crashing.

Office 2010 Installation Failures

Everyone that has used any of the Office 2010 Beta’s know that the new office program just rocks! It certainly makes all the things they introduced in 2007 much much better and more user friendly…

However my post is not about how cool Office 2010 is but rather how much trouble it is getting it installed in the first place – especially when you have a previous copy of Office 2010 (one of the Beta’s).

I just upgraded my beta to a version I downloaded via my Partner MAPS program. However you need to first make sure you totally uninstall the previous versions before upgrading/installing the new version. This is something that may cause a bad response from customers – i.e. the customer upgrade/install experience :(..

This afternoon, I spent over an hour trying to get the new version installed without a hitch… It took about 4 different tries and many searches online to figure out why it kept failing…
Errors received: Error 2203 or 1935 both indicate some sort of access permission issues – even though I ran as Administrator and had full permissions to all the folders for Office installation.

Things I had to do to get the install to work include the following:
– uninstalling all office options – including
– Hotmail Connector
– Live Meeting (any version)
– Office communicator (any version).
– Make sure my account was added to all folders where office installs – under Program Files as well as under \windows\installer.

I then went into my Services.msc console and disabled and stopped Forefront Antimalware services – there are two related to forefront you need to set to disabled. After doing all of these, it’s good to reboot the system to make sure no office files are running nor Antimalware scanning is going on.

Next I went into the folders under Program Files\Microsoft Office and deleted what I could from that those folders. If you cannot delete some of the DLL’s, i suggest renaming them to something else and then rebooting after completing.

I then went into the registry and backed up some of the settings under HKCU\software\Microsoft\Office\14.0\.. there are folders for each application within Office where you can export settings such as where all your OneNote folders are as well as Outlook PST & OST files.

Finally after completing all of the above I was able to install Office 2010 Professional Plus without any blips.

The funny thing (or one of them anyway) about the failures is that it tells you the customer to call PSS for help on the setup and it references a path and a file on your computer that actually doesn’t exist :(.. So when the customer does end up calling PSS they have nothing to give to the PSS engineer :(… Pretty sad messaging there in the UI… The log files are actually found under: Systemdrive\users\username\appdata\local\temp\
the files start with: SetupExe(20100516..Plus a bunch of numbers).log
it is here that all the errors are reported and it takes a bit of searching to figure out what’s really going on.

Honestly, I think there is a lot to be said about proper error reporting as to why something doesn’t install properly. Rather than waste the customer’s time, why not just state in the installer for the customer to make sure all office applications + communicator are removed and to disable the antivirus software they are running before trying to install. Or make the installer do all these things for the customer so they’re experience will be made much better. Just a thought :)..

Anyway, I will continue to promote Office 2010 because I think it’s an awesome product… Where the customer may suffer is during the upgrade/install part. I hope Microsoft Office team can make things better for everyone prior to official release.

Categories: MS Office Solutions

Outlook Connector Prompts to be Upgraded

I got a call tonight from my sister asking for some help with fixing her Outlook Connector. Apparently today she started receiving a prompt every time she opened Outlook to upgrade the Outlook Connector… It gave her the option to Upgrade now or later. If she chose later, then Outlook wouldn’t be able to connect to Hotmail. :(.

The problem was that even if she chose to upgrade the connector, after restarting Outlook, she would receive the same error message :(.

I quickly connected to her computer using my LogMeIn account and started troubleshooting.
– I uninstalled and re-installed Outlook Connector – every which way I could think of – tried a very old copy – fail, tried version for first 2007 Outook – fail, tried the latest and greatest version 12.0.6xxx.1 – all failed! Each time it prompted to be upgraded again! Arrghh!

I did some searching out on the Newsgroups (there wasn’t much really because this appears to be a new issue) and found that the only way to resolve this was to install the OutlookConnector version for Outlook 2010.

Since Outlook 2007 is 32bit, I downloaded the 32bit version of OC for Office 2010 & installed it. It did prompt me one more time to upgrade but this time around it upgraded to the most recent version of 14+. Thereafter, Outlook opened and started to send/receive mail without any issue.

The link to Outlook Connector for Office 2010 is:
for 64bit version:
for 32bit version:

On their pages it states that it supports Outlook 2003, 2007 and 2010.
Hopefully this will work for you as well.

Categories: MS Office Solutions