The Licensing Service Is Too Old. Error: Flxactcommonhandleopen - (50003,71000,10103)

Published: 26 Feb 2020
Last Modified Date: 01 May 2020


When trying to produce a Trusted Storage file on an instance of Tableau Server that has previously had a failed or incomplete Upgrade attempt, or tried to activate licence key on Tableau Prep Builder,
the following error occurs:

"The licensing service is too old. ERROR: flxActCommonHandleOpen - (50003,71000,10103)"



  • Tableau Server 2019.2.2
  • Windows Server 2019
  • Tableau Desktop 2020.1
  • Tableau Prep Builder 2020.1
  • Host on which a failed or incomplete Tableau Server Upgrade has taken place.


Resolution for Tableau Server
  1. Confirm the build number of the version of Tableau Server that is in use.
  2. Check the Windows OS system environment variable PATH for any references to the 'bin' folder of any other versions of Tableau Server than the version with the build number of the version confirmed in step 1.
  3. Edit the PATH variable to remove any references to Tableau Server bin folders from versions other than the one in use.
  4. Restart Windows/OS Server.
Resolution for Tableau Desktop/Tableau Prep Builder
1. Check the version of the file FNPLicensingService64.exe 
a. Navigate to the FNPLicensingService64.exe file 
b. Right click > Properties > Details.
The file is located at C:\Program Files\Common Files\Macrovision Shared\FlexNet Publisher\FNPLicensingService64.exe .

2. If the version of FNPLicensingService64.exe is lower than, then
install Tableau Desktop 2020.1.0 to enable FNPLicensingService64.exe of version to be installed on the machine.


Failed or incomplete Upgrade of Tableau Server left references to the version of FlexNet that was part of a different version of Tableau Server. This can cause the existing version of Tableau Server to try to use a mismatched version of FlexNet.

And the proper version of FNP Licensing service that works with Tableau Desktop 2020.1/Tableau Prep Builder 2020.1 should be
Any version lower than may cause the above error.
Did this article resolve the issue?