Lync 2010 Error Id 504 Source Id 239
failure. Here are a few and what they might be indicating. I hope they make your life a little easier: Instant Messages “
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 https://greiginsydney.com/decoding-lyncs-client-side-error-messages/ at https://sipfed.microsoft.com:5061 doesnt return the certificate that you want. An easier ways is to 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 https://vanbrenk.blogspot.com/2015/03/lync-federation-error-id-504-source-id.html can install the certificate with one mouse click in the local trusted certificate store on the Lync EDGE server. You can 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) ► d
You've configured federation between http://terenceluk.blogspot.com/2013/04/unable-to-send-instant-messages-or-view.html two Lync Server 2013 environments and noticed that one of the organizations can send instant messages and see presence information http://www.networksteve.com/windows/topic.php/Lync_2013_External_Networks/?TopicId=60518&Posts=3 but the other one cannot. The following is the organization that can send instant messages and see presence: While the error id other company displays a globe indicating that the user is a federated contact and is able to receive messages, presence information is labeled as "unknown": An attempt to send a message to this federated contact will display spinning dots: … then source id 239 subsequently fail with the message: When contacting your support team, reference error ID 504 (source ID 239). Troubleshooting information is available online, including best practices for using Lync.TestWhen contacting your support team, reference error ID 1 (source ID 0). Troubleshooting information is available online, including best practices for using Lync. A quick debugging session with the logging tool on the front end server of the user who is unable to send or see presence information will show the following: TL_INFO(TF_PROTOCOL) [0]0C88.14F4::04/24/2013-22:53:16.498.0000358e (SIPStack,SIPAdminLog::ProtocolRecord::Flush:2387.idx(196))[2663723319] $$begin_record Trace-Correlation-Id: 2663723319 Instance-Id: 271E Direction: incoming Peer: svrgalyncedge01.ganet.internal:5061 Message-Type: response Start-Line: SIP/2.0 430 Flow Failed From:
ID 504 (source ID 239). Will you be at the event in Person November 14th, 2013 9:11am are you trying to connect to users in your organization or from other organization. Free Windows Admin Tool Kit Click here and download it now November 14th, 2013 12:22pm This is a common error with federation. If it is federated users, were they ever working? If not have you configured the edge server and the federation settings? Have you enabled users to be able to federate? November 14th, 2013 12:41pm Hi Somet, Agree with Georg. Would you elaborate more about your issue and your Lync environment (especially Edge server and Federation configuration)? Please check if your Edge server is down. Please check if the Edge server of your Federated party is down. If you can receive IMs from someone and get this error when you reply, check their systems external DNS or Edge configuration. Look for wrong or mis-configured DNS or NAT in the Topology. Please check ALL the certificates in the chain between you and the other end. Best Regards, Eason Huang Free Windows Admin Tool Kit Click here and download it now November 15th, 2013 7:38am This topic is archived. No further replies will be accepted. Other recent topics Remote Administration For Windows. Easy remote access of Windows 10, 7, 8, XP, 2008, 2000, and Vista Computers Click here to find out more Reboot Hundreds of computers, disable flash drives, deploy power managements settings. Click here to get your free copy of Network Administrator. Over 25 plugins to make your life easier