VersionRecall Error: Repository is not accessible

Use this forum to ask questions after your subscription maintenance expires or 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.
This topic is 4 years and 9 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
PaschalIT
Posts: 38
Last visit: Fri Jan 10, 2020 7:38 am

Re: VersionRecall Error: Repository is not accessible

Post by PaschalIT »

Yes, the file server has a UNC path. What are you suggesting I switch to use the UNC?
User avatar
Alexander Riedel
Posts: 8479
Last visit: Thu Mar 28, 2024 9:29 am
Answers: 19
Been upvoted: 37 times

Re: VersionRecall Error: Repository is not accessible

Post by Alexander Riedel »

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: 38
Last visit: Fri Jan 10, 2020 7:38 am

Re: VersionRecall Error: Repository is not accessible

Post by PaschalIT »

Changed both Powershell Studio and VersionRecall to load using the UNC path, no change. Still gives both of the same errors.
This topic is 4 years and 9 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.