Skip to Content
avatar image
Former Member

ERROR XRS6016 AFARIA 7

Hello,

In my company we are having an incidence with Afaria. All Android devices are being blocked. The error that LOG gives in Afaria is:

XRS6016: Tenant ID mismatch. Client reported Tenant ID = 6. EXPLANATION: The client reported a Tenant ID that does not match the Tenant ID currently associated with the client. ACTIONS: The client has been reassigned to the generic Tenant ID '0' and marked as unapproved. The administrator will have to reassign the client to the proper Tenant ID or delete the client definition altogether.

Can you help me?

Regards

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Jul 24, 2017 at 01:09 PM

    Hello Rafael,

    I found the KBA # 2343267

    Cause:

    In Afaria 7 SP4 and older versions it is possible possible to select the Session Manager Channel to import in another tenant.

    This is in Afaria 7 SP5 and higher no longer possible.

    Here is the Solution:

    1. Move unnaproved Android devices with the error "XRS6016: Tenant ID mismatch. Client reported Tenant ID = X." to the tenant id X (X is the number of the tenant)
    2. Approve all devices in this tenant and apply policies.
    3. Wait until all the devices connected successfully
    4. Move all devices back to the correct tenant
    5. All devices are approved in the correct tenant and can connect successfully to the Afaria Server

    If this resolves your issue, please mark as correct answer so it will help others if they come across same issue.

    Regards,

    VP

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 24, 2017 at 03:51 PM

    The AFARIA 7 version we currently have is the SP15

    Add comment
    10|10000 characters needed characters exceeded

    • I found the problem of the message same as you. This problem seemed to occur in SP15 environment.
      This phenomenon was reported in following KBA.

      2350503 - Incidents reported by customers that have been fixed in SAP Afaria 7.0 SP18 (7SP18).
      > Android Devices
      > •For some subsequent connections, successfully enrolled Android devices request a valid, different tenant which causes these devices to be moved to the system tenant as "unapproved" devices. Any following connections, result in these devices continuing to be moved to the system tenant as "unapproved" devices. [BCP 190376/2016, SMS-30451]

      This customer upgraded SP15 with SP23 and seemed to evade this phenomenon.

      2338319 - Supported upgrade paths - Afaria

      Thanks,
      Atsushi