Communicator Error Id 430
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Interop ProgramsLibraryForumsGalleryLync Blogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: reference error ID 430 (source ID 239) Lync Server , Lync > Lync 2010 and OCS -
Lync Reference Error Id 403 Source Id 239
Lync Clients and Devices Question 0 Sign in to vote I've seen many threads lync error id 504 source id 239 on this before and most of them have to do with federation issues but I have a user who tried office 365 admin portal to join 2 meetings and received this error. It was hosted by another internal employee and no people outside our domain were joining. Everyone else was able to get in fine (or so I'm told it was a big webinar training session so I don't know how many people joined) The user has done other Lync meetings fine. The only difference in this one was maybe the amount of people joining, and the join meeting link was posted on our internal sharepoint site. He tried twice on Sept 25 and 27th and was unable to get in. The next webinar comes in November so I'd like to figure it out by then. Is there anything on the PC side that could have prevented him from getting in? Thanks for the help! Tuesday, October 02, 2012 8:53 PM Reply | Quote Answers 0 Sign in to vote Hi,WeatherIT, So you mean the user can join other meetings except the webinar that the meeting link was posted on your internal sharepoint site? Since you said the only difference maybe the amount of people joinning,how many of them?As I know,the conference can only support 250 peoples to joina meeting by default due to resources and available processing power PER NODE.You can check Microsoft Lync server support large meeting white paper here. If not the cause,would you please tell more about the failed scenario?How does the user join in the webinar?From Lync client or browser?Internally or Externally?What the detailed error message when he joins in? Please turn on Lync server logging tool and Lync client log,reproduce the issue then use snooper to analyze the sip logto find out more specific information for troubleshooting.You also can use Wireshark or Netmon on the client PC to check the Network traces. Regards, SharonSharon Shen TechNet Community Support *************
Address LookupWhat's My IP AddressContact Tag Archives: error ID 403 (source ID 239) Lync On-Premise with Office 365 Federation - error ID 403 Leave a reply When communicating to hosted companies in Office 365 from an On-Premise Lync environment, I had begun seeing the following symptoms: Presence defaulted to Unknown for federated contacts: When joining someone's meeting or sending them an IM, I would see the following: "When contacting your support team, reference error ID 403 (source ID 239)." Inside of event viewer, I saw: 403 Forbidden ms-diagnostics-public: 1034;reason="Previous hop federated peer did not report diagnostic information";Domain="othercompanydomainon.com";PeerServer="sipfed.online.lync.com" Solution: Interestingly enough, even though you have an On-Premise Lync environment, it https://social.technet.microsoft.com/Forums/lync/en-US/b8b49c43-166d-49cf-9730-5c0ee200580f/reference-error-id-430-source-id-239?forum=ocsclients appears that Office 365 will tie back to your account for some settings. In my case, I had not enabled federation to other PIC providers on Office 365. To resolve the issue, please follow the steps below: Login to the Office 365 Admin Portal Click on Manage Lync Click on the External communications tab and ensure the following settings: Domain federation mode: Turned on http://jackstromberg.com/tag/error-id-403-source-id-239/ for all domains except blocked domains (you can switch to the other mode, just keep in mind you will have to whitelist every domain you are enabling communication with) Public IM connectivity mode: Enabled Next, head over to the Lync Online Control Panel for your on-premise Lync deployment. Select the Federation nand External Access tab and then select SIP Federated Providers Ensure you have created a rule for the provider LyncOnline that is federated to sipfed.online.lync.com
To create the provider via the Lync Server 2013 Control Panel Select New… and then click Hosted Provider Enable communications with this provider: Checked Provider Name: LyncOnline Access Edge Service (FQDN): sipfed.online.lync.com Click Commit To create the provider via PowerShell, execute the following command: New-CSHostingProvider -identity LyncOnline -ProxyFqdn sipfed.online.lync.com -Enabled $True Wait a few minutes for the changes to take effect, exit out of your Lync client on your workstation, reopen and you should now be able to communicate to your federated partner. Bookmark on Delicious Digg this post Recommend on Facebook share via Reddit Share with Stumblers Tweet about it Subscribe to the comments on this post Print for later Bookmark in Browser Tell a friend This en2007 Error ID: 309 Applies To: Communicator 2007 R2, Office Communicator 2007, Less Applies To: Communicator 2007 R2 , Office Communicator 2007 , https://support.office.com/en-us/article/Office-Communicator-2007-Error-ID-309-24317a0d-fa9c-49ba-bd66-f49b89dccd8d More... Which version do I have? More... Details Details Product: Office http://support.blackberry.com/kb/articleDetail?ArticleNumber=000025525 Communicator 2007, Office Communicator 2007 R2 Version: 2.0, 3.0 Source: Office Communications Server ID: 309 Message: Disabled by Policy Explanation You are attempting a task, such as sending an instant message with restricted content, that is disabled by a policy defined on error id the Office Communications Server. Cause Possible causes for Error Message 309 include: For security reasons, Office Communications Server provides organizations with the ability to create URL filters that block hyperlinks with the prefixes and/or extensions that are specified in the filter. Office Communications Server also provides the ability to create File Transfer filters to source id 239 prevent files with certain extensions from being transferred. Each organization is responsible for defining its own URL and File Transfer filters. Resolution If a URL in an instant message is returning a 309 error message, you can place an underscore in front of the URL to send the URL string in the instant message. For example, a URL such as http://example/example.asp?param1=a will raise a 309 error. However, if you place an underscore in front of this URL you can send the IM successfully. For example: _http://example/example.asp?param1=a. If you are trying to transfer a file that is restricted by policy, you should use a method other than Office Communicator file transfer to send the file. Share Was this information helpful? Yes No Great! Any other feedback? How can we improve it? Send No thanks Thank you for your feedback! × English (United States) Contact Us Privacy & Cookies Terms of use & sale Trademarks Accessibility Legal © 2016 Microsoft
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 Eve