SSIS Package Fails with System.Data.SQLite Could Not Load Error (E_POINTER)

Ishika Raiyani 20 Reputation points

I have deployed an SSIS project using an .ispac file into SSISDB. The project contains Cdata Odoo components and Kingswaysoft toolkit.

When I try to execute the package (both from SSISDB and from Visual Studio), it fails with the following error:👁 Uploaded image

[ConnectionException] Unable to establish a connection using provider [System.Data.SQLite]. Details: Could not load file or assembly 'System.Data.SQLite' or one of its dependencies. Invalid pointer (Exception from HRESULT: 0x80004003 (E_POINTER))

I have already installed System.Data.SQLite on the machine, but the error still occurs in both environments.

Question:

What is the correct way to configure or install System.Data.SQLite so that SSIS can properly load it during package execution?

Are there additional steps required (such as handling dependencies, runtime architecture, or deployment configuration) to resolve this issue?

0 comments No comments
Sign in to comment

Answer recommended by moderator

Akhil Gajavelly 1,830 Reputation points • Microsoft External Staff • Moderator

Hi @Ishika Raiyani ,

Thanks for confirming that means the SQLite issue is resolved.

The new error, “The given path’s format is not supported” is not related to SQLite. It indicates an issue with the file path/connection string used in your package. Try bellow steps

  • Verify any file paths or connection strings used in:
    CData Odoo connection
    Flat file / SQLite source
  • Ensure the path is:
    • A valid absolute path (e.g., C:\folder\file.db or \server\share\file.db)
      • Not empty, malformed, or containing invalid characters
      • If using parameters/variables, confirm they are resolving correctly at runtime (SSISDB vs VS can differ)

Add a temporary Script Task or logging to print the final resolved path this usually reveals the issue immediately.

This is now a path/configuration issue, not a driver problem.

Thanks,
Akhil.

0 comments No comments
Sign in to comment

1 additional answer

  1. Akhil Gajavelly 1,830 Reputation points • Microsoft External Staff • Moderator

    Hi @Ishika Raiyani ,

    This error is usually caused by architecture mismatch or missing native dependency.

    To Fix follow bellow steps,

    Install the official System.Data.SQLite bundle (not just DLL)

    Ensure both files are available:

    System.Data.SQLite.dll

    SQLite.Interop.dll (required)

    Match runtime:

    SSISDB/SQL Agent → 64-bit

    Visual Studio → set Run64BitRuntime = True (or install x86 as well)

    Copy DLLs to:

    C:\Program Files\Microsoft SQL Server<version>\DTS\Binn\

    Install VC++ Redistributables (x86 & x64)

    Root Cause

    Missing SQLite.Interop.dll or 32/64-bit mismatch causes the E_POINTER error.

    Thanks,
    Akhil.

    1. Ishika Raiyani 20 Reputation points

      I followed the recommended steps:

      Installed the official System.Data.SQLite bundle

      Copied the DLLs to:

      C:\Program Files\Microsoft SQL Server<version>\DTS\Binn\

      Verified runtime settings (64-bit execution)

      Installed VC++ Redistributables (x86 & x64)

      After applying these changes, I am now encountering a different error when running the package (both in SSISDB and Visual Studio):

      👁 User's image

      Question:

      Since the original SQLite assembly issue seems to be resolved, how should I proceed with troubleshooting this new error?

    2. Akhil Gajavelly 1,830 Reputation points • Microsoft External Staff • Moderator

      Hi @Ishika Raiyani ,

      Just following up to check whether you were able to verify the file paths/connection strings suggested earlier.

      Since the current error points to an invalid or unresolved path format, confirming the final resolved path at runtime (especially when executed from SSISDB vs Visual Studio) will help identify the exact cause.

      If the issue still persists, please share:

      The exact connection string/path being used (mask sensitive details if needed)

      Whether the package runs from VS but fails in SSISDB

      A screenshot of the failing component/error details

      That will help narrow this down further.

      Thanks,
      Akhil.

    3. Akhil Gajavelly 1,830 Reputation points • Microsoft External Staff • Moderator

      Hi @Ishika Raiyani ,

      Just following up to check whether you were able to verify the runtime file path/connection string behavior suggested earlier.

      If the issue still persists, please share any updated error details or screenshots from the SSIS execution logs, especially whether the package works in Visual Studio but fails from SSISDB. That will help narrow down the root cause further.

      Thanks,
      Akhil.

    Sign in to comment
Sign in to answer

Your answer