Emerson Exchange 365

• Not Answered

Dongle not getting detected in particular System

The dongle when i plug in to the usb ports of particular system , not getting detected by the system , but getting detected in another system with same dongle Checked in WATCHIT , the error is LIC_SYSTEM_CLOCK_SET_BACK The issue came after i have installed a Symantec Antivirus software .I tried uninstalling and checked but still not working System time and zone settings was the same as ,what it was , when DeltaV Installed Please give me a solution Thankyou

Jibumc

• 26 Apr 2018 6:13 PM
• Cancel

3 Replies

• Neil Castro

  

  • 27 Apr 2018 10:48 AM

  I guess you are using an SI Dongle.
  
  On the system that shows LIC_SYSTEM_CLOCK_SET_BACK there is a big chance that you, someone, or something (Symantec) changed the machine time to a future date/time then return it to the correct date/time.
  
  In case this is a development or a demo system I recommend starting on a fresh OS with the correct date and time while installing the OS and DeltaV.
  
  In case this is a live system then you may want to insert the license Dongle (non-SI Dongle) intended for the system. The licensed Dongle is not time sensitive.
  
  Hope this helps.
  
  Regards,
  Neil Castro

  • Cancel
• Andre Dicaire

  

  • 27 Apr 2018 2:30 PM

  In reply to Neil Castro:

  The Licensed system dongles are also time aware for the temporary engineering seat licenses that can now be purchased for DeltaV. Manipulation of the system time should not affect the operation of the dongle in general, but could cause any time based licenses to be unavailable. Of course, if you don't have any such licenses, than there would be no impact there.
  
  Manipulating the system time can also disrupt the History data storage. If you set time to future date, say a week in the future, and after an hour, restored normal time, there would be a gap of data for the hour time was set forward, and when the week elapsed to the start of the "future hour", there would be records overlapping for the real data and the data from a week ago, so you'd lose two hours of data. This would also mess up the Dataset time spans if the future time stamp was further than the current data set can collect into. With PI, it would result in disabling data compression and cause every value to be stored as "back in time" data, filling archive files quickly and slowing data retrieval as the quantity of data points would be orders of magnitude larger than normal.
  
  Point is, do not manipulate system time into the future for "test" purposes on a production system, and be prepared to reinstall OS to restore normal operation.

  Andre Dicaire

  • Cancel
• Neil Castro

  

  • 27 Apr 2018 11:51 PM

  In reply to Andre Dicaire:

  Thanks Andre for the new information. :-)
  
  This shows that I have been away from new DeltaV features. I need to either read documentations from Emerson that is new to me or go back to technology work.
  
  Regards,
  Neil Castro

  • Cancel