Troubleshooting license related errors in SSIS Powerpack

[ZappySys]

Problem:

When you run SSIS Package inside Visual Studio it works fine but when you run via command line or SQL Agent Job you may get following error. Unfortunately, there is no one reason why such error can happen so please go through possible cause and solution listed in the next section.

Description: The Execute method on the task returned error code 0x80131500 (License type [SSIS_PP_TRIAL] not found.)

OR

System tried to search for the following license types [SSIS_PP_ENT, SSIS_PP_PRO, …….., SSIS_PP_TRIAL] under the following path [C:\ProgramData\ZappySys\SSISPowerPack] but no valid license found. Additional information >>> LoggedInUser=MYDOMAIN\MYSERVICEACCOUNT >> RunAsUser=MYDOMAIN\MYSERVICEACCOUNT >>> Path access=True >> >> TempFolder=C:\Windows\TEMP\ [Read/Write=OK,OK] >> License Files Scanned [2] ==> C:\ProgramData\ZappySys\SSISPowerPack\SSIS_PP_TRIAL.lic.130498499674709531 [Read=OK], . Please read this link for more information => https://zappysys.com/links/?id=10021. Inner error=> License type [SSIS_PP_TRIAL] not found or its expired. You are running TRIAL build, if you have paid license then you must download full version

Possible Cause(s):

There could be few possible reasons for license related errors.

We wrote another article to explain how to analyze License Error Message

Notes: We have fixed license permission related issues in the Latest Version.
PleaseDownload the Latest version and install it with Typical default setting and test it out.

Here are few possible ways to fix this error.

1. If you are running JOB on a cluster environment where Trial License worked fined but Paid License is failing then try these steps
   1. Run your JOB under Proxy account rather than default SQL Agent Account. We found that when JOB runs under SQL Agent Account it reports Cluster Name as MachineName but when License is registered on a Node its tied with Node Machine Name. Running JOB under Proxy account starts reporting Node name as MachineName and license issue goes away.
      Article#1 More info on this Error.
      Article#2 More info on this Error
2. You are running Job using Proxy account and Proxy account is trying to access Temp directory of Sql Agent Service Account (c:\users\MyAgentAccount\AppData\Local\Temp).
   

   Solution : To fix this issue click here

3. You have purchased license for Single Task or Bundle but your package is using one or more tasks for which you don’t have license. (e.g. You purchase license for JSON Source and started using REST API Task somewhere in the package)
   

   Solution : Purchase license for additional tasks/components you are using or Upgrade your version to higher edition (e.g. JSON Source >> JSON Integration Pack >> Standard Edition >> Professional Edition )

4. One reason for this error could be valid license is not registered (Verify from Start Menu > ZappySys > SSIS PowerPack > LicenseManager). Make sure License is not expired and Status is Valid (Check Status Column in License Manager UI Grid)
   If you don’t see valid License in License Manager UI that means you have to apply valid key.

   Solution :  To apply license check this link

5. If you have a valid license registered (Based on above check) and you still getting error that means Service Account or User Account used to execute Command line or SQL Agent JOB needs read/write permission for the following path C:\ProgramData\ZappySys
   

   Solution : Try to register license using Service account ( Check this article for step-by-step instructions ).
   –OR–
   Run JOB Step using Proxy. Here is the tutorial shows how to setup SQL Proxy Account to Run SSIS Job

6. If you are running JOB using Proxy account (Domain User) and you getting license error in some cases due to missing User Profile and Possible Temp directory.
   

   Solution : Remote Desktop to Server using Proxy account at least once (This process creates missing User Profile folder including user Temp directory for Proxy user. We have confirmed this helped for many users)

7. Some Trial user reported that Package is executed successfully under SQL Agent JOB but when you try to execute via SSMS > SSIS Catalog > Execute Package it fails then most likely its possible permission chain issue with the license.
   

   Solution : Rename C:\ProgramData\ZappySys to something like ZappySys.old and try to execute package again. It will recreate Trial file again with correct Permission chain. ProgramData is hidden folder so if you dont see go to View > Show hidden files and folders.

8. Some Trial user reported that Package is executed successfully under SSIS Catalog (SSMS > SSIS Catalog > Execute Package) but when try to execute via SQL Agent JOB it fails. This can be most likely permission chain issue with the license. Perform these steps see it helps.
9. Many times registering Trial extension from UI solved the error.
10. If you have trial version and SSIS Package fails to execute via SSMS ( SSIS Catalog -> Execute). Also when you check system event log you might see DistributedCOM (DCOM) Permission error like below.

    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
    {2DC39BD2-9CFF-405D-A2FE-D246C976278C} and APPID {DB336D8E-32E5-42B9-B14B-58AAA87CEB06}
    to the user DOMAIN\SOME_USER_ACCOUNT SID (S-1-5-21-xxxxxxxxxxxxxxx) from address LocalHost (Using LRPC) 
    running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component 
    Services administrative tool.

    In such a case try a few things listed here in detail (below at high level fixes)
    Method#1 Uninstall the Trial version and download the full Installer and activate the full license so certain registry key access such as HKCR\CLSID is not invoked in DCOM context. If you are not a paid customer then contact ZappySys Support to obtain FULL Installer.

    Method#2 If you see DCOM Error in System Event Log then, try some workaround mentioned by Microsoft  listed here and here

We find that #3 from above is the most common cause for license failure especially when SQL Agent is running under Custom Service account (Domain service account).

Many customers reported high success when License registered using Service account or Job step ran under Proxy account rather than default Service account. If you can run any sample package via command line (e.g. dtexec /F "c:\temp\mypackage.dtsx") but cannot execute same package via JOB then its mostly permission issue with Service Account. Check last step (below) how to create Proxy (using different account) to solve this issue.

Other Information:

Most common solution

• Open license manager and make sure you have at least one valid license (e.g. Standard Edition, Trial License)
• If you already have valid license then make sure task throwing above error is allowed to run under your purchased license type. For example If you purchased JSON Source License but tying to run REST API Task somewhere in that package then system will try to search license types in following order…
  1. Search Standard Edition License … if not found
  2. Search Web API Integration Pack License… if not found
  3. Search for REST API Task License… if not found
  4. Search for TRIAL License… if not found
  5. In none of above found then throw error
• If you suspect you don’t have correct license then purchase valid license or request Trial extension from us so you can run SSIS packages using SQL Agent or Command line
• If you have valid license then make sure you assign full permission to SQL Agent Service Account or any other account under which Package is running so it can read/write to C:\ProgramData\ZappySys folder and all sub folders
• To detect if its permission related issue or not, try to run sample SSIS Package with at least one paid task (e.g. REST API Task). run following command on command line

  dtexec /F "c:\somefolder\yourpackage.dtsx"

• If above command works fine on command line under your user account but when executed via JOB (under service account) it fails then its most likely permission issue with Service account used by SQL Agent.
• If you suspect above issue with SQL Agent Job then try to run JOB Step using Proxy account. Here is the tutorial shows how to setup SQL Proxy Account to Run SSIS Job
• If proxy account also doesn’t help then contact zappysys support

[Author]

Posts