- The Office Communications Server 2007 R2 front-end servers for the pool are taken offline.
- The Office Communicator 2007 R2 users in the offline pool are moved to a secondary pool to make sure of their instant message and conferencing functionality.
Additionally, the automatic sign-in process for the Office Communicator 2007 R2 users who were moved to the secondary pool is slower than usual in any one of the following situations in Office Communicator 2007 R2:
- During an initial Office Communicator 2007 R2 automatic sign-in after the user is moved to the secondary Office Communications Server 2007 R2 pool
- During an Office Communicator 2007 R2 automatic sign-in after you exit the client application for an extended period.
- During an Office Communicator 2007 R2 automatic sign-in after you restart the Windows client-based computer on which the Office Communicator 2007 R2 client is installed.
The Office Communicator 2007 R2 client updates the user's EndpointConfiguration.cache file when the user signs out of the Office Communications Server 2007 R2 pool. If the sign-out process is interrupted, the EndpointConfiguration.cache file cannot be updated with the secondary Office Communications Server 2007 R2 pool’s FQDN and TCP port information. This causes the Office Communicator 2007 R2 client to do the following:
- Try to automatically sign in to the Office Communications Server 2007 R2 pool by using the legacy FQDN and TCP port information that is listed in the EndpointConfiguration.cache file
- Time out and not connect because the original Office Communications Server 2007 R2 pool front-end servers are offline
- Perform a DNS lookup for the SRV records that are configured for the automatic sign-in process
Fix it for me
To fix this problem automatically, click the Fix it button or link. In the File Download dialog box, click Run and then follow the steps in the Fix it Wizard.
- This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
- If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.
Then, go to the "Did this fix the problem?" section.
Let me fix it myselfTo resolve this issue, follow these steps:
- On the Windows-based client computer that is hosting Office Communicator 2007 R2, click Start, click Run, type taskmgr.exe in the Open box, and then click OK.
- In the Windows Task Manager dialog box, click the Processes tab.
- In the Image Name list, select communicator.exe, and then click End Process to end the communicator.exe process.
- Click Start, click Run, type %userprofile\Local Settings\Microsoft\Communicator\Sip_username@contoso.com, and then click OK.
- Locate and then delete the EndpointConfiguration.cache file in the Sip_username@contoso.com folder.
- Close Windows Explorer.
- Open the Office Communicator 2007 R2 client on the Windows client-based computer.
Did this fix the problem?
- Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support.
- We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me" blog or send us an email message.
Raksta ID: 2527360. Pēdējo reizi pārskatīts: 2011. gada 9. maijs. Pārskatījums: 1