Failure Due to Missing .dll Files

The configuration process can fail with an error stating that the Event Collector component failed to start.

The error is similiar to the below:

05-16@18:50:30 ERROR (UserTaskProgressIndicator.java:67) - Application Deploy with Start failed
05-16@18:50:30 ERROR (UserTaskProgressIndicator.java:75) - Start component 'implementation.ec' failed : java.lang.IllegalStateException: com.tibco.n2.logging.exceptions.cec.N2LFComponentRegistrationError: {COMPONENT_REG_ERROR} - Error registering component [class com.tibco.n2.logging.metadata.n2lf.N2LFMetaData]!
05-16@18:50:30 ERROR (UserTaskProgressIndicator.java:85) - java.lang.IllegalStateException: com.tibco.n2.logging.exceptions.cec.N2LFComponentRegistrationError: {COMPONENT_REG_ERROR} - Error registering component [class com.tibco.n2.logging.metadata.n2lf.N2LFMetaData]!

The Event Collector is the first component to be started and a failure to start the Event Collector component can indicate a broad range of issues. In such cases, examine the log file for additional details about the error.

Consider the following snippet obtained from the BPM.log file corresponding to the error message above.

javax.transaction.xa.XAException: com.microsoft.sqlserver.jdbc.SQLServerException: Failed to create the XA control connection. Error: "Could not load the DLL SQLJDBC_XA.dll, or one of the DLLs it references. Reason: 126(failed to retrieve text for this error. Reason: 15105)."

The error message states that SQLJDBC_XA.dll or one of the DLLs it references could not be loaded. SQLJDBC_XA.dll is a pre-requisite for installation. Ensure that this file is present before proceeding with the installation.