unable to retrieve versions from VersionRecall

Support for all customers who have purchased a VersionRecall product license. This forum does not offer a response time guarantee.
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.
User avatar
clhumphr
Posts: 16
Joined: Mon Nov 29, 2010 5:43 am

unable to retrieve versions from VersionRecall

Post by clhumphr » Wed Aug 03, 2016 5:32 am

Product, version and build: 1.2.133
32 or 64 bit version of product: 64
Operating system: Windows 7
32 or 64 bit OS: 64

When trying to pull out a different version of any script within VersonRecall I get the following message:
The VersionRecall tray application is currently updating this folder or repository. Please try again later.

this has been going on for some time and has slipped through the cracks on my part. However, I have not needed to pull an old version of my scripts till yesterday, which makes the more of an issue for me now.

The repository log file is empty however, the service log @ C:\ProgramData\VersionRecallService\service.log looks like this:
08/01/2016 08:33:08 AM: Repository is offline at 08/01/16 08:33:08
08/01/2016 10:33:14 AM: Repository is offline at 08/01/16 10:33:14
08/01/2016 12:33:23 PM: Repository is offline at 08/01/16 12:33:23
08/01/2016 02:33:30 PM: Repository is offline at 08/01/16 14:33:30
08/01/2016 04:33:39 PM: Repository is offline at 08/01/16 16:33:39
08/01/2016 06:33:40 PM: Repository is offline at 08/01/16 18:33:40
08/01/2016 08:33:41 PM: Repository is offline at 08/01/16 20:33:41
08/01/2016 10:33:42 PM: Repository is offline at 08/01/16 22:33:42
08/02/2016 12:33:43 AM: Repository is offline at 08/02/16 00:33:43
08/02/2016 02:33:44 AM: Repository is offline at 08/02/16 02:33:44
08/02/2016 04:33:45 AM: Repository is offline at 08/02/16 04:33:45
08/02/2016 06:33:46 AM: Repository is offline at 08/02/16 06:33:46
08/02/2016 08:33:47 AM: Repository is offline at 08/02/16 08:33:47
08/02/2016 10:33:55 AM: Repository is offline at 08/02/16 10:33:55
08/02/2016 12:34:02 PM: Repository is offline at 08/02/16 12:34:02
08/02/2016 02:34:09 PM: Repository is offline at 08/02/16 14:34:09
08/02/2016 02:57:07 PM: VersionRecall Service started

08/02/2016 02:57:07 PM: Repository is offline at 08/02/16 14:57:07
08/02/2016 04:17:15 PM: VersionRecall Service started

08/02/2016 04:17:15 PM: Repository is offline at 08/02/16 16:17:15
08/02/2016 06:17:24 PM: Repository is offline at 08/02/16 18:17:24
08/02/2016 08:17:25 PM: Repository is offline at 08/02/16 20:17:25
08/02/2016 10:17:26 PM: Repository is offline at 08/02/16 22:17:26
08/03/2016 12:17:27 AM: Repository is offline at 08/03/16 00:17:27
08/03/2016 02:17:28 AM: Repository is offline at 08/03/16 02:17:28
08/03/2016 04:17:29 AM: Repository is offline at 08/03/16 04:17:29
08/03/2016 06:17:30 AM: Repository is offline at 08/03/16 06:17:30
08/03/2016 08:17:31 AM: Repository is offline at 08/03/16 08:17:31

Thanks,

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

Re: unable to retrieve versions from VersionRecall

Post by Alexander Riedel » Wed Aug 03, 2016 9:46 am

The log indicates that the tray application cannot reach your repository. Please specify where the .recall file is located and what the location of your repository is.
It would be helpful to email the .recall file to support@sapien.com
Alexander Riedel
SAPIEN Technologies, Inc.

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

Re: unable to retrieve versions from VersionRecall

Post by Alexander Riedel » Thu Aug 04, 2016 10:09 am

According to your email and your .recall file you have your source files, your repository and your alternate repository on the same physical NAS.
While this not only defeats the purpose of storing your files on different physical media to prevent loosing everything when your hardware become defect,
it may also prevent successful operation. Since NAS device usually run Linux with a Linux file system and a rather low-powered processor, performance for small files is generally very slow.

If the repository log file is empty and the repository is shown offline, it appears as if you never made an actual connection to that repository.
Please shut down the tray app and see if you can connect to your repository from the VersionRecall Explorer. See if the files there show a status other than offline.
Maybe it would be best to post a screenshot.
Alexander Riedel
SAPIEN Technologies, Inc.