Repository is stored on the NAS however the Service log allways tells me Repository is offline.
I have tried to set up a repository on a different server than the NAS but i still get the same info in the service log. I have yet to have VersionRecall actually keep any versions of my files using the service.
Any suggestions?
I am running Windows 7 64bit and the 64bit SAPIEN Software Suite 2014 with VersionRecall version 1.0.107.0 dated 10/28/2014 7:35PM
Repository is offline
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION 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.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
DO NOT POST LICENSE NUMBERS, ACTIVATION 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.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
Re: Repository is offline
This is most likely a permissions issue. The user that the Service runs under will require permission to access NAS drive (unless the NAS drive has no restrictions). By default the service runs under SYSTEM user.
David
David
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Repository is offline
Thanks David it was permissions the local SYSTEM user did not have rights, once I changed the service to run under my account VersionRecall is now working as it should. Thanks again..davidc wrote:This is most likely a permissions issue. The user that the Service runs under will require permission to access NAS drive (unless the NAS drive has no restrictions). By default the service runs under SYSTEM user.
David