Cisco Cisco Unified MeetingPlace for Microsoft Outlook Manuale Di Manutenzione
108
Chapter 8 Troubleshooting
MeetingPlace for Outlook System Manager’s Guide
Latitude Communications
2. From this log you may observe the MeetingPlace for Outlook
components performing their assigned tasks. For fault
isolation purposes you may be required to forward this log
file to Latitude Customer Support.
isolation purposes you may be required to forward this log
file to Latitude Customer Support.
To generate a .txt file containing the log file:
1. Open a DOS command window and navigate to
<drive>\Latitude\MeetingPlace Gateway SIM
2. From the <drive>\Latitude\MeetingPlace Gateway SIM
prompt, type:
Eventlog >> Output.txt
The result is a text file called Output.txt in the
<drive>\Latitude\MeetingPlace Gateway SIM directory.
<drive>\Latitude\MeetingPlace Gateway SIM directory.
3. Send this file via e-mail to Latitude Customer Support.
Problems Installing MeetingPlace for Outlook
MeetingPlace for Outlook specifications dictate that the gateway
must log into the Exchange server on the domain and be granted
privilege to do so. Testing on Windows 2000 Advanced Server
has shown that the “MeetingPlace for Outlook Version 4” service
will not log into the Exchange server unless the gateway’s
account (specified during installation) is placed in the local
administrator’s group. Failing to do so will result in one of the
following error messages:
must log into the Exchange server on the domain and be granted
privilege to do so. Testing on Windows 2000 Advanced Server
has shown that the “MeetingPlace for Outlook Version 4” service
will not log into the Exchange server unless the gateway’s
account (specified during installation) is placed in the local
administrator’s group. Failing to do so will result in one of the
following error messages:
•
Could not start the MeetingPlace for Outlook Version 4
service on local computer. The service did not return an error.
This could be an internal Windows error or an internal
service error. If the problem persists, contact your system
administrator
service on local computer. The service did not return an error.
This could be an internal Windows error or an internal
service error. If the problem persists, contact your system
administrator
•
MAPI_E_NOT_FOUND
•
There are currently no logon servers available to service the
logon request
logon request