Forum Discussion
kb3199088 breaks test-csucwaconference and hence the watchernode/monitoring
JonatanV, this should be addressed in the December 2017 Cumulative Update (CU6) that is available for download. See the following.
Update Page: https://support.microsoft.com/en-us/help/3061064/updates-for-skype-for-business-server-2015
KB (synthetic transactions): https://support.microsoft.com/en-us/help/4043633
MicrosoftCheck .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.
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
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.
Hi Nicholas
I must have missed your last reply here so sorry for the late reply.
Here is the result of the OutVerboseVariable:
Workflow Instance Id 'ff3a492c-f87a-4d3c-9d69-f24552b45c27', started.
Command line executed is 'Test-CsUcwaConference -TargetFqdn sfbfepool1.domain.com -ParticipantSipAddress sip:sfbstwatcher2@domain.com -RegistrarPort 5061 -OrganizerSipAddress sip:sfbstwatcher1@domain.com -Authentication TrustedServer -OutVerboseVariable detailLogs'.
Workflow 'Microsoft.Rtc.SyntheticTransactions.Workflows.STUcwaConferenceWorkflow' started.
Workflow 'Microsoft.Rtc.SyntheticTransactions.Workflows.STUcwaConferenceWorkflow' completed in '0.000298' seconds.
An exception '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)'.' occurred during Workflow Microsoft.Rtc.SyntheticTransactions.Workflows.STUcwaConferenceWorkflow execution.
Exception Call Stack: at Microsoft.Rtc.SyntheticTransactions.Activities.UcwaConferenceActivity.InternalExecute(ActivityExecutionContext executionContext) at Microsoft.Rtc.SyntheticTransactions.Activities.SyntheticTransactionsActivity.Execute(ActivityExecutionContext executionContext) at System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime) at System.Workflow.Runtime.Scheduler.Run()'UcwaLogIn' sequence activity started.
'UcwaLogIn' sequence activity completed in '2.7E-05' seconds.
Using machine certificate Auth.
'GetSTSUri' activity started.
Starting STS Uri Discovery...Get Sts Uri Activity : Internal Execute: Sip Uri=sip:sfbstwatcher2@domain.com
Get Sts Uri Activity : Internal Execute: Autodiscover result: Is Internal = False
Enter Get Sts Uri Activity : Get STS Uri Via Autodiscover : Sip Uri=sip:sfbstwatcher2@domain.com ; Is Internal= False
Get Sts Uri Activity : Get STS Uri Via Autodiscover : User Resources is NULL. Check if Autodiscover was Enabled and it succeeded.
Get Sts Uri Activity : Internal Execute: Sts Uri from Get STS Uri Via Autodiscover =
Enter Get Sts Uri Activity : Get STS Uri: Sip Uri=sip:sfbstwatcher2@domain.com ; Fqdn=sfbfepool1.domain.com; Port=5061
REGISTER response:CALL-ID: b4cfd953432b44efacb33400738995bd
CONTENT-LENGTH: 0
CSEQ: 1 REGISTER
DATE: Wed, 09 Aug 2017 07:02:50 GMT
FROM: <sip:sfbstwatcher2@domain.com>;epid=CBA3480BEF;tag=7483887f6b
SERVER: RTC/6.0
TO: <sip:sfbstwatcher2@domain.com>;tag=EEC297570ECCB9D14F9D7741C7D82694
VIA: SIP/2.0/TLS 188.95.244.32:57475;branch=z9hG4bK5589f021;ms-received-port=57475;ms-received-cid=8E79D500
WWW-AUTHENTICATE: NTLM realm="SIP Communications Service",targetname="SRV-SFBFE-002.domain.com",version=4
WWW-AUTHENTICATE: Kerberos realm="SIP Communications Service",targetname="sip/SRV-SFBFE-002.domain.com",version=4
WWW-AUTHENTICATE: TLS-DSK realm="SIP Communications Service",targetname="SRV-SFBFE-002.domain.com",version=4,sts-uri="https://sfbwebint.domain.com:443/CertProv/CertProvisioningService.svc"
Found STS Uri : https://sfbwebint.domain.com:443/CertProv/CertProvisioningService.svc.
STS Uri Discovery activity completed successfully.
'GetSTSUri' activity completed in '1.1499722' seconds.
'GetWebTicket' activity started.
Trying to get web ticket.
Web Service Url : https://sfbwebint.domain.com:443/WebTicket/WebTicketService.svc
Using Machine Certificate authentication.
Webticket response headers:Content-Encoding:
Vary:Accept-Encoding
X-MS-Server-Fqdn:SRV-SFBFE-002.domain.com
X-MS-Correlation-Id:2147594391
client-request-id:369aab1c-249b-43de-8395-fa2d22ff9c2d
Strict-Transport-Security:max-age=31536000; includeSubDomains
X-Content-Type-Options:nosniff
Content-Length:2376
Cache-Control:private
Content-Type:text/xml; charset=utf-8
Date:Wed, 09 Aug 2017 07:02:51 GMT
GetWebTicketActivity completed.
'GetWebTicket' activity completed in '0.5502882' seconds.
'UcwaCreateApplication' activity started.
Creating application activity started.
Completed creating application activity.
'UcwaCreateApplication' activity completed in '0.5395524' seconds.
'UcwaLogIn' sequence activity started.
'UcwaLogIn' sequence activity completed in '1.75E-05' seconds.
Using machine certificate Auth.
'GetSTSUri' activity started.
Starting STS Uri Discovery...Get Sts Uri Activity : Internal Execute: Sip Uri=sip:sfbstwatcher1@domain.com
Get Sts Uri Activity : Internal Execute: Autodiscover result: Is Internal = False
Enter Get Sts Uri Activity : Get STS Uri Via Autodiscover : Sip Uri=sip:sfbstwatcher1@domain.com ; Is Internal= False
Get Sts Uri Activity : Get STS Uri Via Autodiscover : User Resources is NULL. Check if Autodiscover was Enabled and it succeeded.
Get Sts Uri Activity : Internal Execute: Sts Uri from Get STS Uri Via Autodiscover =
Enter Get Sts Uri Activity : Get STS Uri: Sip Uri=sip:sfbstwatcher1@domain.com ; Fqdn=sfbfepool1.domain.com; Port=5061
REGISTER response:CALL-ID: 9c234382764e4a3c923296c4eaf4bc19
CONTENT-LENGTH: 0
CSEQ: 1 REGISTER
DATE: Wed, 09 Aug 2017 07:02:51 GMT
FROM: <sip:sfbstwatcher1@domain.com>;epid=274A1C8B7A;tag=db2f9b824
SERVER: RTC/6.0
TO: <sip:sfbstwatcher1@domain.com>;tag=CCECBC6021900CBEBE2AEED77FACB4DE
VIA: SIP/2.0/TLS 188.95.244.32:57476;branch=z9hG4bKe7c3b355;ms-received-port=57476;ms-received-cid=8DA35D00
WWW-AUTHENTICATE: NTLM realm="SIP Communications Service",targetname="SRV-SFBFE-001.domain.com",version=4
WWW-AUTHENTICATE: Kerberos realm="SIP Communications Service",targetname="sip/SRV-SFBFE-001.domain.com",version=4
WWW-AUTHENTICATE: TLS-DSK realm="SIP Communications Service",targetname="SRV-SFBFE-001.domain.com",version=4,sts-uri="https://sfbwebint.domain.com:443/CertProv/CertProvisioningService.svc"
Found STS Uri : https://sfbwebint.domain.com:443/CertProv/CertProvisioningService.svc.
STS Uri Discovery activity completed successfully.
'GetSTSUri' activity completed in '0.019337' seconds.
'GetWebTicket' activity started.
Trying to get web ticket.
Web Service Url : https://sfbwebint.domain.com:443/WebTicket/WebTicketService.svc
Using Machine Certificate authentication.
Webticket response headers:Content-Encoding:
Vary:Accept-Encoding
X-MS-Server-Fqdn:SRV-SFBFE-002.domain.com
X-MS-Correlation-Id:2147594392
client-request-id:8bb9a079-cabc-445b-85cc-33274a7355b4
Strict-Transport-Security:max-age=31536000; includeSubDomains
X-Content-Type-Options:nosniff
Content-Length:2386
Cache-Control:private
Content-Type:text/xml; charset=utf-8
Date:Wed, 09 Aug 2017 07:02:51 GMT
GetWebTicketActivity completed.
'GetWebTicket' activity completed in '0.0246738' seconds.
'UcwaCreateApplication' activity started.
Creating application activity started.
Completed creating application activity.
'UcwaCreateApplication' activity completed in '0.7338275' seconds.
'UcwaConference' activity started.
Conferencing activity started.
'UcwaDeleteApplication' activity started.
Deleting application activity started.
'UcwaDeleteApplication' activity completed in '0.0004567' seconds.Workflow Instance ID 'ff3a492c-f87a-4d3c-9d69-f24552b45c27' completed.
Workflow run-time (sec): 4.5312851.- Nicholas Burkhammer
JonatanV, this should be addressed in the December 2017 Cumulative Update (CU6) that is available for download. See the following.
Update Page: https://support.microsoft.com/en-us/help/3061064/updates-for-skype-for-business-server-2015
KB (synthetic transactions): https://support.microsoft.com/en-us/help/4043633
- Nicholas Burkhammer
Thanks for the info. After some testing, don't think it is .NET version related in this instance although the majority of the time we see that exception, it tends to be the instance. Regarding rolling back Core Components, I would be careful there. The local RTCLOCAL/LYNCLOCAL instances may have been updated, and rolling back CU code to a prior CU can result in issues if there were changes made that result in not calling a stored procedure, etc., in a manner expected.
Can you run the Test-CsUcwaConference cmdlet manually specifying the -OutVerboseVariable cmdlet, passing the verbose output to variable (reference cmdlet documentation for specific syntax), and then paste the results up to the exception and call stack? Don't need specific domain information from the output, so feel free to scrub it.