Microsoft Lync Reference Error Id 504 Source Id 239
Contents |
failure. Here are a few and what they might be indicating. I hope they make your life a little easier: Instant Messages “
Lync Error Id 503 Source Id 239
there, they have an Edge, but you've simply nominated an invalid user - or guessed their e-mail naming format wrong. 2) skype for business There *is* such a user at the recipient’s domain – but they’re not enabled for Federation. There's an instance of OCS/Lync there & they have an Edge. [TBC] 3) There *may be* such a user at the recipient’s domain – but they don’t have open Federation and THEY don’t trust YOUR domain. [In this example, my lab domain is not Federated with Microsoft]. “
The (root) certificate from the company you are trying to federate with is not available. And by root certificate i mean the CA the company has accuired their certificate; Comodo, Baltimore Cyber Trust, Go Daddy etc. There are 2 ways to resolve this, find the sipfederationtls SRV DNS record like this: nslookup -type=SRV _sipfederationtls._tcp.microsoft.com SRV hostname = sipfed.microsoft.com Now you can try to get a certificate by guessing webmail domain names because the certificate at https://sipfed.microsoft.com:5061 doesnt return the certificate that you want. An easier ways is to https://greiginsydney.com/decoding-lyncs-client-side-error-messages/ download the RUCT tool (Remote RU Troubleshotter) found here Type the domain of the company you want to federate with and select the sipfederationtls SRV record, and on the Certificate Information tab click Go. After finding the domain you want to federate with you can install the certificate with one mouse click in the local trusted certificate store on the Lync EDGE server. You can https://vanbrenk.blogspot.com/2015/03/lync-federation-error-id-504-source-id.html easily find the imported certificate chain in the local trusted root store. Source 1 Source 2 Geplaatst door Edwin van Brenk op 15:45 Dit e-mailen Dit bloggen!Delen op TwitterDelen op FacebookDelen op Pinterest Labels: Lync 2010 Locatie: Utrecht, Nederland Geen opmerkingen: Een reactie plaatsen Nieuwer bericht Ouder bericht Startpagina Abonneren op: Reacties plaatsen (Atom) Zoeken in deze blog Wordt geladen... Follow by Email Blogarchief ► 2016 (22) ► oktober (1) ► september (5) ► augustus (3) ► juni (3) ► mei (2) ► april (1) ► maart (2) ► februari (1) ► januari (4) ▼ 2015 (31) ► december (4) ► november (1) ► oktober (6) ► september (3) ► juli (4) ► juni (2) ► mei (2) ► april (1) ▼ maart (2) Lync federation error ID 504 source id 239 Deleted item retention policy not working, well ac... ► februari (1) ► januari (5) ► 2014 (52) ► december (3) ► november (6) ► oktober (6) ► september (9) ► augustus (3) ► juli (2) ► juni (1) ► mei (3) ► april (4) ► maart (4) ► februari (7) ► januari (4) ► 2013 (47) ► december (7) ► nov
and Band Mobile Devices MSN https://community.office365.com/en-us/f/166/t/12676 Music, Movies & TV Office OneDrive Outlook.com Surface Virus and Malware Windows Windows Essentials Windows Insider Program Community Participation Center Participate How To Participate Ask a Question Start a Discussion Discuss the Microsoft Community Site Meet Our Community Leaders Getting Started error id FAQ Sign in Office Browse by product or topic Outlook Word Excel PowerPoint OneNote Access OneDrive for Business Skype for Business Office Insider Install, upgrade and activate My account, billing and sign-in All Topics Browse Office 365 for admin source id 239 topics Deploy Office 365 Upgrade to Office 365 Manage Office 365 Domains in Office 365 Directory Integration Services All Topics Ask, Learn, Solve Microsoft Community is a free community and discussion forum for asking and answering questions about using your Microsoft products. Tell me how it works Top Contributors English This site in other languages Bahasa Indonesia Čeština Dansk Deutsch Eesti Español Francais Italiano Magyar Nederlands Norsk, Bokmal Polski Português Suomi Svenska Tiếng Việt Türkce Ελληνικά Русский עברית العربية ไทย 한국어 中文(简体) 中文(繁體) 日本語 © 2016 Microsoft Microsoft Community Code of Conduct Community Participation Center Trademarks Privacy & Cookies Terms of Use Microsoft Community Code of Conduct Community Participation Center Trademarks Privacy & Cookies Terms of Use © 2016 Microsoft OK