TGRMN Software Logo ViceVersa PRO

FAQ and Knowledge Base

Main Page > Browse Categories > Solutions to Known Issues > [VVScheduler] Windows Server 2016 issues

[VVScheduler] Windows Server 2016 issues

When the new operative system Windows Server 2016 was initially released, VVScheduler had the following issues:  

1) Scheduled tasks may have shown incorrect Next Run Time, Last Run Time, Last Run Result and/or Status.

2) If the option 'Run only if logged' was NOT set in the scheduling properties, then the scheduled tasks failed to run.

3) Tasks that were set to repeat every X minutes in VVScheduler may have failed to run.

All issues are now resolved in ViceVersa PRO 2.5 Build 2519 (or newer) download here and Windows Server 2016 with all the latest updates installed as of August 2017.
User Comments
 Add Comment
There are no user comments for this topic.
Add Comment

Related

 [VVLauncher] Why Do I Get a 'Cannot Monitor Folder' Error When Running VVLauncher as a Service?
 I Get 'Exit Code 2, the system cannot find the path specified' when Running ViceVersa from VVScheduler. Why?
 [VVLauncher] Installing VVLauncher as a Service, I Get the Error that VVLauncher Cannot Access a Network Drive. Why?
 Why Outlook OST files do not copy on Windows Vista, when using VSS Volume Shadow Copies?
 [Error Message] 'Can not copy NTFS Additional File Streams ... The request is not supported.'
Attachments
No attachments

Did this help you?
Yes No

Statistics
58% found this information useful

Other Options
Printable Version

General Information
No. 122
Author: TGRMN Software

Download ViceVersa
Visit ViceVersa Forum
A printable version of the entire ViceVersa FAQ and Knowledge Base is also available.
For further queries, please contact us by E-Mail at support@tgrmn.com.