Lotus Connections events service error messages

Home

Lotus Connections events service error messages

Use the codes included in the error messages generated by IBM Lotus Connections to identify problems related to the events service of the Home page feature and find solutions to those problems. The following events service error messages are generated by Lotus Connections:

Lotus Connections events service error messages

Message Cause Solution
CLFWY0001E: The Source field was null or empty when creating a new event record. The Source field must contain a valid value. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
CLFWY0005E: An attempt was made to register a null event consumer for the Source {0} This is an internal error. Contact IBM Support.
CLFWY0006E: The Event Name field was null or empty when creating a new event record. The Event Name field must contain a value. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
CLFWY0007E: An invalid JSON string was provided This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
CLFWY0008E: The Source field value {0} is not a known, valid source. The event record cannot be created. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
CLFWY0009E: The ACL Feed URL field was null or empty when creating a new event record. The ACL Feed URL field must contain a value. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
CLFWY0011E: The Event Name field was null or empty when sending an event record for source {0}. The Event Name field must be supplied before the event is sent! This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
CLFWY0014E: The Container ID field was null or empty when creating a new event record. The Container ID field must contain a value. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
CLFWY0015E: The input set to add to was provided as null.. A valid set must be provided. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
CLFWY0017E: The Source field was null or empty when registering a new event record consumer. Events will not be sent to the consumer. This is an internal error. Contact IBM Support.
CLFWY0019E: The following class could not be instantiated as an event transport: {0} but was specified as the default transport. Events cannot be propagated to the News Repository. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
CLFWY0020E: The following class is not a valid event transport: {0} but was specified as the default transport. Events cannot be propagated to the News Repository. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
CLFWY0022E: A JMS Exception occurred when consuming an event record. The event record will be retried and eventually be placed on the system exception queue if unsuccessful. An event could not be consumed from the JMS queue used by the event infrastructure. This will result in news stories not displaying in Home Page in some circumstances. Check the configuration of JMS resources in WebSphere®. Also check that the Service Integration Bus is configured to allow access to the user defined in the connectionsAdmin authentication alias. The nested exception provides more details.
CLFWY0024E: JMS QueueConnectionFactory for sending the ACL event record with ID {0} from source {1} were not available. QueueConnectionFactory may not be defined. JMS resources required by the event infrastructure could not be looked up. This will result in news stories not displaying in Home Page in some circumstances. Check the Lotus Connections installer log for any errors during install. Also check the WebSphere JMS Resources to check if any QueueConnectionFactory objects are defined. If not, the installer failed to create them. Attempt a re-install or contact IBM Support.
CLFWY0025E: JMS QueueConnectionFactory for sending the event record with ID {0} from source {1} were not available. QueueConnectionFactory may not be defined. JMS resources required by the event infrastructure could not be looked up. This will result in news stories not displaying in Home Page in some circumstances. Check the Lotus Connections installer log for any errors during install. Also check the WebSphere JMS Resources to check if any QueueConnectionFactory objects are defined. If not, the installer failed to create them. Attempt a re-install or contact IBM Support.
CLFWY0026E: A JMS exception occurred when attempting to sent the event record ID {0} from source {1}. Check the nested exception for more details. An event could not be propagated onto the JMS queue used by the event infrastructure. This will result in news stories not displaying in Home Page in some circumstances. Check the configuration of JMS resources in WebSphere. Also check that the Service Integration Bus is configured to allow access to the user defined in the connectionsAdmin authentication alias. The nested exception provides more details.
CLFWY0027E: A JMS exception occurred when attempting to sent the ACL event record ID {0} from source {1}. Check the nested exception for more details. An event could not be propagated onto the JMS queue used by the event infrastructure. This will result in news stories not displaying in Home Page in some circumstances. Check the configuration of JMS resources in WebSphere. Also check that the Service Integration Bus is configured to allow access to the user defined in the connectionsAdmin authentication alias. The nested exception provides more details.
CLFWY0028E: An EJB instance for the Event Record Transport implementation could not be created. Check nested exception for more details. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Check the nested exception for any details, and resolve any obvious configuration issue. Contact IBM Support.
CLFWY0029E: The EJB Home for the Event Record Transport implementation could not be looked up. Check nested exception for more details. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Check the nested exception for any details, and resolve any obvious configuration issue. Contact IBM Support.
CLFWY0030E: An error occurred when creating a JMS message due to an invalid session. The event will not be sent. Restarting the application may resolve this issue. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. This error may happen due to temporary configuration of infrastructure reasons. Restart the application. If this error persists or requires regular restarts, contact IBM support.
CLFWY0031E: An unexpected implementation class for an ACL event record was received. The event will not be sent. The class was {0} This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
CLFWY0032E: A JMS message could not be created for the event record ID {0} from source {1}. The event will not be sent. Check the nested exception for more details. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
CLFWY0033E: An unexpected implementation class for an event record was received. The event will not be sent. The class was {0} This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
CLFWY0037E: An error occurred while fetching the News Repository EJB. Check the logs for more details. The News Repository EJB could not be looked up. This will result in news stories not displaying on the Home Page updates page. The nested exception will contain exact details of the error. Refer to the error message for the nested exception.
CLFWY0038E: Impossible to get the bootstrap and port information for the remote EJB from LotusConnections-Config.xml The LotusConnections-config.xml file could not be read to obtain the bootstrapHost and bootstrapPort values for the News service. Validate that LotusConnections-config.xml is correct and that the bootstrapHost defined for the News service points to the application server running News, and that the bootstrapPort points to the correct Bootstrap Port for that server. Fix the file and restart the application.
CLFWY0039E: The JMS QueueConnectionFactory or Queue could not be looked up. Check the QCF and Queue is defined in WebSphere and bound to the application. Check the nested exception for more details. JMS resources required by the event infrastructure could not be looked up. This will result in news stories not displaying in Home Page in some circumstances. Check the Lotus Connections installer log for any errors during install. Also check the WebSphere JMS Resources to check if any QueueConnectionFactory and Queue objects are defined. If not, the installer failed to create them. Attempt a re-install or contact IBM Support.

