How to Resolve the Probe Log Error: nimQoSPostMessage - the CI interface has been used in this probe and should be implemented for this QoS as well!!!

Document ID : KB000034265
Last Modified Date : 14/02/2018
Show Technical Document Details
Problem: 
You may see messages like these in the probe log file (level 2):
 
Feb 17 07:25:28:672 sql_response: nimQoSPostMessage - QoS=QOS_95TH_INTERFACE source=ZEUS.colospace.local target=Bed.access.SW02-022\QOS_95TH_INTERFACE\(null)
 
Feb 17 07:25:28:675 sql_response: nimQoSPostMessage - the CI interface has been used in this probe and should be implemented for this QoS as well!!!
 
Feb 17 07:25:28:675 sql_response: nimQoSPostMessage - QoS=QOS_95TH_INTERFACE source=ZEUS.colospace.local target=Bed.access.SW02-032\QOS_95TH_INTERFACE\(null)
 
Feb 17 07:25:28:738 sql_response: nimQoSPostMessage - the CI interface has been used in this probe and should be implemented for this QoS as well!!!
 
Feb 17 07:25:28:738 sql_response: nimQoSPostMessage - QoS=QOS_95TH_INTERFACE source=ZEUS.colospace.local target=Bed.access.SW02-030\QOS_95TH_INTERFACE\(null)
 
 
Cause: 
These messages can be caused by 32 bit binaries being installed on a 64 bit machine.  This can occur if the customer updated their Windows OS from 32bit to 64bit
 
Resolution:
Redeploy the probe and ensure it deploys the 64 bit version of the binaries.  Ensure the JRE is running 64 bit as well.  It might also be necessary to redeploy the robot, hub etc.