none
Error 429 in office2016/office365 version 1707 RRS feed

  • Question

  • Hi,

    We develop a com add-in of Excel, it works well in the past version of office. After update to versio 1707, build 8326.2062, open Excel will pop up an error message that "Error 429 : You do not have an appropriate license to use this functionality".

    Our developer found that it's due to update of  Microsoft Windows Common Controls. It's  Microsoft Windows Common Controls 6.0 before and works fine. Currently we just let our user not to update to this version.

    Can you let's know when you will fix it?

    Regards,

    Colin


    • Edited by rdchuang Thursday, August 10, 2017 8:54 AM
    Thursday, August 10, 2017 8:53 AM

Answers

  • Hi All,

    Seems MS fix it on version 1707 build 8326.2087,  update to this build and check it out.

    Monday, August 28, 2017 9:28 AM

All replies

  • Hi,

    We develop a com add-in of Excel, it works well in the past version of office. After update to versio 1707, build 8326.2062, open Excel will pop up an error message that "Error 429 : You do not have an approciate license to use this functionality".

    Our developer found that it's due to update of  Microsoft Windows Common Controls. It's  Microsoft Windows Common Controls 6.0 before and works fine. Currently we just let our user not to update to this version.

    Can you let's know when you will fix it?

    Thursday, August 10, 2017 8:52 AM
  • Hello Colin,

    What control do you use?

    I test in 1707 build 8326.2070 and add a ListView. There is no error. Please update to the latest version to check if your issue is fixed.

    Regards,

    Celeste


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, August 11, 2017 3:35 AM
    Moderator
  • Hi Celeste,

    Our developer found that office version 1707, build 8326.2070 wouldn't work with Windows Common Controls 6.0 . And our com add-in is using Windows Common Controls 6.0, so there's the problem of error 429(even in 8326.2070). Does MS note that and make them compatible?

    Regards,

    Colin

    Friday, August 11, 2017 9:16 AM
  • Hi Celeste,

    We have the same problem with our software which uses Windows Common Controls 6.0. and TABCTL32.OCX.

    This is VERY Serious for us as we have 500 clients relying on our software to produce Management Accounts and suddenly they can't.

    PLEASE MICROSOFT make this a priority. This could bring down our business.

    Here is the post we made in the Excel Developers Forum

    https://social.technet.microsoft.com/Forums/office/en-US/01122b02-f82a-40dc-b7ab-341b0a5790e2/latest-office-update-for-2016-seems-to-have-broken-tabctl32ocx?forum=excel

    Regards


    Steve Stretch

    Friday, August 11, 2017 1:17 PM
  • Hello Colin,

    Please follow the link below to revert you Office version to check if the issue would be fixed.

    https://support.microsoft.com/en-sg/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-clic

    If the issue is fixed, I suggest you submit a feedback in File -> Feedback.

    Recently, several customers report issues when using MSCOMCTL.OCX after updating.

    Here are the thread links.

    https://social.technet.microsoft.com/Forums/office/en-US/bda97d87-a41d-47a0-b55d-6db43d616db6/license-check-bug-in-latest-update-to-access-2016-activex?forum=Office2016ITPro

    https://social.technet.microsoft.com/Forums/office/en-US/01122b02-f82a-40dc-b7ab-341b0a5790e2/latest-office-update-for-2016-seems-to-have-broken-tabctl32ocx?forum=excel

    https://social.technet.microsoft.com/Forums/office/en-US/e642eac3-e842-4f5b-a774-5516b9bf8474/aug-1-office-update-kb4011051destroys-wmi-access-from-excel?forum=excel

    https://social.msdn.microsoft.com/Forums/office/en-US/6ea617d2-b1f2-476f-8bca-8cd4eac0f235/there-is-no-object-in-this-control?forum=accessdev&prof=required

    Regards,

    Celeste


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, August 14, 2017 7:40 AM
    Moderator
  • Hi Celeste,

    We desperately need to revert back over a hundered clietn PCs amd have looked at your link ...How to revert to an earlier version...

    running ClickToRunofficec2rclient.exe /update user updatetoversion=17.06.8229.2073 does not do anything. (this was the previous version). but on the screen to check what version you have 1706 (8229.2073) so i guess this is the corrrect format?

    Does the version number entered need to be something specific.

    Your earliest response would be great.

    Thanks in advance


    Steve Stretch

    Monday, August 14, 2017 9:21 AM
  • Hello Steve,

    The link is for click to run package. According to your thread, i think you are using msi package. Please visit Determining your Office version – MSI vs. C2R to confirm. For MSI package, we need to uninstall KB to revert to old version. Please uninstall the KB4011051 as Emi suggested. You could go to windows update and check the update history to uninstall the KB.

    Regards,

    Celeste


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, August 14, 2017 9:46 AM
    Moderator
  • Hi Celeste,

    Some of our clients (customers) are on MSI and some are on C2R. The first client we tried to fix was C2R, and the result as per previous post was unsuccessful.

    So, to determination if it failed because for some reason we are putting in an invalid 'updatetoversion' number. do we need to specify one of the below? (from website) e.g. 17.07.8326.2062

    Why are some in BOLD and other not? does this mean anything?

    Thank Celeste

    August 7, 2017

    Version 1707 (Build 8326.2070)

    Not applicable

    Not applicable

    July 31, 2017

    Version 1707 (Build 8326.2062)

    Not applicable

    Not applicable

    July 28, 2017

    Version 1707 (Build 8326.2059)

    Not applicable

    Not applicable

    July 27, 2017

    Version 1707 (Build 8326.2058)

    Version 1705 (Build 8201.2158)

    • Version 1701 (Build 7766.2099)


    Steve Stretch

    Monday, August 14, 2017 10:23 AM
  • OK, I've worked out that the Build Number (1707, 1706) etc IS TO BE IGNORED COMPLETELY. It's always 16.0.xxxx.yyyy

    So you type:

    ClickToRunofficec2rclient.exe /update user updatetoversion=16.0.8229.2103

    I have done this on 2 client PCs and the version has reverted back to 1706 and the problem has gone away.

    So we have a temporary fix.

    Please update us when more is know about the permanent fix.

    Thanks Celeste


    Steve Stretch

    Monday, August 14, 2017 2:13 PM
  • Hi Celeste,

    Can I just confirm from you that Microsoft are indeed looking into this issue and that an updated will be available at some stage as reverting to an previous version is only a temporary solution and i just need to report back to our clients what the current situation is.

    Thanks Celeste


    Steve Stretch

    Tuesday, August 15, 2017 10:13 AM
  • Hello,

    There is no official document to confirm this is a known issue. Emi has reported the issue, but no response has been received. Due to the limitation of community support channel, if the issue is urgent, you could contact the Microsoft professional support. If the support engineer determines that the issue is the result of a bug, the service request will be a no-charge case and you won't be charged.

    http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone

    Regards,

    Celeste


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, August 16, 2017 3:03 AM
    Moderator
  • Hi Steve,

    Same problem here, we had to rollback Office 2016 to version 1706 to get our COM adding to work as before.

    C:\Program Files\Common Files\microsoft shared\ClickToRun>OfficeC2RClient /update user updatetoversion=16.0.8229.2073

    Don't know what MS did to trigger this error 429 in version 1707 but all our customers on Office 2016 are impacted and no answer from Microsoft.

    HTH,

    Alain

    Tuesday, August 22, 2017 12:09 PM
  • Hi Alain,

    Yes that we are doing also, not ideal, as our customers do not want their systems put back but are being forced to.

    Celeste, have you anything more to report from Microsoft regarding this?

    Thanks in advance


    Steve Stretch

    Tuesday, August 22, 2017 12:15 PM
  • We have an Excel add-in that is comprised of an XLA that instantiates COM objects from a VB6 DLL.  Whenever a method in the VB6 DLL tries to load a form that contains controls from the MSCOMCTL.OCX control library, the following error is raised "429 - You do not have an appropriate license to use this functionality". We have run tests and confirmed that this occurs only with Excel 2016, build 1707.  Reverting back to 1706 will restore functionality.  The problem is that we have an install-base of 2500 customers.  Having everyone who receives the 1707 update revert back to 1706 is not a viable option due to the volume of support incidents it is creating.  We need for Microsoft to acknowledge this is a problem and fix it ASAP.

    Tuesday, August 22, 2017 5:21 PM
  • I opened a case with MS on August 11th and on the 14th received this message back from the engineer working the case "Multiple problems related to this issue is already reported to us and we are currently working to fix this problem."

    So they are aware of the problem.

    Tuesday, August 22, 2017 5:25 PM
  • Hi All,

    Seems MS fix it on version 1707 build 8326.2087,  update to this build and check it out.

    Monday, August 28, 2017 9:28 AM
  • Hello,

    Thanks for sharing the information here. It is helpful and I suggest you mark it as answer to close the thread.

    Regards,

    Celeste


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, August 29, 2017 2:08 AM
    Moderator
  • Hello,

    Please install KB4011093 if you are using MSI based edition.

    https://support.microsoft.com/en-us/help/4011093/august-22-2017-update-for-office-2016-kb4011093

    This update fixes the following issues:

    Regards,

    Celeste


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, August 30, 2017 9:42 AM
    Moderator