Sign in to Communicator

This topic discusses how to sign in to Communicator 2007 automatically, how to change your sign-in account, and what to do if you are unable to sign in.

What do you want to do?

Start Communicator and sign in

Change your sign-in account

Troubleshoot sign-in

Start Communicator and sign in

Typically, Communicator 2007 is configured for you by your system administrator. However, the administrator may not have configured Communicator 2007 to start automatically when you log on to Windows, so this option is covered below.

To start Communicator automatically when you log on to Windows

  1. On the Windows desktop, click Start, point to All Programs, and then click Microsoft Office Communicator 2007.

  2. In the Office Communicator window, verify that your user name is correct, enter your password and then click Sign In.

  3. In the Office Communicator Title bar, click the Menu button.

  4. Click Tools, click Options, and if not already selected, select the Automatically start Communicator when I log on to Windows check box.

Top of Page

Change your sign-in account

  1. To change your sign-in account, you must first sign out of Communicator 2007. On the Office Communicator Title bar, click the Menu button, point to Connect, and then click Sign Out.

  2. In the Office Communicator Title bar, click the Menu button, point to Connect, and then click Change Sign-In Address.

  3. In the Options dialog box, under My account, specify a new account in the Sign-in address box, and then click OK.

  4. In the Office Communicator window, type the user name and password for the account, and then click Sign In.

Top of Page

Troubleshoot sign-in

When Communicator 2007 is first installed, it is usually configured for you your system administrator. However, it is possible that you might not be able to sign in. If you receive an error message while trying to sign in, you may want to consider the following troubleshooting steps before contacting your system administrator:

  • Verify your sign-in address, user name, and password.

  • Check advanced account settings, if appropriate.

  • View the Windows event log for detailed information about the error, and then provide that information to your administrator or technical support department.

To verify your account information

  1. In the Office Communicator window Title bar, click the Menu button, point to Tools, and then click Options.

  2. In the Options dialog box, on the Personal tab, under My account, verify that the information in the Sign-in address box is correct.

  3. If you need to configure Communicator manually, click the Advanced button. Verify that the Manual Configuration option is selected, check that the values for Internal server name or IP address, External server name or IP address, and Connect using are correct. Then click OK.

  4. Click OK to close the Options dialog box.

  5. In the Office Communicator main window, re-type your user name and password, and then click Sign In to try the connection again.

If you still cannot sign in, you can find out more about the error by using Communicator's Logging options.

Logging Options

Note   To enable logging, you must belong to the local Performance Log Users group. See "To join the Performance Log Users group" in Microsoft Office Communicator 2007 Deployment Guide, or ask your system administrator.

Office Communicator provides the following logging options that can help you troubleshoot sign-in problems with Communicator.

  • Turn on logging in Communicator     You can enable this option to create a log file, communicator-uccp-log.uccplog, that contains information about the interaction of Office Communicator 2007 with Office Communications Server 2007. The communicator-uccp-log.uccplog file is created in the Windows <user profile>\Tracing folder.

  • Turn on Windows Event Logging for Communicator     When this option is enabled, Communicator writes the following types of errors to the Windows system event log, along with detailed troubleshooting information:

    • Errors that prevent a user from logging on to the server, such as host or domain name errors, or an invalid certificate.

    • Diagnostic messages returned by the server, such as version check failures, problems with log-in credentials, or errors generated in response to a SIP INVITE message from the client.

    • Windows event trace log (ETL) files, which may also be generated on your computer in the <username>/Tracing folder, enable administrators and Microsoft support technicians troubleshoot problems. For more information, contact your Microsoft support representative.

To turn on Logging

  1. In the Communicator Title bar, click the Menu button, point to Tools, and then click Options.

  2. Click the General tab, and then under Options, select the Logging options that you want to enable.

To locate the Communicator log file

  • In Windows Explorer, navigate to the <user profile>\Tracing folder. If you have enabled the Turn on Logging in Communicator option, you will see a communicator-uccp-log.uccplog file in the folder. If you are already signed in, you will need to sign out and then sign back in before the log file is created.

To view the Windows Events Viewer

  1. Click Start, click Run, type eventvwr in the Open box, and then click OK.

  2. In the Event Viewer window, in the Console Tree pane on the left, do one of the following:

    • In Windows XP, click Application.

    • In Windows Vista, double-click Windows Logs, and then click Application.

  3. Double-click the most recent Communicator error in the list to display the error details.

  4. In the Event Properties dialog box, click the Copy button to copy the text of the error to the clipboard.

  5. Paste the error information into a text file or e-mail message, and then contact your system administrator or technical support department.

Top of Page

Applies To: Communicator 2007

Was this information helpful?

Yes No

How can we improve it?

255 characters remaining

To protect your privacy, please do not include contact information in your feedback. Review our privacy policy.

Thank you for your feedback!

Change language