Communities widget error messages

Home

Communities widget error messages

Use the codes included in the error messages generated by IBM Lotus Connections to identify problems with Communities widgets and find solutions. The following error messages are generated by Communities widgets:

Communities widget error messages

Message Cause Solution
CLFWZ0001E: Failed to initialize widget lifecycle event propagater. The widget life-cycle framework failed to initialize. Validate widgets-config.xml settings. Report this problem to Customer Support. Additional information relating to the failure may be found in the SystemOut.log file.
CLFWZ0002E: Failed to handle posted lifecycle event. An application that maintains widget data failed to process a change in the containing community. Examine the logs for further information. If no resolution is evident, report this problem to Customer Support.
CLFWZ0003E: Failed to post event notification to remote widget application handler: {0} Communities was unable to notify a remote application of a community change. Communities will automatically retry to send the event at a later time. Check log files for any blocking problems in the remote application.
CLFWZ0004E: Event '{0}' sent to remote lifecycle handler at {1} returned bad response: {2} Communities was unable to notify a remote application of a community change. Communities will automatically retry to send the event at a later time. Check log files for any blocking problems in the remote application.
CLFWZ0005E: Failed to propagate event to widget application handler: {0} Communities was unable to notify a remote application of a community change. Communities will automatically retry to send the event at a later time. Check log files for any blocking problems in the remote application.
CLFWZ0006E: Local widget application handler failed: {0} Communities was unable to notify discussion forums, bookmarks or feeds of a community change. Examine the logs for further information. If no resolution is evident, report this problem to Customer Support.
CLFWZ0011E: Failed to load widgets-config.xml: {0} The application was unable to read widgets-config.xml. Ensure the widgets-config.xml file exists in the LotusConnections-config directory, and ensure that it has the file permissions set so that the IBM WebSphere Application Server process can read it.
CLFWZ0012E: Failed to queue event for replay: {0} A remote application could not be notified of a change in a community. The widget framework could not write an event record for this change so that it can be replayed in the future. Report this problem to Customer Support. Additional information relating to the failure may be found in the SystemOut.log file.
CLFWZ0013E: Adding new {0} content is blocked until processing of prior content has completed for resource {1}. Try adding the content at a later time. A community owner tried to add a new widget to a community but the framework blocked the action because a prior widget of the same type has unprocessed life-cycle events. Process the life-cycle events for that community. For more information about processing the life-cycle events that occur within a community, see Administering community queued events. Once the queued events for that community have been processed or cleared, the new widget can be added.
CLFWZ0014E: The remote application {0} does not support being reassigned or transferred to another resource A wsadmin command for transferring a remote applications was run on a remote application that does not support that function. The transfer commands are only supported for the Blogs, Activities, Files, and Wikis remote applications.
CLFWZ0015E: No widget definition found with a definition id of '{0}' A wsadmin command was run with an invalid definition ID specified. Rerun the command with the correct definition ID - these IDs are case sensitive.
CLFWZ0016E: Can not assign to resource with id {0}. Resource already has its unique instance of {1}. A wsadmin command for transferring a remote application was run that would result in two unique widget instances contained in the same community. Choose a different community as the destination or delete the blocking unique instance widget.
CLFWZ0017E: Resource with id {0} was not found. A wsadmin command was run with an invalid community UUID specified. Rerun the command with the correct community UUID.
CLFWZ0018E: Widget with instance id {0} was not found. A wsadmin command was run with an invalid widget instance ID specified. Rerun the command with the correct widget instance ID.

Error codes

Related tasks

Administer community queued events

+
Search Tips | Advanced Search

Message	Cause	Solution
CLFWZ0001E: Failed to initialize widget lifecycle event propagater.	The widget life-cycle framework failed to initialize.	Validate widgets-config.xml settings. Report this problem to Customer Support. Additional information relating to the failure may be found in the SystemOut.log file.
CLFWZ0002E: Failed to handle posted lifecycle event.	An application that maintains widget data failed to process a change in the containing community.	Examine the logs for further information. If no resolution is evident, report this problem to Customer Support.
CLFWZ0003E: Failed to post event notification to remote widget application handler: {0}	Communities was unable to notify a remote application of a community change.	Communities will automatically retry to send the event at a later time. Check log files for any blocking problems in the remote application.
CLFWZ0004E: Event '{0}' sent to remote lifecycle handler at {1} returned bad response: {2}	Communities was unable to notify a remote application of a community change.	Communities will automatically retry to send the event at a later time. Check log files for any blocking problems in the remote application.
CLFWZ0005E: Failed to propagate event to widget application handler: {0}	Communities was unable to notify a remote application of a community change.	Communities will automatically retry to send the event at a later time. Check log files for any blocking problems in the remote application.
CLFWZ0006E: Local widget application handler failed: {0}	Communities was unable to notify discussion forums, bookmarks or feeds of a community change.	Examine the logs for further information. If no resolution is evident, report this problem to Customer Support.
CLFWZ0011E: Failed to load widgets-config.xml: {0}	The application was unable to read widgets-config.xml.	Ensure the widgets-config.xml file exists in the LotusConnections-config directory, and ensure that it has the file permissions set so that the IBM WebSphere Application Server process can read it.
CLFWZ0012E: Failed to queue event for replay: {0}	A remote application could not be notified of a change in a community. The widget framework could not write an event record for this change so that it can be replayed in the future.	Report this problem to Customer Support. Additional information relating to the failure may be found in the SystemOut.log file.
CLFWZ0013E: Adding new {0} content is blocked until processing of prior content has completed for resource {1}. Try adding the content at a later time.	A community owner tried to add a new widget to a community but the framework blocked the action because a prior widget of the same type has unprocessed life-cycle events.	Process the life-cycle events for that community. For more information about processing the life-cycle events that occur within a community, see Administering community queued events. Once the queued events for that community have been processed or cleared, the new widget can be added.
CLFWZ0014E: The remote application {0} does not support being reassigned or transferred to another resource	A wsadmin command for transferring a remote applications was run on a remote application that does not support that function.	The transfer commands are only supported for the Blogs, Activities, Files, and Wikis remote applications.
CLFWZ0015E: No widget definition found with a definition id of '{0}'	A wsadmin command was run with an invalid definition ID specified.	Rerun the command with the correct definition ID - these IDs are case sensitive.
CLFWZ0016E: Can not assign to resource with id {0}. Resource already has its unique instance of {1}.	A wsadmin command for transferring a remote application was run that would result in two unique widget instances contained in the same community.	Choose a different community as the destination or delete the blocking unique instance widget.
CLFWZ0017E: Resource with id {0} was not found.	A wsadmin command was run with an invalid community UUID specified.	Rerun the command with the correct community UUID.
CLFWZ0018E: Widget with instance id {0} was not found.	A wsadmin command was run with an invalid widget instance ID specified.	Rerun the command with the correct widget instance ID.