Node-Locked License Failures Caused by a System Clock Set Back

Cause

For security reasons, the FLEXnet software outputs the error The system clock has been set back. if there is a file that is set to a date later than the current OS’s system date. This can be caused by changing the system date of the OS to the past or by files received from other users.

Solution

Windows.

1. Open File Explorer.
   
2. Click [View] > [Options].
   
3. Click [Show hidden files, folders, and drives].
   
4. Disable [Hide protected operating system files].
5. Press the [Apply] button and exit.
6. In the search box at the top of the Explorer window, type modified:>[search start date] modified:<[search end date].
7. Open Windows PowerShell as administrator.
8. Replace the creation dates of the files identified in step 6 with a date earlier than the current date using the (Get-Item [file path]).CreationTime=([creation time to replace]) command.
   
9. Replace the modification dates of the files identified in step 6 with a date that is older than the current date and earlier than the creation date using the (Get-Item [file path]).LastWriteTime=([CreationTime to replace]) command.