Loading

Error "Some of your product keys could not be synchronized" or "116 tableau_error_licensing_resync_general"

Publiseringsdato: Dec 24, 2025
Beskrivelse
When refreshing a product key in Tableau Desktop or Tableau Server, the following error occurs in Manage Product Keys:

Some of your product keys could not be synchronized: <keys>

When activating, deactivating, or refreshing Tableau Server keys via TSM, the following error occurs: 
 
116 tableau_error_licensing_resync_general

Cause

The root cause may vary depending upon which of the above scenarios was the origin of the error.
  • The computer running Tableau Desktop or Tableau Server is unable to communicate with the Tableau Licensing Server.
  • The key is already at the highest available subscription term or maintenance renewal level.
  • The key is obsolete and has been replaced.
  • The machine is in an offline mode with no connectivity to the Internet.
  • Tableau Desktop/Prep is using the Virtual Desktop option.
  • Tableau Desktop/Prep is using the LBLM activation.
  • Tableau Server is using the ATR activation service.
Løsning
Several issues may result in the error listed above. Try the below troubleshooting steps to identify the origin of the error.
  • If the Desktop activation was done using Login-based License Management (LBLM) or Virtual Desktop, no refresh is required.  If Tableau Server is using the ATR activation method, no refresh is required.  These activation methods use the ATR activation service and do not require refreshes.

  • Verify in the Tableau Customer Portal that the product key has additional maintenance or a new subscription term.  Compare the period end date in the Tableau Customer Portal to the end date in the Desktop Manage Keys or Server TSM Licenses UI.  If the expiration or maintenance end date of the license key listed on the product matches the period end date in the Tableau Customer Portal, then there is no additional refresh needed.

  • Verify the key being refreshed in the Desktop Manage Product Keys is found in the Tableau Customer Portal and matches the key being refreshed in the Desktop Manage Product Keys.  If a key has been replaced by another key, it will not be possible to refresh the obsolete key. The new key must be activated to obtain the higher maintenance date.

  • If the product key was activated offline previously due to the inability to reach out to the Tableau License Server, the refresh will fail. 
    Another offline activation will need to be completed to obtain a higher license maintenance end date. Please visit the Tableau Customer Portal to obtain the updated key with the latest maintenance end date.

  • The license data on the Tableau Server or Tableau Desktop computer may be out of sync with the Tableau License Server. 
    Please contact Technical Support and provide the license data outlined in this article: Providing License Data to Tableau Support.

  • The key may be at a maximum activation level.
    Please contact Tableau Technical Support and provide the licensing ID for the key being refreshed or a screenshot of the refresh error that contains the key(s).

  • Check if a previous version of Tableau Desktop is installed, then try refreshing the product key in that version.

  • Ensure that nothing is blocking communication to or from licensing.tableau.com on port 443 of the computer running Tableau Desktop or Tableau Server. For more information, see the Licensing section of the Internet Access Requirements article.

  • Proxies or firewalls such as zscaler may rewrite portions of SSL certificates when Tableau tries to reach the licensing server. 

    1. Run a Fiddler trace and see if the issue resolves.
    2. If the issue does not occur with Fiddler, check for any firewalls, proxies, etc. in the environment that may affect the SSL certificates. For a closer look at traffic, use a Wireshark test to examine the SSL certificates being passed.
    3. Note: Fiddler acts as a software proxy in gathering traffic, and may also rewrite SSL certificates, resulting in Tableau being unable to trust a mismatch in the SSL Certificate signature. More information on Fiddler fixing issues, follow this link.
Knowledge-artikkelnummer

001473814

 
Laster
Salesforce Help | Article