◷ Reading Time: 7 minutes
During execution FlexRule needs to find a license file. You may receive different errors because the license could not be loaded or it is not validated. The errors are found in two different groups:
- Initialization error
- Validity error
In order to make sure runtime can load the license:
- Make sure your license is valid
- Structure your project assemblies and license file
License Initialization Errors
These errors occur when
- FlexRule could not locate or load your license file
- License file is corrupted
- License file is in an invalid format
These errors come with an integer number error code. Here are some codes you may receive:
- Error 30: Invalid license format or it is corrupted
- Error 5: Indicates your license could not be loaded, located
- Error 70,75,80: Internet connection problem
License Validity Errors
You may receive these errors because your license is not valid
- Your trial is finished
- Your machine specification has changed
- License is not for the right version you are using, etc.
These errors come with a GUID reference number. For more detailed information, check License validation errors
Setup assembly with license
The assembly that is referencing FlexRule libraries must also sign in with the license. That is as simple as adding an assembly level attribute to your project AssemblyInfo.cs file.
Simply add the following definition to your AssemblyInfo.cs:
[assembly: FlexRule.License.LicenseProviderAttribute(typeof(FlexRule.License.FileBasedLicenseProvider))]
License Validation
This is a process that tests your actual license and if for any reason it fails, it throws an exception with a code. Each of the error codes indicates the area of the problem.
For example, if you get a “Visual studio” error code, that might show you are running a license that does not allow you to run VS on the machine.
Features codes
If a feature is not enabled by your license, you may get one of the following error codes. That means you cannot run a particular feature. However, based on your license you are still able to work on other functional areas.
2591462c-dba5-4da1-8d55-6827a379144c 4551f867-5f27-42b1-9565-c4f76c2b854a 017a4389-1f5f-4688-a32a-64f36d7ca6d6 f1348653-2114-4516-b484-7e7b05713e8d b6342fd0-d47f-420b-a919-ed39afa37014 5dd29305-89e4-476d-bd63-20993f8f982c 9758fd3b-00eb-48f7-80fc-0075f809d4ee 9ae4f512-e417-44aa-9869-2c4a779fc7e8 a2215c96-4992-4e0b-9fef-85b42cdc3b7e 41d75ecd-a2c0-4ed7-9e5b-15d9a254892f 5ae51448-8ee2-443e-b90d-961032786468 5c93577e-cb97-4199-b1b5-3d84cd20847d 45b51bd0-313f-4e83-a5ed-9c0bf1ce1887 d7c25646-97fa-41db-beb9-4ebe06a0f482 b875db67-2ce5-4c74-a749-06f06463c2df 5de86d73-e350-4d0e-a540-c27d732c870f 022051ac-e3c2-4406-83db-4fa1c01a453d 75fb3b62-da4c-4644-9e4e-43fe96e6140f 767cd1d1-d661-4845-9bf0-cdbb860377c5 870a5271-b32f-4dc8-a21c-786c4166f279 db7f446a-753c-40bc-bbaa-a8a0e0559ad7 ac795ea8-0981-4e79-a142-3a106ca34f3e e2e3d854-9eb1-445c-bd3b-69ef907fc2c6 e302b78a-d60c-4f63-9070-08828c1135b1 a23cb550-44bb-4baa-9834-8f488e7cc8f3 c3c1c6e0-6677-4f31-bb3d-9f270d7e819a
Visual studio codes
If you have VS installed or running, you may receive the following error codes.
| 074f0665-b91c-4789-97a0-d8b23b8d9d89 | VS is installed on this machine |
| d32837ff-a7d1-4a26-b1fc-413a2732deb7 | VS is running |
| 4d5c2512-91a0-4781-8804-5e1a52edd04a | VS Debugger is attached |
Machine, version and date codes
Generic license error that you may receive because of timing, version mismatch or assembly identity match.
| ec169a71-a4dd-4f62-8956-8f874379487a | Machine id mismatch |
| b1dd3cc2-a56c-48ff-bac9-afc759612fad | Version mismatch |
| de3e5b3b-8d7f-41e0-b6c1-206bd74a0f66 | Date has expired |
| 8ee010e5-61d2-44a4-8c4c-05970f7ea1bf | File signature mismatch |
| ed313666-f586-4dea-a3be-8a9cb5953e48 | Machine id mismatch |
| 0fc2f14c-be60-4db9-b361-c74cb232f057 | Machine id mismatch |
Machine id mismatch
Each license is unique to the machine. You will get this error if you use a license that is not assigned to the specific machine. For example, if you use a new machine with a license copied from your old machine.
As the solution, contact the support team with your new machine’s serial number.
Version mismatch
FlexRule licenses are version-specific.
For example, if you are using Runtime version 9 in Designer, and try to use version 8 Runtime license, you will get the following version mismatch error.
As the solution, download the correct license version from the FlexRule user portal.
Hosting environment codes
The way you host the rules may not be allowed by your license (i.e., WCF, WebAPI, Remoting, etc.). In these cases you may receive one of the following errors:
0800cef5-23ba-4f06-a603-7ddd79d146c6 f571b9eb-0d36-4375-ba77-810b3f2402e4 45cd952c-9be3-4dda-a79b-2787d7e0137e 07890d8d-500c-410f-a620-c76ff9005352 71e017ad-4ae5-43a8-9686-ce35c3cefbcf 5a336946-901b-48b5-88f5-c173d75a347f 757f3312-0451-446e-bfbc-7c7eb9dcecc8 89bf1ba3-1c06-4cbc-8758-15bf3945f964 364b66a0-041b-438d-873c-1a7e12719d80 dac64d8c-af8d-4251-8f1e-7c9ea1b7b563
Operating system codes
Your license may not allow you to run your application on some operating systems (OS). If that is the case, you may receive one of the following error codes:
d2308baf-663c-4397-8812-3bd7d61accfa e58bacac-f8f4-49c8-bf06-290ba310b918 fbddb4f2-a25e-4338-a5d5-eae00cc4f50a 06c9d43a-4e47-43fb-9280-54849a98e183 9185e97c-64b7-495c-b35e-1771b4116e4d 319f5af1-7235-4dcd-9065-fff4cddc40f2 975031a8-0146-47dc-9bb8-4457dad56153 6006020b-6b51-418d-aafb-69f08dd76654 400ad172-122b-469b-a78a-5d27162a6552 a37a58ca-7398-4bbd-9cb8-2ad2182142ef fe746fcb-ad56-4621-ad1e-77f5008dde21 b7eea249-9878-4c44-bb56-975d66cc886f 07be84f8-7e21-4dc3-afbc-2d4814152e30 1cc09e2d-5474-40cc-ad2d-ab23fc19c83e a6e0045a-8d9f-4958-9205-7b1b0a736ab4 132dc51b-b1a8-408c-b76d-ad3a700e5811 3f711109-4cdd-481d-9c27-faba39d5bbc5