Troubleshooting path errors when configuring a source component

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

Both errors are usually caused by pointing the File Name / Path field at a folder instead of a file:

  1. The path entered is a folder, not a specific file; the component tries to open the folder itself, which results in “access is denied”.
  2. The path is missing a file name or wildcard at the end, so the engine looks for a file matching the folder path exactly and reports “could not find a part of the path”.
  3. The path syntax is malformed, missing a backslash after the drive letter, or mixing \ and / separators (e.g. c:path/folder), which can trigger these errors even when the folder itself is valid.

Solution

Point to a specific file

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

Use a wildcard to read multiple files

  1. Open the Source component editor.
  2. In the File Name / Path field, enter the folder path followed by a wildcard pattern instead of a bare folder path:
    C:\path\folder\*.json
  3. Save the configuration and run the package to confirm the matching files are picked up.

Best practice

  1. Always end the File Name / Path field with either a file name or a wildcard (e.g. *.json), never 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 inside the wildcard itself.
  3. Use consistent path syntax: backslashes (\) for Windows-style paths, with a separator after the drive letter (C:\, not C:).
  4. If the path and syntax are both correct and the error still occurs, confirm the account running the package has read permissions on that folder/file.

Need more help?

If the issue persists, contact ZappySys Support: