Share via

OLicenseHeartbeat.exe - APPCRASH - Error showing in Reliability History

Anonymous
2021-03-04T07:41:55+00:00

Why am I getting the following error in the Reliability History during the night after a clean installation with all updates done?

This shows on two different computers (one in English UK and on in French CH). The copies were successfully activated. Can I prevent this?

***Moved from: [Microsoft 365 and Office / Install, upgrade and activate / Windows 10 / Microsoft 365 Apps or Office 365 Business]***

Microsoft 365 and Office | Install, redeem, activate | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

15 answers

Sort by: Most helpful
  1. Anonymous
    2021-03-11T11:03:41+00:00

    Heartbeat Exe not working - Microsoft Community

    Try to perform a manual update of Office. Open any Office application (e.g., Word) and go to File / Office Account / Office Updates and select Update Now. After the update OLicenseHeartbeat.exe no longer exists. It seems to be the solution (by eliminating the source of the problem!).

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-03-08T13:20:21+00:00

    I also have this same error as of 3/6/21 after the 3/5/21 Office update. I am running Office 16 Pro 64bit install. I also have 2 older PC's running Office 16 Home & Student with 32bit installs, both have the same update but no App Crash error. Here is what I found:

    Search "Task Scheduler" and open the App. Go to Task Scheduler Library - Microsoft - Office. In the middle pane you will see a task called "Office 15 Subscription Heartbeat". It is a scheduled task to run the OLicenseHeartbeat.exe at 12:00AM. When this runs, it will cause the error. In the case of the 2 PC's with the 32bit installs and why no errors, it is because the task cannot run due to the file path in the task is for the 64bit install so it cannot find the file for the 32bit install as it is in the "Programs (x86) directory and not in the "Programs" directory.

    Office runs fine with no issues for the 32bit installs. Evidently, the OLicenseHeartbeat.exe not running on schedule for the last several days has not affected the performance of the program. I have disabled this task on my 64bit install PC and it also has not had any adverse affect on the Office performance. It works as it always has and now no more errors in the Reliability History Monitor. For some reason should Office later develop a related issue, just re enable the task then go to C:\Program Files\Common Files\microsoft shared\OFFICE16\ and manually run the OLicenseHeartbeat.exe file.

    It's been my experience with disabling certain Office tasks that once the next Office update is pushed out all tasks will be reset and enabled back to their defaults. If the update fixes this issue all is good. If not, then you will see the App Crash again and will have to disable the task again.

    I have filed this Problem Report in the Feedback Hub with the above information. Since the App Crash does not cause any issues with Office so far, I'm sure there is no urgency to fix it. Also you will notice in the Reliability History that a report is sent to Microsoft about the App Crash. I'm sure they have been inundated since Office is on so many PC's.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-03-10T12:00:42+00:00

    Thanks for the information. FYI, as of this writing, I did not automatically receive the latest update yet and had to manually update from within Office. MS removed the offending task "Office 15 Subscription Heartbeat" from the task scheduler and the OLicenseHeartbeat.exe file from C:\Program Files\Common Files\microsoft shared\OFFICE16. Problem Solved!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-03-10T11:19:53+00:00

    This now appears to be fixed by the latest update.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2021-03-06T14:05:21+00:00

    I have a brand new Dell laptop with the latest Windows and had 0 errors on Reliability History. Working fine.

    Truth is, Microsoft Office 365 ProPlus was working fine for 1 month (received the new laptop 1 month ago) until last night automatically received the update from Version 2101 (Build 13628.20448) to Version 2102 (Build 13801.20266).

    Now, I turn on my computer and have the SAME issue (see below error). The problem is the update. Had the update not occurred, I'd had never known about this error. Your Office is fine and the program just crashed as a result of the update. Likely a one-time item.

    Faulting Application Path: C:\Program Files\Common Files\Microsoft Shared\OFFICE16\OLicenseHeartbeat.exe

    Problem signature

    Problem Event Name: APPCRASH

    Application Name: OLicenseHeartbeat.exe

    Application Version: 16.0.13801.20182

    Application Timestamp: 602dd932

    Fault Module Name: KERNELBASE.dll

    Fault Module Version: 10.0.19041.804

    Fault Module Timestamp: 0e9c5eae

    Exception Code: c06d007e

    Exception Offset: 000000000002d759

    OS Version: 10.0.19042.2.0.0.256.161

    Locale ID: 1033

    Additional Information 1: fe25

    Additional Information 2: fe2598982014b3017e66523903d0ddc3

    Additional Information 3: a604

    Additional Information 4: a604c4b1640c4358ff7ba7d3c516c2c1

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments