Office 2016 Licensing Service Not Available

Anonymous
2015-09-24T17:40:19+00:00

Since upgrade my Office 2013 software to Office 2106, I am seeing this error in the Windows 10 Event Log

Event 0, Office 2016 Licensing Service

The description for Event ID 0 from source Office 2016 Licensing Service cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Subscription licensing service failed: -1073418220

  • <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  • <System>

  <Provider Name="Office 2016 Licensing Service" />

  <EventID Qualifiers="0">0</EventID>

  <Level>2</Level>

  <Task>0</Task>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2015-09-24T04:12:50.000000000Z" />

  <EventRecordID>10572</EventRecordID>

  <Channel>Application</Channel>

  <Computer>TestSystem</Computer>

  <Security />

  </System>

  • <EventData>

  <Data>Subscription licensing service failed: -1073418220</Data>

  </EventData>

  </Event>

This error normally occurs daily, generated by Microsoft installed Task Scheduler task 'Office Subscription Maintenance' being run.  I've also manually run this task at different times of the day in case the problem is an overloaded license server.  No luck, always fails

Is this something additional I need to accomplish to "reset" something on my computer so it goes to the correct server to validate my license?

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

42 answers

Sort by: Most helpful
  1. Anonymous
    2017-05-28T14:39:58+00:00

    Hi,

    To better assist you with your concern, we suggest posting a feedback via the Feedback Hub so that our developers will be able to come up with a patch or a workaround for the issue.

    In order to submit new feedback, please follow these steps:

    1. On a Windows 10 device, search for 'Feedback Hub" in Cortana search, then launch the app.
    2. Navigate to Feedback in the left menu, then press Add new feedback.
    3. Select the Problem, and share any details you think are relevant, and choose an appropriate category and subcategory.
    4. Important: If possible, reproduce the problem(s) after clicking Begin Monitoring (or Start Capture) near the end of the form; Stop Monitoring when you're done.
    5. Once you've completed the form and monitoring, click Submit.
    6. Click Continue using Feedback Hub.
    7. Click My feedback at the top, then find the item you submitted (it may take a while to appear).
    8. Open the item you submitted, then click Share.
    9. Click Copy link, then paste the link here in your response (it will look like https://aka.ms/<unique link>).

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-05-26T05:12:19+00:00

    I am administrator of 450 Windows 7 workstations. We also have this issue in every our workstations which are using Office 2013/Office 2016. Every night when Office 15 Subscription Heartbeat scheduled task is running it gives an error Application event error Office 2016 Licsensing Service (

    Subscription licensing service failed: -1073418220).

    Everything seems to be working fine but these error events fill up my event collector and I have to clean up my event collector every morning because of this.

    Any ideas what to do? Just reinstalling/repairing office doesnt work for this issue.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-12-25T20:53:17+00:00

    As one of those individuals who has wasted a lot of time and efforts chasing it down."..... Hours later I am very pleased to finally find your post. I will happily ignore this matter.

    And if you had nickel for every bug......consider Word comes in 102+ other languages and everyone who participated in this thread could retire. 

    LAZ

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-10-24T20:05:52+00:00

    This is nothing new. Troubleshooting requires the elimination of the obvious (i.e. reboot, repair install, etc.) that's just how it works unless you've got a smoking gun in the logs pointing at something really specific. I hate to defend MS but, if you think you should always update/upgrade to the latest/greatest OS or version of Office, you're inevitably going to be in for some pain. Essentially you are still a beta user for the first year or two it comes out if you do. 

    Except these days updates are force fed by Microsoft unless you want to skip all updates including security issues.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-10-24T17:48:18+00:00

    This is nothing new. Troubleshooting requires the elimination of the obvious (i.e. reboot, repair install, etc.) that's just how it works unless you've got a smoking gun in the logs pointing at something really specific. I hate to defend MS but, if you think you should always update/upgrade to the latest/greatest OS or version of Office, you're inevitably going to be in for some pain. Essentially you are still a beta user for the first year or two it comes out if you do.

    Was this answer helpful?

    0 comments No comments