Good afternoon, I'm hoping that you can help me.

We've got a Lync 2010 pool for internal use only without an edge server. It's been working fine for about a year, and conferencing used to work fine. We're not sure what's changed besides re-issuing the Lync certificate about 3-4 months ago. All services are running correctly, the certificates are all correctly published and trusted however, when trying to start a conference with more than one other user the following error appears on the client:

"The conference service did not respond. Please wait and try again".

As part of troubleshooting this issue, I've re-issued the certificate to the server and checked that is it being used for all purposes in IIS and is bound to the correct ports etc. within the IIS management console.

I've enabled client logging and get the following errors in the UCCP Log:

Component: UCCP
Level: ERROR
Flag: N/A
Function: N/A
Source: N/A
Local Time: 06/09/2015-13:28:41.958
Sequence# : 0000338C
CorrelationId : N/A
ThreadId : 1BDC
ProcessId : 0848
CpuId : 0
Original Log Entry :
06/09/2015|13:28:41.958 848:1BDC ERROR :: SIP_URL::InternalInitialize Didn't find host while parsing SIP URL

Component: UCCP
Level: ERROR
Flag: N/A
Function: N/A
Source: N/A
Local Time: 06/09/2015-13:28:41.959
Sequence# : 0000338D
CorrelationId : N/A
ThreadId : 1BDC
ProcessId : 0848
CpuId : 0
Original Log Entry :
06/09/2015|13:28:41.959 848:1BDC ERROR :: SIP_URL::ParseUrlParams invalid char F found when trying to parse params

Component: UCCP
Level: ERROR
Flag: N/A
Function: N/A
Source: N/A
Local Time: 06/09/2015-13:28:41.959
Sequence# : 0000338E
CorrelationId : N/A
ThreadId : 1BDC
ProcessId : 0848
CpuId : 0
Original Log Entry :
06/09/2015|13:28:41.959 848:1BDC ERROR :: SIP_URL::ParseUrlBase ParseSipUrlParams failed 80004005

Component: UCCP
Level: ERROR
Flag: N/A
Function: N/A
Source: N/A
Local Time: 06/09/2015-13:28:41.959
Sequence# : 0000338F
CorrelationId : N/A
ThreadId : 1BDC
ProcessId : 0848
CpuId : 0
Original Log Entry :
06/09/2015|13:28:41.959 848:1BDC ERROR :: SIP_URL::InternalInitialize ParseSipUrl(sip:Firstname Lastname) failed 80ee0012

This appears in event viewer:

A SIP request made by Communicator failed in an unexpected manner (status code 80ef025b). More information is contained in the following technical data:
 
 RequestUri:   sip:My email address;gruu;opaque=app:conf:chat:id:9ZJDC00S
From:         sip:My email address;tag=9a27b146d8
To:           sip:My email address ;gruu;opaque=app:conf:chat:id:9ZJDC00S;tag=9FB535301B3ED4D02DD5AF161F5E6258
Call-ID:      b771c84b055c4c9b904d9e6c742365ad
Content-type: application/sdp;call-type=im

v=0
o=- 0 0 IN IP4 Client IP
s=session
c=IN IP4 Client IP
t=0 0
m=message 5060 sip null
a=accept-types:text/plain multipart/alternative image/gif text/rtf text/html application/x-ms-ink application/ms-imdn+xml text/x-msmsgsinvite 


Response Data:
603  Decline
ms-diagnostics:  3098;reason="No MCU Factory Available";source=">Lync FQDN<";OriginalPresenceState="0";CurrentPresenceState="0";MeInsideUser="Yes";ConversationInitiatedBy="0";SourceNetwork="0";RemotePartyCanDoIM="No"

However, after trawling the internet this seems to be almost unrelated to the current issues I'm experiencing.

I'm lost as to where to go next and would appreciate a hand.

• Edited by dave.field Tuesday, June 09, 2015 12:35 PM

Hi Eric,

Thanks for the reply.

There doesn't appear to be any errors in event viewer on the single FE server. If there is a particular component that I should enable logging on the Lync server, I'll be happy to provide the output here. Unfortunately there are so many components I'm not really sure which one to enable logging on.

However, we don't use a load balancing system so at least that shouldn't be the issue :)

Regards,

Dave

Just going to update this thread because it looks like the issue is resolved now (paid for a Microsoft support call).

The issue happened because we use an offline root CA based PKI, this apparently causes Lync 2010 some issues when hosting the FE server on 2012 R2 (little did I know!).

However, the fix seems to be pretty easy. Adding the following registry keys and restarting all the services (and the Lync clients I may add) resolved the issue:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL]
"SendTrustedIssuerList"=dword:00000000
"ClientAuthTrustMode"=dword:00000002
"EnableSessionTicket"=dword:00000002

Hope this helps other people who are in a similar position as it had me tearing my hear out trying to get to the bottom of it.

Regards,

Dave

• Edited by dave.field Monday, June 15, 2015 3:53 PM
• Marked as answer by dave.field Monday, June 15, 2015 3:53 PM