Error Id 504 Source Id 239
Contents |
The (root) certificate from the company you are trying to federate with is not available. And by root certificate i mean the CA lync 2013 error id 504 the company has accuired their certificate; Comodo, Baltimore Cyber Trust, Go Daddy etc. lync 504 kilde id 239 There are 2 ways to resolve this, find the sipfederationtls SRV DNS record like this: nslookup -type=SRV _sipfederationtls._tcp.microsoft.com SRV hostname reference error id 504 (source id 239) = 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 when contacting your support team reference error id 504 (source id 239 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 easily
Error Id 403 (source Id 239)
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) ► november (8) `
failure. Here are a few and what they might be indicating. I hope they make your life a little easier: Instant Messages “
Lync Error 403 Source 239
There is no such user at the recipient’s domain. There's an instance of OCS/Lync microsoft lync error id 504 (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) There lync error id 403 *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 https://vanbrenk.blogspot.com/2015/03/lync-federation-error-id-504-source-id.html 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]. “
ID 504 (source ID 239). Will you be at the http://www.networksteve.com/windows/topic.php/Lync_2013_External_Networks/?TopicId=60518&Posts=3 event in Person November 14th, 2013 9:11am are you trying http://support.blackberry.com/kb/articleDetail?ArticleNumber=000025525 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 error id 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 error id 504 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
following message was not delivered More Details (Error ID 504)" appears when sending a message to a BlackBerry Client for use with Microsoft Office Communications Server from the Microsoft Lync Server or OCS 2007 R2 desktop client Article Number:000025525 First Published:August 15, 2015 Last Modified:March 22, 2016 Type:Support Environment BlackBerry Enterprise Server 5.0 SP3BlackBerry Client for use with Microsoft Office Communications Server 2007Microsoft Lync Server 2010Microsoft Office Communications Server 2007 R2 Back to top ↑ Issue Tracking JI 598603 Back to top ↑ Overview If this issue is present, the following symptoms will be observed: Users can successfully send messages from the BlackBerry Client for use with Microsoft Office Communications Server 2007 to the Microsoft Lync Server or Microsoft Office Communications Server 2007 R2 desktop client.Users are unable to send messages from the BlackBerry Client for use with Microsoft Office Communications Server 2007 to other users signed in from the BlackBerry Client for use with Microsoft Office Communications Server 2007. The error message Your message could not be sent (Error - failed to execute your last action (100)) will be received on the BlackBerry smartphone.Users are unable to send messages from the Microsoft Lync Server desktop client to the BlackBerry Client for use with Microsoft Office Communications Server 2007 R2. The error message The following message was not delivered More Details (Error ID 504)" "source id 239 will be received on the Microsoft Lync Server desktop client.On the BlackBerry Client for use with Microsoft Office Communications Server 2007, other users signed in from the BlackBerry Client for use with Microsoft Office Communications Server 2007 may appear to be offline.In the Microsoft Lync Server logs, event ID 14502 will be logged, indicating that there have been connection failures with the remote server. For Microsoft Office Communications Server 2007 R2 there may not be an error in the OCS event viewer logs. See the following example for the Microsoft Lync Server: Log Name: Lync Server Source: LS Protocol Stack Date: 12/22/2010 5:30:51 AM Event ID: 14502 Task Category: LS Protocol Stack Level: Error Keywords: Classic User: N/A Computer: OCSSERVER.EXAMPLE.COM Description: A si