Error codes

+
Search Tips | Advanced Search

Message	Cause	Solution
CLFWY0001E: The Source field was null or empty when creating a new event record. The Source field must contain a valid value.	This is an internal error. This will result in news stories not displaying in Home Page in some circumstances.	Contact IBM Support.
CLFWY0005E: An attempt was made to register a null event consumer for the Source {0}	This is an internal error.	Contact IBM Support.
CLFWY0006E: The Event Name field was null or empty when creating a new event record. The Event Name field must contain a value.	This is an internal error. This will result in news stories not displaying in Home Page in some circumstances.	Contact IBM Support.
CLFWY0007E: An invalid JSON string was provided	This is an internal error. This will result in news stories not displaying in Home Page in some circumstances.	Contact IBM Support.
CLFWY0008E: The Source field value {0} is not a known, valid source. The event record cannot be created.	This is an internal error. This will result in news stories not displaying in Home Page in some circumstances.	Contact IBM Support.
CLFWY0009E: The ACL Feed URL field was null or empty when creating a new event record. The ACL Feed URL field must contain a value.	This is an internal error. This will result in news stories not displaying in Home Page in some circumstances.	Contact IBM Support.
CLFWY0011E: The Event Name field was null or empty when sending an event record for source {0}. The Event Name field must be supplied before the event is sent!	This is an internal error. This will result in news stories not displaying in Home Page in some circumstances.	Contact IBM Support.
CLFWY0014E: The Container ID field was null or empty when creating a new event record. The Container ID field must contain a value.	This is an internal error. This will result in news stories not displaying in Home Page in some circumstances.	Contact IBM Support.
CLFWY0015E: The input set to add to was provided as null.. A valid set must be provided.	This is an internal error. This will result in news stories not displaying in Home Page in some circumstances.	Contact IBM Support.
CLFWY0017E: The Source field was null or empty when registering a new event record consumer. Events will not be sent to the consumer.	This is an internal error.	Contact IBM Support.
CLFWY0019E: The following class could not be instantiated as an event transport: {0} but was specified as the default transport. Events cannot be propagated to the News Repository.	This is an internal error. This will result in news stories not displaying in Home Page in some circumstances.	Contact IBM Support.
CLFWY0020E: The following class is not a valid event transport: {0} but was specified as the default transport. Events cannot be propagated to the News Repository.	This is an internal error. This will result in news stories not displaying in Home Page in some circumstances.	Contact IBM Support.
CLFWY0022E: A JMS Exception occurred when consuming an event record. The event record will be retried and eventually be placed on the system exception queue if unsuccessful.	An event could not be consumed from the JMS queue used by the event infrastructure. This will result in news stories not displaying in Home Page in some circumstances.	Check the configuration of JMS resources in WebSphere®. Also check that the Service Integration Bus is configured to allow access to the user defined in the connectionsAdmin authentication alias. The nested exception provides more details.
CLFWY0024E: JMS QueueConnectionFactory for sending the ACL event record with ID {0} from source {1} were not available. QueueConnectionFactory may not be defined.	JMS resources required by the event infrastructure could not be looked up. This will result in news stories not displaying in Home Page in some circumstances.	Check the Lotus Connections installer log for any errors during install. Also check the WebSphere JMS Resources to check if any QueueConnectionFactory objects are defined. If not, the installer failed to create them. Attempt a re-install or contact IBM Support.
CLFWY0025E: JMS QueueConnectionFactory for sending the event record with ID {0} from source {1} were not available. QueueConnectionFactory may not be defined.	JMS resources required by the event infrastructure could not be looked up. This will result in news stories not displaying in Home Page in some circumstances.	Check the Lotus Connections installer log for any errors during install. Also check the WebSphere JMS Resources to check if any QueueConnectionFactory objects are defined. If not, the installer failed to create them. Attempt a re-install or contact IBM Support.
CLFWY0026E: A JMS exception occurred when attempting to sent the event record ID {0} from source {1}. Check the nested exception for more details.	An event could not be propagated onto the JMS queue used by the event infrastructure. This will result in news stories not displaying in Home Page in some circumstances.	Check the configuration of JMS resources in WebSphere. Also check that the Service Integration Bus is configured to allow access to the user defined in the connectionsAdmin authentication alias. The nested exception provides more details.
CLFWY0027E: A JMS exception occurred when attempting to sent the ACL event record ID {0} from source {1}. Check the nested exception for more details.	An event could not be propagated onto the JMS queue used by the event infrastructure. This will result in news stories not displaying in Home Page in some circumstances.	Check the configuration of JMS resources in WebSphere. Also check that the Service Integration Bus is configured to allow access to the user defined in the connectionsAdmin authentication alias. The nested exception provides more details.
CLFWY0028E: An EJB instance for the Event Record Transport implementation could not be created. Check nested exception for more details.	This is an internal error. This will result in news stories not displaying in Home Page in some circumstances.	Check the nested exception for any details, and resolve any obvious configuration issue. Contact IBM Support.
CLFWY0029E: The EJB Home for the Event Record Transport implementation could not be looked up. Check nested exception for more details.	This is an internal error. This will result in news stories not displaying in Home Page in some circumstances.	Check the nested exception for any details, and resolve any obvious configuration issue. Contact IBM Support.
CLFWY0030E: An error occurred when creating a JMS message due to an invalid session. The event will not be sent. Restarting the application may resolve this issue.	This is an internal error. This will result in news stories not displaying in Home Page in some circumstances.	This error may happen due to temporary configuration of infrastructure reasons. Restart the application. If this error persists or requires regular restarts, contact IBM support.
CLFWY0031E: An unexpected implementation class for an ACL event record was received. The event will not be sent. The class was {0}	This is an internal error. This will result in news stories not displaying in Home Page in some circumstances.	Contact IBM Support.
CLFWY0032E: A JMS message could not be created for the event record ID {0} from source {1}. The event will not be sent. Check the nested exception for more details.	This is an internal error. This will result in news stories not displaying in Home Page in some circumstances.	Contact IBM Support.
CLFWY0033E: An unexpected implementation class for an event record was received. The event will not be sent. The class was {0}	This is an internal error. This will result in news stories not displaying in Home Page in some circumstances.	Contact IBM Support.
CLFWY0037E: An error occurred while fetching the News Repository EJB. Check the logs for more details.	The News Repository EJB could not be looked up. This will result in news stories not displaying on the Home Page updates page.	The nested exception will contain exact details of the error. Refer to the error message for the nested exception.
CLFWY0038E: Impossible to get the bootstrap and port information for the remote EJB from LotusConnections-Config.xml	The LotusConnections-config.xml file could not be read to obtain the bootstrapHost and bootstrapPort values for the News service.	Validate that LotusConnections-config.xml is correct and that the bootstrapHost defined for the News service points to the application server running News, and that the bootstrapPort points to the correct Bootstrap Port for that server. Fix the file and restart the application.
CLFWY0039E: The JMS QueueConnectionFactory or Queue could not be looked up. Check the QCF and Queue is defined in WebSphere and bound to the application. Check the nested exception for more details.	JMS resources required by the event infrastructure could not be looked up. This will result in news stories not displaying in Home Page in some circumstances.	Check the Lotus Connections installer log for any errors during install. Also check the WebSphere JMS Resources to check if any QueueConnectionFactory and Queue objects are defined. If not, the installer failed to create them. Attempt a re-install or contact IBM Support.