Keil Logo

LICENSE: Receiving error R214 building a project

Information in this knowledgebase article applies to:

  • C51 Version 8 and later
  • C166 Version 6 and later
  • C251 Version 4 and later
  • MDK-ARM Version 3 and later


When trying to build a project, the Keil IDE gives the license error R214: A Floating user has incorrect Computer Time.

The Keil tools on this PC are registered using a Floating License.


There is an incorrect computer time on a computer that has accessed the Floating License File (FLF).

The clock setting of all FLF users must be within ±15min, e.g., if the current user's timestamp is more than 15 minutes in the future of any other user's previous checkout time, this error is thrown.


Consult your IT group about the server settings and caching issues with the server. Then check the System times on all PCs using the FLF. Convert all system times into UTC format - it will make it easier to see any issues with Time Zones, Daylight Savings, etc.

To get the System Time of a PC in UTC format:

  1. From the Windows start button, find and open Windows PowerShell.
  2. On the PowerShell command prompt, type: get-date -format FileDateTimeUniversal
  3. Have the other FLF users run the get-date -format FileDateTimeUniversal command. Verify everyone is within ±15 minutes of the same universal time.
  4. Decode the result. From PowerShell Get-Date Command:
    "[The result] is in the form of yyyyMMddTHHmmssffffZ (case-sensitive, using a 4-digit year, 2-digit month, 2-digit day, the letter "T" as a time separator, 2-digit hour, 2-digit minute, 2-digit second, 4-digit millisecond, and the letter "Z" as the UTC indicator). An example of results when you use this format is 20180907T1828218703Z."

    So T1828218703Z is 18h :28m :21s :8703ms.
  5. Set the correct system time on the affected PCs.

Consult your company's IT group for solutions. Some possible options could be:


This error may cause licenses to be blocked for 3 hours. If an FLF user advances their Windows Date/Time (e.g. by days, weeks or months) and then checks out a license, this can block every other user until that time is reached in real life.

In such cases, the only solution is to create a new FLF.

  1. Contact Keil and send them the compromised Floating License File.
  2. The Keil Sales team will issue a new Floating License Product Serial Number(PSN) - free of charge.
  3. Have the License Administrator of your company create a new Floating License File on the server.
  4. Have all FLF users register their PCs with the new FLF.



Last Reviewed: Thursday, January 10, 2019

Did this article provide the answer you needed?
Not Sure
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.