Cisco Cisco MeetingPlace Gateway SIM Anleitung Für Quick Setup
Troubleshooting Cisco Unified MeetingPlace Web Conferencing
How to Resolve Failed Server Issues
7
Error Message: Read Failure in Named Pipe in Audio Service
Error Message Read Failure in Name Pipe in Audio Service.
Explanation
The Cisco Unified MeetingPlace Web Conferencing Service has lost its connection to
the Cisco Unified MeetingPlace Audio Service. This could be due to a manual restart or an error.
Recommended Action
Do nothing. The Web Conferencing Service will reconnect automatically; the
error message is for information only.
Web Conferencing Does Not Start After Moving Time on the Web Server
Problem
User moved the time backwards then forward on the Web Server. Now Web Conferencing does
not start.
Possible Cause
There may be bad “date_begin” values in the pps_acl_quotas table in the MPWEB
Slave database used by the Web Server (MPWEB_xxxxx). Those dates are initialized at the time
when Web Conferencing is installed so if the time was moved backwards, Web Conferencing will
refuse to work because it cannot find the proper “disk quota” permissions.
when Web Conferencing is installed so if the time was moved backwards, Web Conferencing will
refuse to work because it cannot find the proper “disk quota” permissions.
Solution
Manually change the “date_begin” values pps_acl_quotas table in the MPWEB Slave database
to some time in the past relative to the current system time.
Time is Not Synchronized Between the Web Server and the Application Server
Problem
Web Conferencing configures the Windows Time service on the Web Server to synchronize its
time with the Application Server. When the Cisco Unified MeetingPlace Web Conferencing master
service comes up, it should trigger a time synchronization with the Application Server. This is not
happening.
service comes up, it should trigger a time synchronization with the Application Server. This is not
happening.
Solution
Complete the following workaround.
Step 1
Stop the Cisco Unified MeetingPlace Web Conferencing master service.
Step 2
Look at the time on both the Application Server and the Web Server and try to adjust the clock on the
Web Server to match the time on the Application Server within 30 seconds.
Web Server to match the time on the Application Server within 30 seconds.
Step 3
Invoke the Windows Time Service to synchronize between the Web Server and the Application Server:
a.
Open a DOS command window.
b.
Enter the following command: w32tm/resync
c.
Enter the following command to see if the time is now within 30 seconds: w32tm /monitor
/computer:hostname_AppServer
/computer:hostname_AppServer