Coldmoon
June 3rd, 2009, 10:47 AM
Hi all,
We recieved a report from a user today indicating that installation of RVS 3 Beta 4 resulted in the product registration being expired due to a unique set of circumstances. We are working to fix this issue as quickly as possible.
What happened:
1. Install RVS 3 Beta 4 on a time shifted system (Ex: Today's date is June 2009 but the system is set for June 2000) - software registration is shown as expired
2. Common method to correct - User resets their system time to the current day/date - the software still shows expired
3. Uninstall/reinstall with proper day/date reset before installation of the software - still results in expired registration
The work-around:
If this happens, please do the following:
1. Exit (stop) the Returnil GUI
2. Run "services.msc" and then stop the "Returnil Core Service"
3. Open a command prompt, change directory to
%SystemRoot%\system32\Returnil\RVS3, and then delete all "*.db" files
4. Restart the "Returnil Core Service"
5. Restart the Returnil GUI
This should correct the issue.
Mike
We recieved a report from a user today indicating that installation of RVS 3 Beta 4 resulted in the product registration being expired due to a unique set of circumstances. We are working to fix this issue as quickly as possible.
What happened:
1. Install RVS 3 Beta 4 on a time shifted system (Ex: Today's date is June 2009 but the system is set for June 2000) - software registration is shown as expired
2. Common method to correct - User resets their system time to the current day/date - the software still shows expired
3. Uninstall/reinstall with proper day/date reset before installation of the software - still results in expired registration
The work-around:
If this happens, please do the following:
1. Exit (stop) the Returnil GUI
2. Run "services.msc" and then stop the "Returnil Core Service"
3. Open a command prompt, change directory to
%SystemRoot%\system32\Returnil\RVS3, and then delete all "*.db" files
4. Restart the "Returnil Core Service"
5. Restart the Returnil GUI
This should correct the issue.
Mike