Lync Reference Error Id 400 Source Id 239
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Interop ProgramsLibraryForumsGalleryLync Blogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: LYNC 2010 Federation works but not for external users Lync Server , Lync > Lync 2010 and OCS
Lync Reference Error Id 403 Source Id 239
- Interoperability Question 0 Sign in to vote Hello all, Weird, as this was when contacting your support team reference error id 1 source id 0 working at first but then stopped working. Lync 2010 Standard server, working fine for internal and external users. Federation IS
Lync Error Codes
working for internal users to GMail (using XMPP on separate server), AOL, Microsoft, and other OCS/LYNC federated partners. But it stopped working for remote users, so if I am working outside of the network, lync error id 504 (source id 239) I can sign in fine and do things with internal users and other remote users at other sites. But the Federation is not working. If my GMail user contacts me, the IM comes through and shows the message in the popup. But once I click it, the window is blank and no replies can go through. When contacting your support team, reference error ID 400 (source ID 239). Thanks lync error id 503 source id 239 for any suggestions, Greg Moved by Ben-Shun Zhu Thursday, February 17, 2011 7:58 AM incorrect queue (From:Edge Servers) Wednesday, February 16, 2011 3:15 PM Reply | Quote Answers 1 Sign in to vote OK finally some good updates. After lots of digging into logs, settings, etc, two very simple but brick-wall causing technical settings were found and fixed... then all the issues went away. 1) internal SRV record pointing to sipinternal.mig.com was all good, but the certificate on the front-end server was missing sipinternal.mig.com in the SAN entries. Once added, that ensured internal clients connected internally without falling back to the external sip.mig.com (edge external NIC) and having some routing issues 2) the edge internal certificate, which I had generated on the front-end using the Lync Wizard, and then exported/imported onto the EDGE, had the front-end FQDN as one of the SAN entries in addition to the various SAN entries that get created automatically). That was making the EDGE server think it was sending traffic to itself and bypassing some authentication checks. This was the item that once fixed, all the issues just went away once services were recycled. So, happy times now :-) Marked as answer by Greg M Pa
failure. Here are a few and what they might be indicating. I hope they make your life a little easier: Instant Messages “
Error Id 430 (source Id 239)
not be found and this message was not delivered” 1) There is lync call was not completed or has ended no such user at the recipient’s domain. There's an instance of OCS/Lync there, they have an Edge, but you've
Lync Reference Error Id 102 Source Id 238
simply nominated an invalid user - or guessed their e-mail naming format wrong. 2) There *is* such a user at the recipient’s domain – but they’re not enabled for Federation. https://social.technet.microsoft.com/Forums/lync/en-US/154496ce-cfda-478f-9c65-74e83d130077/lync-2010-federation-works-but-not-for-external-users?forum=ocsinterop 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]. “
a PBX I've been called a few times in the past to look at the issue where Lync Server 2010 http://terenceluk.blogspot.com/2013/03/lync-server-2010-or-2013-im-instant.html or 2013 IM (Instant Messaging) conference no longer works when RCC (Remote Call Control) is configured with a PBX and as simple as the root cause is for administrators who have configured RCC before, it may not be the same for ones who are doing it the first time so this post serves to list the symptoms and error id the solution to the issue. Problem You attempt to start a IM conference between 3 participants: The IM window above has 2 participants (both Terence Luk accounts). You attempt to invite the 3rd person into the IM chat window: You see the 3rd participant briefly displayed in the chat windows: … but quickly disappear leaving the IM: There are source id 239 times when you are able to bring the 3rd participant in but you receive the following error when you send a message: When contacting your support team, reference ID 400 (source ID 239). Troubleshooting information is available online, including best practices for using Lync. No one receives the instant message. Reviewing the application logs on the workstation's event logs show the following event ID 11 warning logged: The description for Event ID 11 from source Lync cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.If the event originated on another computer, the display information had to be saved with the event.The following information was included with the event: Lync80ef0190RequestUri: sip:tluk@contoso.com;gruu;opaque=app:conf:chat:id:FS500B1GFrom: sip:tluk@contoso.com;tag=582b69a2deTo: sip:tluk@contoso.com;gruu;opaque=app:conf:chat:id:FS500B1G;tag=(null)Call-ID: a5902bd56aa54dbab02f70021f05257fContent-type: application/sdp;call-type=imv=0o=- 0 0 IN IP4 10.40.2.10s=sessionc=IN IP4 10.40.2.10t=0 0m=message 5060 sip nulla=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:400 Bad request: TR87 protocol violation; required application/csta+xml content missing or invalidms-diagnostics-public: 1033;reason="Previous hop server component did