Cisco Cisco Customer Response Solution Downloads トラブルシューティングガイド

8-79

Cisco Unified Contact Center Express Servicing and Troubleshooting Guide, Release 7.0(1)

Chapter 8 Troubleshooting Tips

High Availability and Bootstrap

This section contains the following troubleshooting tips on Cisco Unified CCX 7.0(1) high availability
and bootstrap problems:

•

Transaction Manager cannot start, page 8-79

•

Have an exception on startup with a message like "unable to recover transaction" or an error message
related to reading or modifying the "Tx.per" file., page 8-79

Transaction Manager cannot start

Symptom

Cisco Unified CCX cannot be started since the Transaction Manager failed to start.

Error Message The "BOOTSTRAP_START_ERROR" and "transaction manager is not started"
error messages are in the same log statement.

Possible Cause

The third-party Transaction Manager (Mahalo) log in wfavvid\TxnMgrPersistence\ may

be corrupted.

Recommended Action

Manually clean TxnMgrPersistence? directory.

Step 1

Shut down the Node Manager.

Step 2

Copy everything in the wfavvid\TxnMgrPersistence\ directory to a backup directory. Then delete all the
files in the wfavvid\TxnMgrPersistence\ directory.

Step 3

Restart the Node Manager.

Have an exception on startup with a message like "unable to recover
transaction" or an error message related to reading or modifying the "Tx.per"
file.

Symptom

Symptom #1: in the log, you see TxLoggerException?, TxLoggerIOException?,

TxLoggerClassNotFoundException?, TxLoggerFileNotFoundException?, or other Tx......Exception.

Symptom #2: when bootstrap_mgr debug log is turned on, if you see "Recovery.recover" and "about to
recover." but did not see "Recovery.recover(): total pending tx: or "Recovery.recover(): no pending tx".

Symptom #3: or if you see an error message that mentions the file "Tx.per".

Error Message See the previous symptoms topic for the message.

Possible Cause

The files in BSTxState? may be corrupted.