none
WCF service moniker broken in office 365 RRS feed

  • Question

  • Hi,

    we have some .NET software that communicates with Excel through a service moniker.  Everything worked fine until the last update of office 365. Now the GetObject in vba code fails with an Automation Error Invalid Syntax -2147221020 (800401e4).

    It still works fine with the standalone version of Excel 2016 or other previous versions but not with the version downloaded with Office 365.

    Has the feature been removed? turned off?

    Details:

       OS : win 10, win 7 on a variety of machines

       WCF service programmed in C#, VS2013

    Tuesday, January 9, 2018 8:33 PM

All replies

  • Hi Robert,

    Did Excel 2016 and Office 365 install on the same computer?

    After installing the update, if you register a new WCF Service Moniker, will you receive the same error?

    To be honestly, we are not familiar with WCF Service moniker, could you share us a simple project and detail steps, then we could try to reproduce your issue at our side.

    Best Regards,

    Tao Zhou


    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, January 10, 2018 9:43 AM
  • Same issue with the latest update 8201.2213.

    Reverting back to previous office update i.e. 8201.2200 resolved the issue for us.

    Please let us know if you find a fix for it to work with the latest versions.

    Wednesday, January 17, 2018 11:21 PM
  • Hi RajST,

    Based on your description, it seems this issue is related with this specific version.

    I checked my avalible update, but, I could not update to the 8201.2213 version.

    I would suggest you ignore this update before next update comes.

    @Robert

    Could you check whether your issue is caused by this update?

    Best Regards,

    Tao Zhou


    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.

    Thursday, January 18, 2018 2:17 AM
  • The issue is caused by update. I also tried to update to newer built 8431.2153 and problem is still there.

    reverting to 8201.2200 - and all is working again. When is the fix will be available?

    Tuesday, February 6, 2018 2:47 PM
  • We're experiencing the same issue with a WCF call over mex to a remote Windows Service. The issue does not occur in 1708.8431.2110, and does occur in all versions from 1708.8431.2153 up to 1803.9126.2191 (targeted May 8 release).
    • Edited by FlorisMK Friday, June 22, 2018 8:09 AM misspelled WCF as WFC
    Friday, June 22, 2018 8:09 AM
  • Microsoft Tech Team,

    We're using Office 365 MSO(16.0.10730.20264).
    It's still failing with same error message.
    This is major problem for us to upgrade our business users to this version.
    Can your team fix it asap?

    Thank you!

    Ellen

    Monday, March 25, 2019 3:40 PM