Chronicall Errors caused by [Missed Packet]






Errors within Xima’s Chronicall logs can be caused by the system missing reported events.  This can be seen within the Tomcat logs located “C:\Program Files (x86)\Xima Software\Chronicall\tomcat\logs”  Search by the Date Modified and inspect the latest file beginning with the Year-Month-Date-xxxxxx.log.

Within this file, look for [Missed Packet].  The line will look similar to:

“Tue May 05 13:22:04 CDT 2015 [Missed Packet: expecting 87034 received: 87036] ...

Continue Reading →

Avaya UCM Problems

We recently experienced trouble with our Avaya Unified Communications Module (UCM). Naturally this occurred just after the 1 year warranty expired. So despite there being a proliferation of problems with these modules…Avaya would not do anything – so, we were forced to make some decisions.

We were able to resolve the problem by re-imaging the UCM.

Consider NOT replacing or fixing the UCM. After the UCM failed, our tech felt the quickest way to ...

Continue Reading →

VirtualCenter Server will not start

Was working one minute…now its not! Welcome to the wonderful world of Windows Updates. I’m assuming this was broken by the unattended installation of Server 2008 R2 SP1 through our environment or some KB update prior.

It all started with this error when I tried to log into VCenter Server:

“vSphere Client could not connect to ‘{machine name}’ A connection failure occurred (Unable to connect to the remote server)”

After investigating this, I determined the VMware VirtualCenter Server Service was not running. However, ...

Continue Reading →

Renaming a VMWare Virtual Machine

This procedure was documented using VM Infrastructure 3.5 for altering ESXi 3.5 virtual machines. You may need to use Veeam to make the renaming adjustments. Could also be done via SSH.

CAUTION: If snapshots do exist and are needed, then you may need to alter the *.vmdk files to keep the chaining in place. If you do not need the snapshots, select “delete all” under the snapshot manager and perform this procedure after the host has consolidated them.


  1. Copy to ...
Continue Reading →

Importing Excel XLS to SQL SSIS error

While trying to execute an SSIS import package on a customer’s Excel file, SQL Server 2008 SP1 was returning a “truncated” error. Although, the SSIS package was set to ignore these, the execution halted and data was not written to the SQL table.

There were a number of posts including David Klein’s and Waxtadpoles regarding SQL 2005 and the “TypeGuessRows” setting in the registry.  Their suggestion was to set the value to 0 (zero), in order to force ...

Continue Reading →