Cisco Unified MeetingPlace, Release 6.x -- Troubleshooting Cisco Unified MeetingPlace for Office Communicator - Revision history

Jmcmulle at 19:02, 25 June 2009

2009-06-25T19:02:20Z

← Older revision		Revision as of 19:02, 25 June 2009
Line 141:		Line 141:

	'''Error Message: ''' <tt>The Cisco Unified MeetingPlace LCS Gateway Service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts services. </tt>		'''Error Message: ''' <tt>The Cisco Unified MeetingPlace LCS Gateway Service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts services. </tt>
-

	'''Explanation: ''' You did not enter an IP address during the installation or configuration.		'''Explanation: ''' You did not enter an IP address during the installation or configuration.
-

	'''Recommended Action: ''' Enter a valid IP address.		'''Recommended Action: ''' Enter a valid IP address.

	See [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace for Office Communicator#Configuring Cisco Unified MeetingPlace LCS Gateway Parameters\|Configuring Cisco Unified MeetingPlace LCS Gateway Parameters]] for more information.		See [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace for Office Communicator#Configuring Cisco Unified MeetingPlace LCS Gateway Parameters\|Configuring Cisco Unified MeetingPlace LCS Gateway Parameters]] for more information.

Jmcmulle at 19:02, 25 June 2009

2009-06-25T19:02:01Z

← Older revision		Revision as of 19:02, 25 June 2009
Line 148:		Line 148:
	'''Recommended Action: ''' Enter a valid IP address.		'''Recommended Action: ''' Enter a valid IP address.

-	See [[Cisco Unified MeetingPlace, Release 6.x --Configuring Cisco Unified MeetingPlace for Office Communicator#Configuring Cisco Unified MeetingPlace LCS Gateway Parameters\|Configuring Cisco Unified MeetingPlace LCS Gateway Parameters]] for more information.	+	See [[Cisco Unified MeetingPlace, Release 6.x -- Configuring Cisco Unified MeetingPlace for Office Communicator#Configuring Cisco Unified MeetingPlace LCS Gateway Parameters\|Configuring Cisco Unified MeetingPlace LCS Gateway Parameters]] for more information.

Jmcmulle at 19:01, 25 June 2009

2009-06-25T19:01:41Z

← Older revision		Revision as of 19:01, 25 June 2009
Line 137:		Line 137:

	=== Troubleshooting Installation and Configuration Problems ===		=== Troubleshooting Installation and Configuration Problems ===
		+
		+

	'''Error Message: ''' <tt>The Cisco Unified MeetingPlace LCS Gateway Service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts services. </tt>		'''Error Message: ''' <tt>The Cisco Unified MeetingPlace LCS Gateway Service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts services. </tt>
		+

	'''Explanation: ''' You did not enter an IP address during the installation or configuration.		'''Explanation: ''' You did not enter an IP address during the installation or configuration.
		+

	'''Recommended Action: ''' Enter a valid IP address.		'''Recommended Action: ''' Enter a valid IP address.
		+
		+	See [[Cisco Unified MeetingPlace, Release 6.x --Configuring Cisco Unified MeetingPlace for Office Communicator#Configuring Cisco Unified MeetingPlace LCS Gateway Parameters\|Configuring Cisco Unified MeetingPlace LCS Gateway Parameters]] for more information.

Jmcmulle at 18:59, 25 June 2009

2009-06-25T18:59:59Z

← Older revision		Revision as of 18:59, 25 June 2009
Line 138:		Line 138:
	=== Troubleshooting Installation and Configuration Problems ===		=== Troubleshooting Installation and Configuration Problems ===

-	'''Error Message: ''' The Cisco Unified MeetingPlace LCS Gateway Service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts services.	+	'''Error Message: ''' <tt>The Cisco Unified MeetingPlace LCS Gateway Service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts services. </tt>

	'''Explanation: ''' You did not enter an IP address during the installation or configuration.		'''Explanation: ''' You did not enter an IP address during the installation or configuration.

	'''Recommended Action: ''' Enter a valid IP address.		'''Recommended Action: ''' Enter a valid IP address.

Jmcmulle: added a section about install and config error message

2009-06-25T18:59:17Z

added a section about install and config error message

← Older revision		Revision as of 18:59, 25 June 2009
Line 133:		Line 133:
	## Verify that the base DN is correct.		## Verify that the base DN is correct.
	# To do additional LDAP troubleshooting, download a light-weight LDAP browser from the Internet, and use it to log on to the Active Directory server to verify the administrative account container and base DN settings.		# To do additional LDAP troubleshooting, download a light-weight LDAP browser from the Internet, and use it to log on to the Active Directory server to verify the administrative account container and base DN settings.
		+
		+
		+
		+	=== Troubleshooting Installation and Configuration Problems ===
		+
		+	'''Error Message: ''' The Cisco Unified MeetingPlace LCS Gateway Service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts services.
		+
		+	'''Explanation: ''' You did not enter an IP address during the installation or configuration.
		+
		+	'''Recommended Action: ''' Enter a valid IP address.

MeetingPlace Express Moderator at 21:45, 16 June 2009

2009-06-16T21:45:27Z

← Older revision		Revision as of 21:45, 16 June 2009
Line 4:		Line 4:


-
-	~~This chapter contains the following sections:~~
-	* [[Cisco Unified MeetingPlace, Release 6.x -- Troubleshooting Cisco Unified MeetingPlace for Office Communicator#Configuring Logging\|Configuring Logging]]
-	* [[Cisco Unified MeetingPlace, Release 6.x -- Troubleshooting Cisco Unified MeetingPlace for Office Communicator#Tracking a Conference in the Logs\|Tracking a Conference in the Logs]]
-	* [[Cisco Unified MeetingPlace, Release 6.x -- Troubleshooting Cisco Unified MeetingPlace for Office Communicator#Troubleshooting Cisco Unified MeetingPlace LCS Gateway Startup Problems\|Troubleshooting Cisco Unified MeetingPlace LCS Gateway Startup Problems]]
-	* [[Cisco Unified MeetingPlace, Release 6.x -- Troubleshooting Cisco Unified MeetingPlace for Office Communicator#Troubleshooting Office Communicator Error Messages\|Troubleshooting Office Communicator Error Messages]]
-	* [[Cisco Unified MeetingPlace, Release 6.x -- Troubleshooting Cisco Unified MeetingPlace for Office Communicator#Troubleshooting User Authentication Problems\|Troubleshooting User Authentication Problems]]

MeetingPlace Moderator at 00:15, 31 January 2008

2008-01-31T00:15:02Z

← Older revision		Revision as of 00:15, 31 January 2008
Line 63:		Line 63:

	'''Recommended Action''' Enter the correct IP address.		'''Recommended Action''' Enter the correct IP address.
		+

MeetingPlace Moderator at 00:14, 31 January 2008

2008-01-31T00:14:34Z

← Older revision		Revision as of 00:14, 31 January 2008
Line 57:		Line 57:


-	If the Cisco Unified MeetingPlace LCS Gateway service fails to start, check the Gateway Systems Integrity Manager (Gateway SIM) log to see if the LCS Event Receiver Add-In has been loaded into the Cisco Unified MeetingPlace Web Conferencing service.	+
		+	'''Error Message''' <tt> Service cannot be started...The requested address is not valid in its context. </tt>
		+
		+	'''Explanation''' You entered the wrong listening IP address on the LCS Gateway tab in the Cisco Unified MeetingPlace gateway configurations utility.
		+
		+	'''Recommended Action''' Enter the correct IP address.
		+
		+
		+
		+	'''Problem''' If the Cisco Unified MeetingPlace LCS Gateway service fails to start, check the Gateway Systems Integrity Manager (Gateway SIM) log to see if the LCS Event Receiver Add-In has been loaded into the Cisco Unified MeetingPlace Web Conferencing service.


	If the system has not loaded the LCS Event Receiver Add-In, users cannot use DTMF controls in meetings. (For example, #5 for muting and unmuting, #41 for locking or unlocking a meeting, etc.)		If the system has not loaded the LCS Event Receiver Add-In, users cannot use DTMF controls in meetings. (For example, #5 for muting and unmuting, #41 for locking or unlocking a meeting, etc.)
		+
		+
		+	'''Solution''' Check the LCS Event Receiver Add-In status:

MeetingPlace Moderator at 00:06, 31 January 2008

2008-01-31T00:06:07Z

← Older revision		Revision as of 00:06, 31 January 2008
Line 38:		Line 38:
	## From the Windows Start menu, choose '''Settings''' > '''Control Panel''' > '''Administrative Tools''' > '''Services'''.		## From the Windows Start menu, choose '''Settings''' > '''Control Panel''' > '''Administrative Tools''' > '''Services'''.
	## Right-click '''Cisco Unified MeetingPlace LCS Gateway''' and click '''Stop'''.		## Right-click '''Cisco Unified MeetingPlace LCS Gateway''' and click '''Stop'''.
-	~~<!--the following two steps were removed per the RN:~~
-	~~## Right-click '''Cisco Unified MeetingPlace Web Conferencing''' and click '''Stop'''.~~
-	~~## Right-click '''Cisco Unified MeetingPlace Web Conferencing''' and click '''Start'''.-->~~
	## Right-click '''Cisco Unified MeetingPlace LCS Gateway''' and click '''Start'''.		## Right-click '''Cisco Unified MeetingPlace LCS Gateway''' and click '''Start'''.
	## Close the Services control panel.		## Close the Services control panel.
Line 74:		Line 71:
	#: <tt> Loaded ConferenceTechnologyProvider interface for "LCS MPEventBroker" </tt>		#: <tt> Loaded ConferenceTechnologyProvider interface for "LCS MPEventBroker" </tt>
	#: <tt> Load of "LCS MPEventBroker" add-In completed </tt>		#: <tt> Load of "LCS MPEventBroker" add-In completed </tt>
-	~~<!--the following were replaced by the above per RN~~
-	~~#: <tt> Load of "LCS MPEvent Receiver CTP Add-In" add-In completed </tt>~~
-	~~#: <tt> Conf Tech Provider "LCS MPEvent Receiver CTP Add-In" is active </tt> -->~~
	# If the entries are not found, stop the Cisco Unified MeetingPlace LCS Gateway service, restart the Cisco Unified MeetingPlace Web Conferencing service, and then start the Cisco Unified MeetingPlace LCS Gateway service:		# If the entries are not found, stop the Cisco Unified MeetingPlace LCS Gateway service, restart the Cisco Unified MeetingPlace Web Conferencing service, and then start the Cisco Unified MeetingPlace LCS Gateway service:
	## From the Windows Start menu, choose '''Settings''' > '''Control Panel''' > '''Administrative Tools''' > '''Services'''.		## From the Windows Start menu, choose '''Settings''' > '''Control Panel''' > '''Administrative Tools''' > '''Services'''.

MeetingPlace Moderator at 00:05, 31 January 2008

2008-01-31T00:05:28Z

← Older revision		Revision as of 00:05, 31 January 2008
Line 53:		Line 53:


-	For troubleshooting purposes, the LCS Conference ID and Cisco Unified MeetingPlace meeting ID are both logged ~~during~~ meeting ~~creation~~. When the ~~Office Communicator~~ user ends the conference, the tie between these two IDs ~~is removed~~. If the MOC user initiates another conference, the same LCS Conference ID ~~will be used~~, but it ~~will be~~ mapped to a new Cisco Unified MeetingPlace meeting ID.	+	For troubleshooting purposes, the LCS Conference ID and Cisco Unified MeetingPlace meeting ID are both logged in the Gateway Systems Integrity Manager (Gateway SIM) log when the meeting is created. When the MOC user ends the conference, the system removes the tie between these two IDs. If the MOC user initiates another conference, the system uses the same LCS Conference ID, but it is mapped to a new Cisco Unified MeetingPlace meeting ID. If the MOC user has the "Use reservationless" parameter set to yes in the user profile, the system sets the MOC-initiated meeting ID to the user's profile ID (phone number). Otherwise, the system randomly generates the meeting ID.