Error on JMS connection: Error retrieving JNDI context:

JNDI setup failed on RNAME

The JNDI server cannot be reached or the URL specified in the associated JNDI alias is incorrect

Check if the URL in the associated JNDI alias is correct. If you are using a Universal Messaging cluster, ensure that the JNDI alias specifies all cluster nodes, either in the JNDI provider URL, or in the JNDI failover list

Error on JMS connection: Error creating connection factory:

Internal lookup failed for name

ConnectionFactory not found in JNDI or lookup name in JMS alias is incorrect

Check if the given JNDI provider URL in the JNDI alias is correct. Check in the JNDI context on the specific server if a ConnectionFactory exists with the lookup name specified in the JMS alias. If using a Universal Messaging cluster, check that the channel naming/defaultContext is clustered correctly

Error on JMS connection: Error creating connection:

URL in ConnectionFactory cannot be reached

Check if the URL provided in the ConnectionFactory is reachable from the Integration Server machine. If Integration Server is on a different machine from where Universal Messaging is installed, ensure that the ConnectionFactory URL does not include localhost

Error on JMS connection: Error retrieving JNDI context:

Client does not have the required permissions

Check if the Integration Server client has Access rights in the Universal Messaging server ACL and Subscribe rights in the naming/defaultContext channel ACL

Error on webMethods Messaging connection: Error initializing Universal Messaging session:

URL in webMethods Messaging alias cannot be reached

Check if the Universal Messaging URL in the webMethods Messaging alias is correct and is reachable from Integration Server

Error enabling JMS trigger or sending JMS message:

Channel could not be found on the server

JNDI destination exists, but channel does not exist

Check that the URL in the ConnectionFactory used by the JMS alias refers to the same Universal Messaging server. If using a Universal Messaging cluster, check if the relevant topic is correctly clustered and available on all cluster nodes

Error enabling webMethods messaging trigger or publishing a webMethods messaging message:

Channel could not be found on the server

Channel does not exist

Synchronize the Integration Server document type with the Provider using Designer

Messages are not being delivered, or other error messages in a cluster

Cluster not configured correctly

Check if the Universal Messaging servers are correctly clustered. Check if the naming/defaultContext channels are correctly clustered. Check if the channels and queues are correctly clustered

If correctly clustered, the relevant icons appear orange in Enterprise Manager

Check if a valid Universal Messaging cluster URL is configured in: