Sometimes when running package which uses SSIS PowerPack Components You may get below error
Error: System.IO.FileLoadException: Could not load file or assembly 'ZappySys.Json' or one of its dependencies.
Invalid pointer (Exception from HRESULT: 0x80004003 (E_POINTER))
File name: 'ZappySys.Json' ---> System.ArgumentNullException: Value cannot be null.
Parameter name: value
The above error may be due to missing DLL. Any of the following reasons can cause this error.
- You are using a newer version of SSDT with SQL Server 2019 as default (i.e. SSDT 15.8.1 or higher).
- You are using Default TargetServerVersion (i.e. SQL Server 2017) but SSIS PowerPack did not install it or user unselected during setup.
- Your SSIS PowerPack setup did not install required files or you have unselected some SSIS Versions manually during setup.
- You have installed some other 3rd party SSIS Components (e.g. Microsoft SSIS Azure FeaturePack) which is conflicting with ZappySys.
- You might be using HTTP Connection Manager with Dynamic Token Method
Try these solutions, one by one:
This issue was resolved in SSIS PowerPack v184.108.40.20620. Thus if you are using an older version simply update it.
If you are a trial user use this link:
If you are an existing user use this link:
If you are using HTTP Connection with Dynamic Token Method then change Token Extraction Mode from Json to Regex.
For example if you entered JSONPath as
then change that option to Regex like below. It will extract value of access token. For more information on Regex check this article.
To fix above error you have to change TargetServerVersion as mentioned here - Select the one to match your SQL Server Version. After you change Default Target Server Version you will see your Project Name suffixed with Version name in the Solution Explorer Tree Node (e.g. TestProject (SQL Server NNNN).
You can also try re-install SSIS PowerPack (Uninstall and then Install). Make sure you Select Custom Install and make sure all SSIS Versions selected including 2017.
If you just installed some 3rd party components / tools other than ZappySys and started noticing this issue then most likely its conflicting with ZappySys. For example some customer reported this error after installing SSIS Azure FeaturePack.
Try to uninstall conflicting product and see error goes away. We also offer Azure related components in PowerPack.
If above fixes don't help, perform the steps below.
Go to this folder using Windows Explorer:
-- OR -- (use Command Line to find below folder if you are using version 220.127.116.1131 or older)
Then locate a similar latest modified folder like below, enter it and copy "ZappySys.Json.dll" file:
Copy this file to Path Specified in next 2 sections.
For Visual Studio Error - Copy to below path
If you got error during Package Execution in Visual Studio SSIS Designer then paste "ZappySys.Json.dll" to below folders (Assuming you installed Visual Studio on C Driver):
C:\Program Files (x86)\Microsoft Visual Studio\2017\<YOUR INSTANCE NAME>\Common7\IDE\CommonExtensions\Microsoft\SSIS\<VERSION>\Binn\
Example folder looks like this:
C:\Program Files (x86)\Microsoft Visual Studio\2017\SQL\Common7\IDE\CommonExtensions\Microsoft\SSIS\150\Binn\
C:\Program Files (x86)\Microsoft Visual Studio\2017\SQL\Common7\IDE\CommonExtensions\Microsoft\SSIS\140\Binn\
C:\Program Files (x86)\Microsoft Visual Studio\2017\SQL\Common7\IDE\CommonExtensions\Microsoft\SSIS\130\Binn\
If above folder doesn't exist, paste the file to the SQL Server as indicated below (choose the Target Server version you use in the VS project).
For SSIS Catalog / JOB Error - Copy to below path
If you got error during Package Execution in SSIS Catalog or SQL Job / DTEXEC Command line then paste "ZappySys.Json.dll" to below folders (Assuming you installed SSIS on C Driver):
C:\Program Files\Microsoft SQL Server\<VERSION>\DTS\Binn
C:\Program Files (x86)\Microsoft SQL Server\<VERSION>\DTS\Binn
Example folder looks like this:
For SQL 2019
C:\Program Files\Microsoft SQL Server\150\DTS\Binn
C:\Program Files (x86)\Microsoft SQL Server\150\DTS\Binn
For SQL 2017
C:\Program Files\Microsoft SQL Server\140\DTS\Binn
C:\Program Files (x86)\Microsoft SQL Server\140\DTS\Binn
If nothing helps, then you can try turning on Fusion Logging and examine the logs.