VersionRecall Error: Repository is not accessible

Use this forum to ask questions before you buy. Need information on licensing or pricing? Questions about a trial version? This is the right place for you. No scripting questions, please.
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
PaschalIT
Posts: 32
Joined: Tue Apr 02, 2019 4:37 pm

Re: VersionRecall Error: Repository is not accessible

Post by PaschalIT » Tue May 28, 2019 12:14 pm

Yes, the file server has a UNC path. What are you suggesting I switch to use the UNC?

User avatar
Alexander Riedel
Posts: 7021
Joined: Tue May 29, 2007 4:43 pm

Re: VersionRecall Error: Repository is not accessible

Post by Alexander Riedel » Wed May 29, 2019 12:03 am

Yes, I have tried any which to make happen what you observe and the only way I can do that is by having two userids where one does not have access to the drive mapping.
The use of a UNC path would verify that and potentially fix the problem for you as well.
Alexander Riedel
SAPIEN Technologies, Inc.

PaschalIT
Posts: 32
Joined: Tue Apr 02, 2019 4:37 pm

Re: VersionRecall Error: Repository is not accessible

Post by PaschalIT » Wed May 29, 2019 8:04 am

Changed both Powershell Studio and VersionRecall to load using the UNC path, no change. Still gives both of the same errors.