Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

File path not recognized when creating file system repository



When creating the file system repository, the file path is not recognized.

Error Messages

Specified path is not valid

Steps to Reproduce

  1. Create a repository.
  2. Select a file system and add a network drive location which has full access privileges.

Root Cause

A defect or configuration issue in  the operating environment.
The Windows Network Share Path is not visible from the Pega instance that is run from a Linux system.


Perform the following local-change:

The node on which the Pega instance is running must access and detect the path specified in the 'Resource Path' property.
In this case, since the Pega instance is run from a Linux based environment, to make the Windows share available, the the shared directory must be mounted (for example, \\<hostname>\<directoryname>) on the Linux node with the help of cifs-utils (or any other client, such as Samba).

Follow the below steps such that the Windows File-System Repository works from a Linux environment:
  1. Install cifs-utils.
  2. Mount the Windows Share using the /etc/fstab file to provide the details of the Windows Shared folder.
  3. Run the -a Mount command to mount this directory. The Share is mounted successfully
  4. Log in to Pega Platform 7.3.1.
  5. Create a new repository type and provide the new mount location.
  6. Click Test connectivity.

Published May 9, 2019 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us