[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5170
  • Last Modified:

UNABLE TO LOG INTO OFFICE COMMUNICATOR CLIENT

We intend to deploy Live Communication Server in our enterprise network.  I tried this in a lab enviroment, using a Windows 2003 SP2 DC as the DNS server as well, i have another Windows 2003 SP2 as the LCS server with  Live communication server 2005 Standard Edition installed . the activation was successfully.

i had another machine running windows XP2 as the client on which i installed windows office communicator 2005 with the hotfix package updated. i configured this after enabling a user in the LCS server successfuly and configuring the SIP as well. I did all this successfuly though its my first experience with this, but i followed the deployment guide step by step and all the checks at each stage was ok.

However i couldnt login any of the 2 users i had sip enabled on the lcs server on the communicator, the error message is  always "cannot sign in to communications service because the server is temporarily unavailable. please try again later. if the problem persists, contact your system administrator."      i had tried all i could to no avail. i need help urgently as i have a deadline to deliver on this.





Live Communications Server 2005 Deployment Log
 
 
Time Logged: Thursday, July 19, 2007 9:25:45 AM
 

Action  Action Information  Execution Result  

Execute Action       Success
 

Check Domain Prep State   FQDN: CONTOSO.COM
Accounts: Ready
Domain Root Permissions: Ready
Microsoft Container Permissions: Ready
System Container Read Permissions: Ready
Users Container Read Permissions: Ready
Domain Controllers Container Read Permissions: Ready
Computers Container Read Permissions: Ready
Schema Container Read Permissions: Ready
Configuration Container Read Permissions: Ready
Display Specifiers Container Read Permissions: Ready
   Success
 

Check Forest Prep State   FQDN: CONTOSO.COM
Microsoft Container: Ready
Service Connection Point: Ready
Global Settings: Ready
Domain Data: Ready
LCS Property Set: Ready
LCS User Search Property Set: Ready
LCS Display Specifiers: Ready
Pools Container: Ready
   Success
 

Server Domain State   Domain Member: True
User Has Domain Access Rights: True
Domain Admin: True
Domain Prep State: Ready
Domain Added to Root: Ready
   Success
 

Activate   Activation Server Role: LCS 2005 Standard Edition Server
Activation Service Account: LCService
Start Service After Activation: True
Unregister Existing SPN's During Activation: True
Local Computer Primary DNS Suffix: Ready
   Success
 

Check Server State   Server FQDN: HQ-CON-LCS-01.CONTOSO.COM
Server Name: HQ-CON-LCS-01
LCS Service Account: LocalSystem
Domain Account: False
Local Computer Primary DNS Suffix: Ready
Server Role: Not Assigned
   Success
 

Existing Server State   Event Logging Enabled: True
Domain Member: True
Server Installation Role: LCS 2005 Standard Edition Server
LCS Service Installed: True
LCS Service Enabled: False
Microsoft Container: Not Ready
Microsoft Container Permissions: Not Ready
Trusted Server Entry: Not Ready
Server Object: Not Ready
Enterprise Service: False
Home Users: None
Pool Associated: False
IM Archiving Agent WMI Instance: False
IM Archiving Agent Permissions: False
DCOM Permissions: Not Ready
DCOM Machine Restrictions: Not Ready
   Success
 

Activate Standard Edition Server   Server Role: LCS 2005 Standard Edition Server
   Success
 

Create Microsoft Container       Success
 

Create Microsoft Container Permissions       Success
 

Create Server Object       Success
 

Create Standard Edition Server Pool   Pool FQDN: HQ-CON-LCS-01.CONTOSO.COM
Pool Distinguished Name: CN=HQ-CON-LCS-01,CN=Pools,CN=RTC Service,CN=Microsoft,CN=System,DC=CONTOSO,DC=COM
   Success
 

Check Pools Container   Service Connection Point: Ready
Pools Container: Ready
   Success
 

Check Pool State   Pool Name: HQ-CON-LCS-01
Active Directory Pool Object: Ready
Pool Backend: (local)\rtc
Pool FQDN: HQ-CON-LCS-01.CONTOSO.COM
Pool Type: LCS 2005 Standard Edition Pool
Pool Major Version: 0x00000002
Pool Minor Version: 0x00000001
Pool Service Connection Point: Ready
   Success
 

Validate Pool FQDN DNS registration   Pool FQDN: HQ-CON-LCS-01.CONTOSO.COM
DNS Record Count: 0x00000001
   Success
 

Associate Server With Pool       Success
 

Create Trusted Server Entry       Success
 

Activate Service       Success
 

Create Domain Service Account       Success
 

Grant Logon As Service Right   LCS Service Account: CONTOSO\LCService
   Success
 

Register SPN   User With SPN: CN=LCService,CN=Users,DC=CONTOSO,DC=COM
SPN: Ready
   Success
 

Create Local Group Memberships       Success
 

Create DCOM Permissions       Success
 

Create DCOM Machine Restrictions       Success
 

Enable Service       Success
 

Stop Service   Stop Duration: 10
   Success
 

Start Service   Startup Duration: 1292
   Success
 

Activated Server State   Event Logging Enabled: True
Domain Member: True
Server Installation Role: LCS 2005 Standard Edition Server
LCS Service Installed: True
LCS Service Enabled: True
Microsoft Container: Ready
Microsoft Container Permissions: Ready
Trusted Server Entry: Ready
Server Object: Ready
Enterprise Service: True
Home Users: None
Pool Associated: True
Pool Distinguished Name: CN=HQ-CON-LCS-01,CN=Pools,CN=RTC Service,CN=Microsoft,CN=System,DC=CONTOSO,DC=COM
Pool Type: LCS 2005 Standard Edition Server
IM Archiving Agent WMI Instance: False
IM Archiving Agent Permissions: False
DCOM Permissions: Ready
DCOM Machine Restrictions: Ready
   Success
 
0
adeseye_odunsi
Asked:
adeseye_odunsi
  • 5
  • 4
1 Solution
 
kinetik20Commented:
Are you sure your typing the login details correctly for the users?

There is 3 login details that need to be filled out. An example is below.

Sign-In Name: sip:user@domainname.local (this is a setting under actions, options in the communicator)
Username: user@domainname.local
password: userpassword

Hope this helps.
0
 
adeseye_odunsiAuthor Commented:
Kinetic20 thanks for your response:

 I didnt add the sip:user@domainname.local, i have only user@domain.local as the Sign-In Name. i did not even have option to input username and password. why is this so? I added sip: to the sign-in name but the error remains the same.

I built another windows 2003 virtual server, which is a DC, as well as a DNS, i installed LCS 2005 Standard edition on the same server, and also installed communicator on the same machine (i did this again in order to see if there is something i have done wrong in the initial installation). This is holding all possible roles of an LCS environment, and all installation  were successful the logs did not give any error. On the communicator, there was a provision for username and password, apart from the sign in name, which i also added SIP: but the error in login is same as the earlier one on the Windows XP2 in the other separate domain. kindly help further.
0
 
kinetik20Commented:
Within Communicator itself are you clicking actions, then options and type the sip:user@domain.local?

the user name will only be user@domain.locl
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
adeseye_odunsiAuthor Commented:
thats actually what i did initially, i only added it after your first post, i had removed the sip: with the results still being the same.
0
 
kinetik20Commented:
Try this. Inside communicator click actions, then options. Make sure that the account is set to

sip:user@domain.local

Then select advanced. Now manually set the Live Communications servers IP address.

0
 
adeseye_odunsiAuthor Commented:
i had tried this beforehand as well. its  not working.I NEED HELP PLEASE.
0
 
kinetik20Commented:
Are their any firewalls on the clients? That may be the issue. You may need to allow access to the Communicator in the firewall.
0
 
kinetik20Commented:
Also you may want to try to uninstall the Communicator all together and reinstall it.
0
 
adeseye_odunsiAuthor Commented:
thanks so much for you clues, they helped in improving my knowhow of the lcs which am trying out for the first time. i eventually got around to find out what the problem  is. i wish to place on record though that the clue came from my search through past issues that had been discussed on Expert Exchange. my sip uri was different from the LCS server domain, i eventually got around to add the sip uri to the LCS server snap in console and this resolves the problem.
0
 
mkrbCommented:
Worked for me also, the SIP URI was a .co.uk, where as the server domain was .net (as i use both). Changed sip uri to .net and all working, cheers
0

Featured Post

Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now