Comments on: Office Communications Server 2007 R2 Group Chat Deployment – Part 2

By: wolffparkinsonwhite

wolffparkinsonwhite — Fri, 20 Jan 2012 08:55:30 +0000

This is good stuff many thanks. It worked almost first time . I had an error when creating the web site but the reason was because I was binding only with the FQDN. I add a new binding with the machine name and it was fine.

By: Elan Shudnow

Elan Shudnow — Fri, 10 Jun 2011 04:07:12 +0000

Possibly due to database being on the same Group Chat Server. The database is not supported on the same server. This may be why the Group Chat database can't establish a connection.

By: Gary

Gary — Tue, 24 May 2011 15:13:28 +0000

Hello, thank you for this post very good information.

When I try to connect I get “Cannot establish a network connection. Make sure you are connected to the network and try again”

I have everything set the way you suggested, except for 3 things.

I am running this in a VMware.

I a self signed certificate created in IIS7 on the same server.

I am running the chat database on the same server as the Group Chat Server.

Would any of theses cause this problem?

Thanks
Gary

By: Sam

Sam — Thu, 02 Dec 2010 15:22:39 +0000

Pawel, I seem to be having the issue you're describing, yet I cannot get the admin tool to login. That's a good call on the debug logging, from that I've determined that the certificate I'm using appears to be the issue (error in the OCS log is: "The Group Chat server can not establish or maintain MTLS connection to the Office Communications Server.") but it's blowing my mind as to what I'm missing. SN/CN/SAN, you name it. It's all the FQDN of my Group Chat server. The cert is trusted, it's issued by the same internal CA as our MTLS cert for our OC server, it has server and client authentication enabled. I really cannot see what I'm missing here but at least the logging is pointing to the cert being the issue.

The ONLY thing that isn't consistent with everything else on the cert is the friendly name, which is (get this) a NICE name that is not the FQDN. Can it possibly be this mind-numbingly stupid little thing that is causing the cert not to work and thus no admin tool login? What else can I possibly look at to correct this?

THIS CHAT SERVER WILL BE THE DEATH OF ME.

By: jose

jose — Thu, 18 Nov 2010 22:00:27 +0000

Hi,

By: Sébastien

Sébastien — Thu, 07 Oct 2010 14:52:46 +0000

Hi all

Actually i’m trying to install a lab of OCS 2007 R2 Wint Exchange 2010.
My lab is :
1 GC on Windows 2008 R2 Fr latest Fix
1 DC on Windows 2008 R2 Fr latest Fix
1 Exchange 2010 Fr latest hot fix on Windows 2008 R2 Fr latest Fix
1 OCS Server 2007 R2 FR latest CU on Windows 2008 R2 Fr latest Fix
1 CWA serveur FR latest CU on Windows 2008 R2 Fr latest Fix
1 MEDIATION serveur FR latest CU on Windows 2008 R2 Fr latest Fix
1 Chat and Complicance serveur US on Windows 2008 R2 Fr latest Fix
1 Sql 2008 serveur FR latest SP on Windows 2008 R2 Fr latest Fix

My error is : SQL error [121] cant oppening database.

I follow the Microsoft Documentation, your documentation.

I tried install this chat and compliance serveur on seperate machine : result Idem
I tried install this chat server on an windows 2008 R2 US and SQL 2008 US : result idem
I tried install the SQL serveur in windows 2008 FR with SQL 2005 FR latest SP : result Idem.

I found some trick on Googled like OS version and SQL version (Spanish for exemple) not supported.

The trace i see on the SQL SQL is : tblversion and tblcomplicane version does not exist. But if i manualy create this table, the result is the same.

Is there every one can hel me ?

Thank a lot.

Sébastien, French Guy so sorry for my english.

By: Pawel

Pawel — Fri, 06 Aug 2010 11:38:25 +0000

my 2c after banging my head for 1 day with Admin Tool problem:

- review "Office Communications Server 2007 and 2007 R2 Certificate Guide.doc"
You must have the FQDN of the Group Chat Server as the SN/CN and you must also include the Client EKU for the Administration tool, otherwise the Group Chat administration tool WILL NOT BE ABLE TO CONNECT to the Group Chat server.
- you DON'T have to rebuild the Group Chat server from scratch each time you encounter an issue!! (learnt after 3 rebuilds..)
just run ServerConfigTool.exe located in %ProgramFiles%Microsoft Office Communications Server 2007 R2Group Chat Server and adjust settings as needed
- don't follow blindly all the posts googled regarding the issue, for instance this one http://blogs.technet.com/b/ucedsg/archive/2009/05…
suggests adding service accounts to RTCUniversalServerAdmins group :o :O
- if needed, run ServerConfigTool.exe and set Error Level for services to Debug. restart services then check Office Communications Server event log and review EACH event log entry (in my case, Information type-of had details about the error)

I also kept receiving "Cannot sign in because of a problem with the chat room service" (when using manual configuration) error.
In my case, the error was cause by certificate – make sure your cert has Client EKU enabled (I had to use modified custom Web Server template when requesting the cert).
If you include any SANs, make sure the last SAN entry matches certificate Subject Name.

By: Aaron Tiensivu's Blog

Aaron Tiensivu's Blog — Tue, 27 Jul 2010 19:29:57 +0000

Installing OCS 2007 R2 Group Chat Server on Server 2008 R2…

To begin, follow the instructions here for the usual Server 2008 R2 workaround/fixes for Server 2008 R2 and OCS 2007 R2. 1. From an elevated PowerShell prompt: Import-Module ServerManager [Enter] 2. Install the prerequisites for Group Chat Server wit…

By: eshudnow

eshudnow — Thu, 10 Jun 2010 01:26:15 +0000

Thanks for sharing that information. I have another article here on OCS Audio/Video in which I encountered the same thing where the Internal Edge Certificate was a single name public cert. The www name Thawte automatically put on the certificate also messed things up. This was solved, at least temporarily, but a CNAME that would redirect the www back to the correct location.

By: TraciSylvia

TraciSylvia — Wed, 09 Jun 2010 20:38:01 +0000

I was getting the same error. I actually opened a Microsoft ticket on this. My fix was changing my certificate. Originally I was using a GoDaddy single name cert. The problem is, with Godaddy, they put an extra SAN name on the cert that start with www. on all of their single name certs. I spoke to GoDaddy and they said they can not issue certs with out the extra www. SAN name on the certificate. This caused Group Chat Admin not to be able to login. If your certificate does have SAN names on it, the FQDN of the server needs to be at the bottom of the Subject Alternative Name list on your Certificate. I ended up using a certificate from www.namecheap.com because they dont add additional SANs on when all you buy is a single name cert.