Troubleshooting path errors when configuring a source component in SSIS

SSIS PowerPack Troubleshooting
,
1

Problem

When configuring a file-based Source component (e.g. JSON Source, CSV Source, XML Source) in ZappySys, you may see one of these errors:

Access to the path "c:path/folder" is denied.

Could not find a part of the path 'D:\Zappysys\Test\JSONs\'.

Cause

The same underlying issue usually causes both errors: the File path field points to a folder instead of a file, so the component either tries to open the folder as if it were a file (Access denied) or looks for a file whose name is the folder path itself (path not found).

  1. Path field contains only a folder path, with no file name or wildcard.
  2. Path syntax is malformed, with mixed slash types or a missing separator (e.g. c:path/folder is missing the backslash after the drive letter).
  3. The account running the package does not have read permissions on that folder/file.

Solution

Method 1: Point to a specific file

  1. In the Source component editor, open the File Name / Path field.
  2. Enter the full path, including the file name and extension:
D:\Zappysys\Test\JSONs\file.json
  1. Save the configuration and run the package to confirm the file is read correctly.

Method 2: Use a wildcard to read multiple files

  1. In the Source component editor, open the File Name / Path field.
  2. Instead of the bare folder path, enter a wildcard pattern that matches the files you want:
C:\path\folder\*.json
  1. Save the configuration and run the package to confirm the expected files are picked up.

Best practice

To avoid this issue:

  1. Always point the Path field at a file or a wildcard — never at a bare folder path.
  2. If subfolders also need to be included, check whether the component offers a recursive/subfolder option rather than trying to express that in the wildcard itself.
  3. Use consistent path syntax for the OS (backslashes for Windows paths, correct drive letter, no missing separators).
  4. Confirm the account running the package has read permissions on the target folder/file before troubleshooting further.

Need more help?

If the issue persists, contact ZappySys Support: