critical mail: PACKET PROCESS THREAD...RAISED AN EXCEPTION

[Belinda Frick]

I am using the AMTMitelCRE recording solution Version [1.6.4.7] and I get the following critical e-mail:

--------------------- CRITICAL ERRORS START HERE ---------------------
2012-05-28 10:48:13 2012-05-28 10:48:13 THE PACKET PROCESS THREAD EXECUTE ON CRE SERVER AMETHYST RAISED AN EXCEPTION.
---------------------- CRITICAL ERRORS END HERE ----------------------

AMTMitelCRE log entries at time of critical e-mail:

Code: Select all

[2012-05-28 10:48:13.811] Version [1.6.4.7] Error in TPacketProcessor.ProcessPackets.BlockWrite: Disk full
[2012-05-28 10:48:13.811] Version [1.6.4.7] CRITICAL ERROR: PacketProcesser Execute Exception: Disk full

[2012-05-28 10:48:23.810] Version [1.6.4.7] Error in TPacketProcessor.ProcessPackets.BlockWrite: I/O error 27

This could be an incorrect disk full error message.

To ensure that recordings are taking place and loading, please check:

• the amtmitelcre log:
  AMETHYST Webadmin -> Configure Cardserver/CRE, click on view log link. Scroll down to see last entries and compare with current date-time.
• the sweeper log:
  AMETHYST Webadmin -> View Logs, click on the today line and then the view log link for sweeper. Scroll down to see last entries and compare with current date-time.
• You can also check under View Call History if recordings for the last hour is loading:
  AMETHYST Webadmin -> View Call History.

If any errors in the logs, please search the forum for them to address it.

If no recordings are taking place please check

• the space on the AMETHYST server and your CRE server:
  AMETHYST Webadmin -> Available Disk Space
• that the AMTMitelCRE software is running:
  On the AMETHYST Webadmin Home page, the link must display 'Stop AMTMitelCRE'. If it shows 'Start AMTMitelCRE' then it is not running and you need to click on it to start it.

NOTE:

I/O error 27 is "file too large". It wrote a 2GB RTP file, which is the maximum it can write. It could because an agent didn't put the phone down or something similar.

It kept giving this error until the extension stopped recording, which is why we kept getting error messages. File errors of this type are limited to sending e-mails every 2 hours.

This problem will be fixed in the next version of the CRE.

UNDER INVESTIGATION!!!