Please enable JavaScript to view this site.

CopiaFacts™ Reference Manual

Navigation: Introduction > Troubleshooting

CopiaFacts shuts down on BladeWare failures

Scroll Prev Top Next More

Symptoms:

A BladeWare Error/Exception in COPIAFACTS causes shutdown

Actions:

Open the trace file for the day of the shutdown and search/filter for the string kill_flags = 00000010. You may need to press F12 to see more than just the last session in the file. For BladeWare users, this string normally confirms that the fault is in BladeWare.

If the trace file has a session which starts other than at midnight check the configuration listing at the start of the session to see if under "Services" it shows BladeWare Service with version 2.4.18.0. If not, try downloading this with COPIAINSTALL and installing it. Version 2.4.18.0 is the most reliable version we have available.

Send the trace file to Copia Support for further advice. Other details in the trace file may confirm that the issue is cause by a failure in BladeWare, or lead to an alternative resolution of the problem if not.

If OMACHECK is not being used, Copia Support will recommend settings for automatic shutdown and restart on BladeWare error outcomes. This will also ensure that BladeWare issues are quickly detected and the machine rebooted, so that any resulting failed transmissions are retried.

If problems in BladeWare continue to occur, our recommendation is to switch to TE-Systems XCAPI. Support from Commetrex for BladeWare is no longer available.