Ranger is unable to validate read/write permissions to the folder specified for the repository.
Although there are a few causes for this (permissions, DNS resolution, network access) which are mentioned in another KB article (https://support.quest.com/vranger/kb/112246) the issue could simply be corruption with the network folder itself.
If you have already validated the permissions are correct, and trying to use the IP address for the share to rule out DNS resolution, and you can ping the IP from the Ranger server, you might consider the following:
1) Create a new folder on the same (or different) level as the existing folder that you use for your repository.
2) Share off the folder and provide read/write permissions to that folder for the account that you will use within Ranger.
3) Copy (if you have available space) or Cut the entire contents of the old repository (savepoints and the GlobalManifest) and paste these into the new folder that you have created.
4) Once the data has finished copying go back into Ranger and create a new repository, give it a new name that differs from the previous repositories name, and point it to this new folder that you created.
5) When asked if you want to 'Update' the existing during the import process choose 'Update' which will attempt to point your existing jobs to the new repository.
6) If the repository saves, and once the import finishes, go into My Jobs and edit your scheduled (or On Demand) just to validate that the new repository information did import and you jobs will point to the new location.
7) Run a test jobs against the new repository to validate that it will read/write.
8) If this succeeds remove the old repo, and remove the old folder from your network (if applicable).
