Error Id 101 Source Id 238
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Interop ProgramsLibraryForumsGalleryLync Blogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Cannot sign in to Lync Attendee because of a problem connecting to the server. Lync Server , Lync > Lync 2010 and OCS - Edge Servers Question 0 Sign in to vote I can access the Meet simple URL using a web browser fine (via a TMG proxy). However when I try and join the same meeting via Lync Attendee I get this error (reference error ID 102 source ID 238). I take it this goes via the Edge server and not TMG proxy ? I have the following public DNS SRV record _sip._tls.company.co.uk Any idea's ? Thanks Bill Tuesday, November 15, 2011 1:20 PM Reply | Quote Answers 0 Sign in to vote Hi,Bill, If you use Lync web app you are talking to the reverse proxy which in turn talks to the internal Lync Front End pool(no edge involved unless and until you try to share your desktop which installs the plugin and then connects to the Edge server);If you use Lync Attendee it will connect to the Access Edge server and then establish a TLS session with the Access Edge server when you join a meeting.Based on your description,it seems a certificate issue on your Edge server,would you please check the certificate configuration with below: Internal Edge(Private,recommend be issued from the internal CA): SN: Internal Edge Interface FQDN(i.e. lsedge.contoso.com) SAN: null External Edge(Public): SN: Access Edge external interface FQDN or hardware load balancer VIP (for example,access.contoso.com). SAN: Access Edge external interface FQDN or hardware load balancer VIP (for example,access.contoso.com). Web Conferencing Edge external interface FQDN or hardware load balancer VIP (for example, webcon.contoso.com). Sip.domain.com (If you are using client auto-configuration or federation, also include any SIP domain FQDNs used within your company) Reverse Proxy(Public): SN: Reverse Proxy FQDN(i.e lsrp.contoso.com) SAN: External Web Services FQDN (i.e Lswebext.contoso.com) Dialin URL(i.e dailin.contoso.com) published Meeting URL(i.e. meet.contoso.com) Also please check your DNS setting with thethis link http://technet.microsoft.com/en-us/library/gg412787.aspx Another information about DNS requirements for your refer
KNOWLEDGE BASE Top Microsoft Lync & OCS from Microsoft Support Most Recent KBs for Lync 2010 Most Recent KBs for Lync Server Most Recent KBs for Lync Server 2010 Top Office 365 Solutions from Microsoft Support Most Recent KBs for Office 365 for enterprises Most Recent KBs for Office 365 for education LATEST LYNC SERVER UPDATES LATEST OCS UPDATES LINKS LYNC BUDDY ABOUT LINK & CONNECT CERTIFICATIONS https://social.technet.microsoft.com/Forums/lync/en-US/ca898e65-33c5-42ea-9236-94535c4bb99e/cannot-sign-in-to-lync-attendee-because-of-a-problem-connecting-to-the-server?forum=ocsedge & NOMINATIONS Tag Archives: lync-error-id-102-source-error-238 Troubleshooting Lync 101:16? Attendee client can not find server 4 Replies A client tried to invite some users that were federated and some that were not. The users that didn’t federate used the Attendee client and got an error saying “Cannot sign in to Lync Attendee because http://www.ultimate-communications.com/tag/lync-error-id-102-source-error-238/ of a problem connecting to the server. If the problem continues, please contact your support team. When contacting your support team, reference error ID 102 (source ID 238)” The Attendee does not have them same tools of troubleshooting as the full Lync client so there was no good logs to look at. After some reading and trial and error I found out that the client had not configured the external automactic configuration records correctly, to allow external automatic configuration. The record, _sip._tls.sipdomain.com, needs to be in place. It also needs to be in place for the internal SIP doamin being used. So if you are using an internal sip domain that is different from the published record domain you will need to rectifiy that before the attendee client will work. This entry was posted in Lync 2010 and tagged attendee, attendee-error-reference-error-id-102source-id-238, attendeeid102, cannot-sign-in-to-lync-attendee-because-of-a-problem-connecting-to-the-server, cannot-sign-into-lync-attendee-because-of-a-problem-connecting-to-the-server, cannot-sign-into-lync-attendee-error-id-102-source-id-238, error-id-102-source-id-238-lync-attendee, Lync Server 2010, lync-attendee-canot-signt-in-to-lync-attendee-because-of-problem-connecting-error-id-102, lync-attendee-client-filter, lync
client error which I hadn’t seen before “Call was not transferred because [user name] does not have an audio device set up to accept calls.” In this case, the error was a little misleading. http://tomtalks.uk/2011/07/lync-client-error-codes/ The endpoint the customer was transferring to was fine, and it was happening to more than one user. In actual fact this was a SIP Refer issue. As soon as we disabled https://support.cybersource.com/cybskb/index?page=content&id=C156&pmv=print&impressions=false SIP refer on the PSTN trunk, transfers were successful. In my troubleshooting I came across this useful reference list of SIP errors in the Microsoft protocol documentation, and thought it might come in error id useful. http://msdn.microsoft.com/en-us/library/gg132389(v=office.12).aspx Mode Error Id Error Message Additional Information Conference 400 [user name] cannot be reached. This person is using an application that does not support this type of meeting. Conference 404 [user name] cannot be found. Please check the address and try again. Conference 404 The meeting you are trying to join has ended. The meeting you are trying to join has ended error id 101 or does not exist. Contact your support team with this information. Conference 408 The conferencing service did not respond. Please wait and try again. Conference 408 The invitation to [user name] expired. Conference 410 [user name] cannot be found. Please check the address and try again. Conference 413 This online meeting cannot be found. This online meeting cannot be found on the server. Please check the meeting ID and try again. Conference 415 [user name] cannot be reached. This person is using an application that does not support this type of meeting. Conference 480 [user name] cannot be reached and may be offline. Conference 482 [user name] cannot be reached because of conferencing service issues. Conference 483 [user name] cannot be reached because of conferencing service issues. Conference 486 Cannot reach [user name]. Try again later. Conference 488 [user name] cannot be reached. This person is using an application that does not support this type of meeting. Conference 488 The meeting you are trying to join has ended. The meeting you are trying to join has ended or does not exist. Contact your support team with this information. Conference 500 [user name]
Entertainment Enterprise Retail Enterprise Travel Enterprise Small Business Our Integrations & Partnerships Partner Solutions Acquirers Payment Service Providers Technology Platforms System Integrators Become a Partner Payment Processing Cross-Channel PaymentsGateway & Processing ConnectionsPayment CardsDigital Wallets & Instant CheckoutDirect Debit & Bank TransfersReconciliation ReportsPayer AuthenticationGlobal Tax CalculationRecurring BillingAccount Updater Payment Security Secure Acceptance Web/MobilePoint-to-Point Encryption (P2PE)Payment Tokenization Fraud ManagementDecision ManagerManaged Risk ServicesPayer AuthenticationFraud AlertDelivery Address Verification Export Compliance Other Services Professional ServicesGlobal Support Options Getting Started Integration Methods Implement CyberSource Services Technical Documentation Test & Manage APIs & Integration Apple Pay™ Secure Acceptance Visa Checkout Simple Order API & SOAP Toolkit API Virtual Terminal Batch Upload Legacy Integrations Documentation by Product Type Global Payment Services Fraud Management Payment Security Reporting & Reconciliation Tax Services CyberSource Essentials Universal Management Portal Other Resources Server Release Notes SO API Release Notes Quick References Glossary Error / Reason Codes Merchant Support Knowledge Base Glossary Best Practices Global Support Options Quick References Error / Reason Codes Technical Documentation Integration Methods CyberSource Services Server Release Notes Simple Order API Release Notes Simple Order API & SOAP Toolkit API Test & Manage Legacy Integrations Merchant Account Administration Business Center Documentation Data Retention Policy Merchant Acquiring Account Pay My Invoice Processor Specifications Intro to Credit Card Services Operations & Procedures for Visa Merchants FAQs by Category CyberSource Account Type CyberSource Connection Method CyberSource Product / Service CyberSource Topic Find Answers Find Answers Enter que