Currently have a SQL 2005 Server backend database, OCS Enterprise 2007 Server installed in consolidated mode, CA server.
Client machines login but have no option for password, which I presume is classed as "auto-logon".
I have carefully been through the "OCS_EnterpriseEditionDepl
oyment" Manual. I am at the point now where I need to log in via communicator but I get the following error:
"Cannot sign in because the server is temporarily unavailable"
I have run the validation server wizard, it completes but with failures. [I have included the logs for analysis.]
When I run "Validate Front End Server Configuration" under "Deploy Pool in a Consolidated Topology"
The "Validate Local Server Configuration", "Validate Connectivity" complete with warnings.
[Office Communications Server 2007 Deployment Log.pdf]
The "Validate SIP Logon", "Check this box to use client auto-logon for validation", "Validate IM Conference" are the ones that Complete with failures. [Office Communications Server 2007 Deployment Log-2.pdf]
The users are enabled and exist within the Users section of Office Communications Server console.
I have used ocstest1 and ocstest2 , both exist and have been enabled. Where you specify the User accounts to test the validation what is the correct syntax for the Account and User Name, as I have been putting the same for both. i.e. ocstest1@corp.quadratek.ne
t.
SQL server can see OCS 2007 server, clients can see both servers. All other OCS tasks have completed without failures except this one.
CA server has issued a certificate and it was installed successfully on the OCS Server.
I understand its difficult to fully diagnose without seeing the setup, I am hoping you can throw some ideas in for me to try.
Background: CSGW006V=SQL Server
CSGW016V=OCS Server 2007
ocs.corp.quadratek.net = pool name
DNS record been setup to point this pool name to the OCS Server.
Start Free Trial
