An Error Mgcchans Is Stopping Due To An Unhandled Exception
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Interop ProgramsLibraryForumsGalleryLync Blogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: OCS Group chat, auto configuration doesnt work, admin tool wont launch Lync Server , Lync > Lync 2010 and OCS - Lync Clients and Devices Question 0 Sign in to vote I've installed things with the following config: vsocs02 This is the ocs server, i have created a pool with a certificate here of vsocs02pool.domain.local Vsocsgc01 This is the group chat server.. i have configured the IIS cert on here as vsocs02pool.domain.local (i tried just vsocsgc01.domain.local before, no luck).. Vsocsgc02 This is the group chat compliance server. If i try auto configuration from a client i get: "cannot establish a network connection". If i do manual configuration.. it works, but then in communicator, i get a message from myself about being invited to a conference, but the group chat window never appears.. Same thing on the gc server, if i launch the admin tool.. it says that its inviting me to a conference, but i never see the group chat admin tool. I think the autoconfig issue is probably cert related, but i'm not sure what cert i should be using, or how it should be configured (i'm using my domain Enterprise authority to create the cert).. Any thoughts? Thanks Sunday, February 14, 2010 10:17 PM Reply | Quote All replies 0 Sign in to vote I stumbled onto some tips on how to configure the cert.. basically stating to use the OCS server's cert wizard to create a cert with the gc server name referenced, and the pool fqdn in the san.. so i followed these steps to recreate the cert and reinstall group chat.. but i still cannot get the admin console to come up.. nor can i get end user client machines to bring up the group chat window.. I did notice that t
2010 (Wave14) UC OCS 2007 R2 OCS 2007 R2 Group Chat Lookup Service fails tostart Filed under: UC OCS 2007 R2 — Leave a comment July 15, 2009 OCS 2007 R2 Group Chat Lookup Service fails to start Office Communications Server Group Chat Lookup Service fails to start and you see the following Event in the Event Viewer: Event Type: Error Event Source: OCS MGC Event Category: (1098) Event ID: 6381 Date: DATE Time: TIME User: N/A Computer: SERVERNAME Description: An error MGCLOOKU is stopping due to an unhandled exception has occurred due to an unhandled exception The certificate https://social.technet.microsoft.com/Forums/lync/en-US/8949b55d-c9dd-4672-869a-c94c22f89cef/ocs-group-chat-auto-configuration-doesnt-work-admin-tool-wont-launch?forum=ocsclients ‘CN=gcf.domain.com' must have a private key that is capable of key exchange. The process must have access rights for the private key… Reset the permissions so the Lookup Service and Channel Service have full control to the C:\documents and settings\all users\application data\microsoft\crypto\RSA\MachineKeys folder and the files in the folder and restart the service Like this:Like Loading... Related Comments RSS feed Leave a Reply Cancel reply Enter your comment here... Fill https://ledarma.wordpress.com/2009/07/15/ocs-2007-r2-group-chat-lookup-service-fails-to-start/ in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s Notify me of new comments via email. « Group Chat Stop both the channel and the lookupservers What ports do I need? Group Chat Server OCSR2 » Email Subscription Enter your email address to subscribe to this blog and receive notifications of new posts by email. Join 4 other followers Recent Posts Download Microsoft Lync Server 2010 Release Candidate(RC) OCS 2007, 2007 R2, lCS 2005 after upgrade Domain Controllers to Windows Server 2008R2 Audio and Video through the web browser via Wave 14 CS2010 Did you say Communications Server 14 would be supported virtualized? Really? The answer isyes Smart SIP OCS and Cisco Author By KevinPeters Address book will not syncautomatically Polycom does`t upgrade Error0x2ee7/0 Microsoft Office Communicator Always onTop Microsoft Office Communications Server 2007 R2 ServerUpdateInstaller.exe Hotfix KB968802 ID:504 error Presence offline in CWAR2 Categories Certificate authority (1) Exchange 2007 (1) Exchange2010 (1) LYNC 2010 (Wave14) (4) UC OCS 20
integrate well into the product. The server installation is a separate install, the client is http://www.itworkedinthelab.com/2012/09/lync-2010-group-chat-channel-service-crashes-after-startup/ separate and the installation process as a whole doesn't follow the http://www.shudnow.net/2009/03/18/office-communications-server-2007-r2-group-chat-deployment-part-2/ rest of the methods used in Lync. Fortunately, first glances at Lync 2013 makes it look like these things will be greatly improved in that version. In the meantime, I installed the Group Chat feature in my lab recently to do some testing and ran across the an error issue below… After the server started, the "Channel Service" (channelservice.exe) shutdown immediately; the application log on the Group Chat server showed that MGCCHANS had "stopped successfully". This event was followed by a Windows error report event with the following not-so-descriptive text: Log Name: Application Source: Windows Error Reporting Event ID: 1001 Description: Fault bucket , type 0 Event an error mgcchans Name: CLR20r3 Response: Not available Cab Id: 0 Problem signature: P1: channelservice.exe P2: 4.0.0.0 P3: 4cc14a3e P4: ServerCommon P5: 4.0.0.0 P6: 4cc149fd P7: 275 P8: 52 P9: VSZKJIURG0PVPRTZK4C0UMFFCF5NO5JQ P10: Attached files: These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_channelservice.e_fc1a205973cc651cbeb7209b17e5ec665b634ea_0d48b8f1 Analysis symbol: Rechecking for solution: 0 Report Id: bbaf572a-fd5c-11e1-b9f3-005056b30028 Report Status: 4 The real answer was found in ChannelServer.log file in "C:\Program Files\Microsoft Lync Server 2010\Group Chat Server\Logs". In this log was the following line: Microsoft.Rtc.Internal.Chat.Server.ServerCommon.Exceptions.StopServerException: Compliance enabled but not accessible, must shut down. This was indeed the case, the Compliance option was selected during the install but the server had not been provisioned yet. Disabling the Compliance option per the TechNet documentation was a quick fix that allowed the Channel Service to start successfully. As an odd aside, after making the above change I received the following prompt: I guess I'm not familiar with the timing of "at your leisure"… Posted by Joseph Palarchio at 2:12 AM Tagged with: Group Chat, Microsoft Lync 2010 Leave a Reply Cancel reply Name (required) Email (require
series. In Part 1, we started off by preparing our servers in preparation for OCS Group Chat Installation. We created our services, created our SQL Database, and assigned permissions. In this Part, I will go over the installation of our Group Chat Server and Administrative Tools. Part 1 Part 2 Group Chat OCS 2007 R2 Server Installation When installing OCS R2 Group Chat and running the setup executable, you will be asked to install several pieces of software to prepare the environment. You will be asked to install the Microsoft Visual C++ 2008 Redistributable. Click Yes to Continue. You will then be asked to install the Microsoft .NET Framework 3.5. Click Yes to Continue. You will then be asked to install the Microsoft Unified Communications Managed API 2.0 Core Redist 64-bit version. Click Yes to Continue. Once Microsoft Unified Communications Managed API 2.0 , you will be presented with the Welcome screen which will begin the installation process. Click Next to Continue. The next screen is the licensing screen. Make sure you fully read the entire agreement! Once you have done so (and I know you will, right?) Click Next to Continue. Enter your Username and Company information. Click Next to Continue. Enter the installation path you want the binaries installed to. Click Next to Continue. When the feature screen appears, you have 2 choices which are both selected at the same time. Keep in mind, that you must disable one of the options. You cannot have both the Chat Server and the Compliance Server collocated on the same box. Make sure the Chat Server is selected and the Compliance Server is not selected. We will be installing the Compliance Service in the next Part. Click Next to Continue. Confirm your installation. Click Next to Continue. Installation is ready to proceed. Click Next