Forum Discussion

JonatanV's avatar
JonatanV
Copper Contributor
May 29, 2017
Solved

kb3199088 breaks test-csucwaconference and hence the watchernode/monitoring

the latest update to core components breaks test-csucwaconference
i have verified it on two separate systems

after the update you get the following error:
Test-CsUcwaConference -TargetFqdn fepool1.domain.com -ParticipantSipAddress sip:watcher2@domain.com -RegistrarPort 5061 -OrganizerSipAddress sip:watcher1@domain.com -Authentication TrustedServer

Target Fqdn : fepool1.domain.com
Target Uri : https://sfbwebint.domain.com/CertProv/CertProvisioningService.svc
Result : Failure
Latency : 00:00:02.9260389
Error Message : Failed conferencing activity.Method not found: 'Void Microsoft.Rtc.Internal.Ucwa.ClientModel.Interfaces.InvitationDetails..ctor(System.String, Microsoft.Rtc.Internal.Ucwa.ResourceContract.CallType, Microsoft.Rtc.Internal.Ucwa.ResourceContract.Importance, System.String)'.
Diagnosis :

 

uninstalling the update again "resolves" the issue

 

this is still an issue after the latest may updates for s4b

16 Replies

  • Check .NET version, and ensure you have .NET 4.5.2 installed.  Missing method error indicates likely related to core code.  Error is in similar range to https://support.microsoft.com/en-us/help/3209492/step-1-of-sfb-2015-deployment-wizard-fails-after-you-install-cu4.  Would recommend installing .NET 4.6.2 as that is supported with SfBS 2015 servers per https://blogs.technet.microsoft.com/nexthop/2016/02/11/on-net-framework-4-6-2-and-skype-for-businesslync-server-compatibility/.

     

    Be aware of if .NET 4.5.2+ are installed, the May 2017 Security rollup for .NET results in this KB (

    https://blogs.technet.microsoft.com/uclobby/2017/05/24/lyncsfb-server-event-41026-ls-data-mcu-after-may-2017-net-framework-update/) happening, so plan workarounds accordingly.

     

    Hope this helps.

     

    • JonatanV's avatar
      JonatanV
      Copper Contributor

      Hi Nicholas

      Thanks for your reply

      As far as i can tell the error is not related to .net. However i do believe that its a change or a bug in the core code.
      Btw you can also run the test manually from another skype server, like front end, and you will get the same error.

      • Nicholas Burkhammer's avatar
        Nicholas Burkhammer
        Icon for Microsoft rankMicrosoft

        Jonatan,

         

        After performing  additional research, it is likely the issue you are experiencing is related to a product issue in Skype for Business Server 2015.  The stack trace from the error is going to be key here.  While the Method Not Found piece matches, it doesn't contain as much information as an output of the verbose variable that is a parameter with the cmdlet.  This will allow me to determine if it matches up with the particular stack trace related to the issue that we have been working on.  If you could provide that while replacing any PII type data (domain names, server names, user names, etc.), I’ll be able to provide a better answer.

         

        If your issue is related to the issue we've been working, we are hoping to release a fix in the next Cumulative Update (CU) for Skype for Business Server 2015.  Please ensure to note the following caveats.

        • Any timeframe references, CU references, etc., are tentative.  They can change without notice.
        • Fixes can be removed from updates if they don't pass validation and regression testing, etc.
    • Ken Barnett's avatar
      Ken Barnett
      Copper Contributor
      Did you have to back out the full CU or just one component? if one component which one?
      • JonatanV's avatar
        JonatanV
        Copper Contributor

        You only have to uninstall the sfb core components update to make it work again.

  • Maluks's avatar
    Maluks
    Iron Contributor

    Have received this error after applying SfB server CU5 on Saturday, but I cannot find the KB3199088 installed on Skype servers. 

  • JonatanV's avatar
    JonatanV
    Copper Contributor

    It would be great to get some feedback on this issue. Especially if its known by MS and will be fixed soon :)

     

    Regards

    Jonatan

Resources