This blog is a collection of my experiences and findings in the Lync world. It is intended to document my experiences, and at times frustrations, with Microsoft's Lync and surrounding technologies. And more importantly...offers a central database for quick reference. This blog is separate from LyncSorted and thus runs its own subscriber feeds.
In my case this is where the problem was, somehow ... mysteriously the Authoritative Domain had changed. Update Now I have see this else where, when I have the opportunity to investigate why I'll come back and post an update.
at Microsoft.Rtc.Management.Deployment.Core.CompatTrustedService.GetTrustedService(ADSession session, ADObjectId containerId, String fqdn, String serviceType) at Microsoft.Rtc.Management.Deployment.Core.CompatTrustedService.Create() at Microsoft.Rtc.Management.Deployment.Roles.WebServices.GlobalActivate(IService service, Computer computer) at Microsoft.Rtc.Management.Deployment.Core.Service.GlobalActivate(Computer computer) at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog[T](Action`1 action, T arg)
Error: An error occurred: "Microsoft.Rtc.Management.Deployment.ActiveDirectoryException" "Found multiple objects with identity "lyncFE01.lynclab.local.McxInternal" in Active Directory."
Solution 1) Run Test-CsTopology -Report C:\temp\testtopology.html
2) Prepare the appropriate AD for a TXT file:Ldifde -f c:\temp\addif.txt -s DC_FQDN -d "CN=RTC Service, CN=Services, CN=Configuration, DC=lynclab, DC=local"
3) Find the duplicate entries in txt file. Then delete them from AD using ADSIE Edit
Problem You get the error message "Lync cannot verify that the server is trusted for your sign-in address"
Cause When Lync Communicator discovers the Lync FE to log on to it uses the SRV Record _sipinternaltls._tcp.SIPDOMAIN.com. If the associated server FQDN is resolved to a server that doesnt match the SIP DOMAIN then this error is presented.EG Below record is for DNS zone xxx.co.nz, Sip Domain is xxx.co.nz but target host is a .local FQDN
Add an A record (xxx.co.nz for the FE Server) with matches the Sip and DNS, then edit the SRV record to point to this record.
Problem Can't connect to the Lync Server control Panel directly but https:\\FQDN\cscp works
Solution Something I didn't realize is that the Control Panel uses the DNS _sipinternal SRV Record. This is the record in the DNS branch matching the SIP Domain and not necessarily the branch that matches the internal DNS naming.
Problem Lync cannot verify that the server is trusted for your sign-in address. Connect anyway?Cause Lync Client 2013 has an additional safety check implemented in that the users SIP Domain is compared with the FQDN of Lync server when the user tries to connect.
In the most environments, the SIP domain is different from the Active Directory domain.
Problem Communicator can't sign in and and reports:- Cannot sign in to Communicator because your computer clock in not set correctly...
Solution This is caused when there is a time difference between the Lync\OCS server and the clients. I think the maximum threshold is around 10 minutes for time difference. Correct this and you should be sorted
Problem When trying to sign in to Lync get the following error: There was a problem verifying the certificate
Solution It's either a certificate trust issue or a DNS name mismatch to the certificate that you have issued. The PC or device which you are using to logon to Lync needs to trust the certificate chain from which you generated the Lync certificate(s) and the DNS records used to locate and connect to the Lync server need to match the name(s) on the certificate.
In my case I was using Manual Login and pointed to the IP address which was obviously not in the certificate :p
Unable to change the default Meet URL. Get a red X and the OK button is greyed out.
Firstly let me say that I prefer adding a URL/meet than a meet.URL since I don't need to add additional SANs to my cert. This is the reason why this ussue has come up. In any event... Topology builder will allow you to add a Meet and Dialin URL that actually conflicts with the External Web Services (shouldn't let you...)
It does however give you an error if you try to make it the default or try to remove another meet url that is different from the External Web Ultimately the simple URL's and the External URL's need to be different
The error here says that the Credentials for the request to the site were deleted. It also explains how no delegation is set and user authentication isn't enabled. Of course this needs to be enabled!!!
Problem Partners receiving a large number of errors in the Edge Server event log like below
Solution The cause seems to be Lync still sending discovery packets every 10 minutes. If federation is allowed, add the SIP domain to the allowed list, if blocked - add the SIP domain to the blocked list. This will be followed by a final event entry stating that the problem has been resolved
Problem Foreign user is sent a Lync online Meeting Request, if the invited user has Lync installed but doesn't have Federation capabilities the Join Conference request url will fail (since it calls the local Lync client to connect) Solution Force the conference invite URL to launch the Web and Lync Attendee options and not local Communicator Client (if present) -Just append this to the url "?sl=1"
Problem Lync Communicator Mobile wont login Error Message Server unavailable at this time Solution On the Sign In page you enter your SIP Login name and password. However you also need to go to More Details (ios and WM7)\Options (Android) and add your user name. I have found that the username for WM7 needs to be Domain\User Name, although this format works on Android and ios simpoly adding the user name also works
Problem While trying to call in to a conference from an external PSTN connection the error "Sorry, I can't seem to connect you to your meeting..." Error Message S4 traces on snooper revealed a "foreign gateway" IP address been called by the Mediation server. Solution The default Gateway in Topology Builder was an old (decommisioned) SIP connection (aka "foreign gateway". Changed that to the gateway I was actually using to call out on - solved!
Problem ApplicationServer (includes Call Park Service) Starts and then stops within seconds Error Message ErrorCode=-2146893022 FailureReason=IncorrectNameInRemoteCertificate LocalEndpoint=127.0.0.1:62233 RemoteEndpoint=127.0.0.1:5075 RemoteCertificate=<null> Solution #1 make sure 127.0.0.1 localhost exists in hosts file #2 For EE Server you need add both the FQDN of pool name and server name as SAN in the default certificate.