Smarts: Unable to start any Smarts services because the system clock was changed.
search cancel

Smarts: Unable to start any Smarts services because the system clock was changed.

book

Article ID: 303786

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:




Unable to start any Smarts services because the system clock was changed
After correcting the system clock, the physical servers were rebooted several times but Smarts domain log files still report licensing errors similar to the following:

[06-Jan-2009 8:25:48 AM+718ms Central Standard Time] t@4860 dmboot
RSRV-E-ELICENSE-Unable to obtain license
 LIC-ECHECKOUT-While attempting to check out license for AP_ICSRV
 LIC-EGENERIC-License file does not support this version.
  . Feature:       AP_ICSRV
  . Application version > License version: 3.00 > 1.1
  . License path:  D:\InCharge7\License\smarts.lic
  . FLEXnet Licensing error:-21,126.  System Error: 2 ""
  . For further information, refer to the FLEXnet Licensing End User Guide,
  . available at "www.macrovision.com".



Environment

VMware Smart Assurance - SMARTS

Cause

This is caused by system files that reflect incorrect timestamps.

Resolution

To resolve this issue:
  1. Search through the filesystem that Smarts is installed on, as well as your entire root directory, and find all files that have a timestamp which is in the future.
  2. Re-save all of these files with today's date.
  3. Ensure that the license file is located in the path specified in the License path that is indicated in the error. If this is not the intended path to the license file, edit the SM_LICENSE environment variable in the Smarts runcmd_env.sh file to point to the correct location of the license file.
  4. Ensure the Windows registry key also reflects the correct path to the license file:

    HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager\SM_LMGRD92_LICENSE_FILE
  5. Once the above steps are taken, restart the Smarts services.

If the above steps are taken and are still unable to start Smarts services, contact EMC Technical Support and reference to this Knowledgebase solution (53821 ).