Symptoms

While performing a capability request/response call, the following error has been noted:

"System machine type does not match expected machine type.: [1,4,5,0[7000003F,0,450048]]"

Cause

It has been found that this error can be caused by a mismatch between the machine type information that is sent in the capability response and the machine type that the capability response application detects it is being run on.

To reproduce this error:

1. Set the MACHINE_TYPE in ExampleVirtualizationCallout.c to VIRTUAL.
   

   FlxBool
   FlxExtVirtualMachineGetType(
   FlxExtVirtualMachineRef vm,
   FlxUInt32 * type,
   FlxErrorRef error)
   {
   (void)vm;
   if(!type)
   {
   FlxSetExternalError(error, EXTERR_BAD_PARAM, 0, 20000);
   return FLX_FALSE;
   }
   /*
   * TODO - put detection code here,
   * for now hard code to FLX_MACHINE_TYPE_UNKNOWN
   */
   *type = FLX_MACHINE_TYPE_VIRTUAL;
   return FLX_TRUE;
   }

2. Create a capability request.
3. Through FlexNet Operations / back office server, generate a response.
4. Change the MACHINE_TYPE in ExampleVirtualizationCallout.c to PHYSICAL
   

   FlxBool
   FlxExtVirtualMachineGetType(
   FlxExtVirtualMachineRef vm,
   FlxUInt32 * type,
   FlxErrorRef error)
   {
   (void)vm;
   if(!type)
   {
   FlxSetExternalError(error, EXTERR_BAD_PARAM, 0, 20000);
   return FLX_FALSE;
   }
   /*
   * TODO - put detection code here,
   * for now hard code to FLX_MACHINE_TYPE_UNKNOWN
   */
   *type = FLX_MACHINE_TYPE_PHYSICAL;
   return FLX_TRUE;
   }

5. Process the response. This should result in the error.

Resolution

Ensure that the code that deals with the machine type is coded in a way that will process this information correctly.