License error license exhausted cannot allow another user

License error license exhausted cannot allow another user

Error on a Kerio Connect firewall: license error: license exhausted, cannot allow another host

Looks like the customer’s firewall license expired a few months ago and we are getting weird network issues. We suspect that when the license expired it limits the number of machines on the network that can reach the outside. But we are struggling to find documentation to back this up. Does anyone know how Kerio behaves if the license expires? From what we can approximate, it might limit you to twenty five network devices?

Kerio Connect is their email product. Do you mean Kerio Control?

Also, found this on GFI’s forum from 2014.

Based on the couple posts I have seen, each registered user can have five devices. So, if they have 30 devices, they need 6 user licenses. Did they add any extra devices lately?

Kerio Connect is their email product. Do you mean Kerio Control?

Yes, fixed it. Wrote that while on the phone.

Based on the couple posts I have seen, each registered user can have five devices. So, if they have 30 devices, they need 6 user licenses. Did they add any extra devices lately?

Easily, but more likely they just let their license expire.

Источник

License error license exhausted cannot allow another user

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I have a domain that was successfully running with two Windows 2003 DCs. I added a Windows 2008 R2 DC to the network successfully. I demoted (removed) one of the 2003 DCs. I added a Windows 2008 R2 Terminal Server to the network. I added the TS Licensing Server as well. I activated the Licensing Server and installed my User CALs. All seemed to work well until I looked at the error log. Whenever a non-administrator user logs in to the TS machine I get an error in the errror log telling me that

The Remote Desktop license server cannot update the license attributes for user «USER» in the Active Directory Domain «DOMAIN». Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain «DOMAIN».

I do not get this error when an administrator logs in via TS.

When I look at the Security Groups in the DC for the domain there is a Builtin Security Group called «Terminal Server License Servers» and it has the terminal services computer (which is the same as the license server) listed in the group.

How do I fix this?

Answers

1. Logon to your 2008 R2 DC as an administrator
2. Start—Run—adsiedit.msc
3. In the left pane, navigate to where the OU for your users is located
4. In the left pane, right-click on CN= and choose Properties
5. On the Security tab, click the Advanced button
6. Click the Add button, type Terminal Server License Servers and click OK
7. On the Properties tab, select Descendant User objects in the Apply onto box
8. In the Permissions box, select Allow for all of the following:

Read msTSExpireDate
Write msTSExpireDate
Read msTSLicenseVersion
Write msTSLicenseVersion
Read msTSManagingLS
Write msTSManagingLS

9. Click OK, and click OK again to save your changes

Please test by having a standard user logon to your RDS. After the user has logged on, check the event logs of the server, there should not be a event id 4105 Warning for the user in the System log, and there should be a event id 4143 Information entry for the user under Microsoft-Windows-TerminalServices-Licensing/Admin log.

• Proposed as answer by TP [] MVP Friday, May 7, 2010 8:45 AM
• Marked as answer by Lionel Chen — MSFT Wednesday, May 12, 2010 9:14 AM

All replies

It is a problem with the read / write users in the group «Terminal Server License Servers.» This group does not exist in Windows Server 2000 and appears with WS2003. If your domain was originally Windows 2000, and migrated to Windows 2003 and now has migrated to WS2008, it is possible that this is your problem.

Colobora con el foro: Si la respuesta es de utilidad para resolver tu duda/problema, usa la opción «Marcar como repuesta». Otros usuarios con dudas similares -en un futuro- lo agradecerán.

Is this what you get in Events? If so, can you please let me know if there is any warning or error shown in the ‘Review Configuration’?

Remote Desktop Services Team Blog: http://blogs.msdn.com/rds

1. Logon to your 2008 R2 DC as an administrator
2. Start—Run—adsiedit.msc
3. In the left pane, navigate to where the OU for your users is located
4. In the left pane, right-click on CN= and choose Properties
5. On the Security tab, click the Advanced button
6. Click the Add button, type Terminal Server License Servers and click OK
7. On the Properties tab, select Descendant User objects in the Apply onto box
8. In the Permissions box, select Allow for all of the following:

Read msTSExpireDate
Write msTSExpireDate
Read msTSLicenseVersion
Write msTSLicenseVersion
Read msTSManagingLS
Write msTSManagingLS

9. Click OK, and click OK again to save your changes

Please test by having a standard user logon to your RDS. After the user has logged on, check the event logs of the server, there should not be a event id 4105 Warning for the user in the System log, and there should be a event id 4143 Information entry for the user under Microsoft-Windows-TerminalServices-Licensing/Admin log.

• Proposed as answer by TP [] MVP Friday, May 7, 2010 8:45 AM
• Marked as answer by Lionel Chen — MSFT Wednesday, May 12, 2010 9:14 AM

We are on a Windows 2003 AD domain with only 2003 DC’s. Your steps references a Windows 2008 R2 DC. What is the process to resolve this in our Windows 2003 AD domain?

I will assume that you have not updated your AD schema to version 2008, please let me know if you have since the steps will be slightly different. Below are the instructions for working on your 2003 DC with a 2003 schema:

1. Logon to your 2003 DC as an administrator
2. Make sure your TS Licensing server is a member of the Terminal Server License Servers group using ADUC
3. Download and install the windows support tools on your 2003 DC (if you have not already):

4. Start—Run—adsiedit.msc
5. In the left pane, navigate to where the OU for your users is located
6. In the left pane, right-click on CN= and choose Properties
7. On the Security tab, click the Advanced button
8. Click the Add button, type Terminal Server License Servers and click OK
9. On the Properties tab, select User objects in the Apply onto box
10. In the Permissions box, select Allow for all of the following:

Read terminalServer
Write terminalServer

11. Click OK, and click OK again to save your changes

Please test by having a standard user logon to your RDS. After the user has logged on, check the event logs of the server, there should not be a event id 4105 Warning for the user in the System log, and there should be a event id 4143 Information entry for the user under Microsoft-Windows-TerminalServices-Licensing/Admin log.

Источник

[Закрыто] Проблемы с менеджером лицензий и Расшифровка Кодов ошибок

TechnologiCS → TechnologiCS → Установка/настройка → Проблемы с менеджером лицензий и Расшифровка Кодов ошибок

Чтобы отправить ответ, вы должны войти или зарегистрироваться

Сообщения 1

#1 Тема от Елена Кузнецова 16 января 2009 13:54:41

• 
• Елена Кузнецова
• Участник
• Неактивен

• На форуме с 2 декабря 2008
• Сообщений: 97

Тема: Проблемы с менеджером лицензий и Расшифровка Кодов ошибок

Если у вас возникли проблемы с менеджером лицензий, пожалуйста используйте следующую последовательность действий.

Внимательно прочитайте сообщение менеджера лицензий. Возможно у вас просто исчерпан лимит подключений или нет связи с сервером лицензий CSoft Development.

Если сообщение отсутствует, но есть код ошибки, поищите его среди приложенных ниже описаний. Возможно это подскажет вам путь решения проблемы.

Внимательно просмотрите лог файл менеджера лицензий, там содержится подробная информация о ходе его работы. По умолчанию лог файл находится в файле C:Program FilesCSoftCS License Serverflex.log или C:Program Files (x86)CSoftCS License Serverflex.log для x64 ОС.

Если выше перечисленные шаги не помогли разобраться вам самостоятельно, отправьте запрос с подробным описание ошибки на адрес soft@csoft.ru не забыв приложить лог файл и файл лицензий.

С уважением, служба технической поддержки TechnologiCS.

Коды ошибок менеджера лицензий

Errors marked with an ‘*’ indicates errors which should not appear in shipping software. These are errors intended to help the programmer incorporate FLEXlm in their product, and should be fixed before shipping.
Errors marked with ‘+’ indicate errors due to an operating system failure.

Error Description

-1 Cannot find license file
-2 Invalid license file syntax
-3 No server for this feature
-4 Licensed number of users already reached
-5 No such feature exists
-6 No port number in license file and FLEXlm service does not exist [pre-v6only]
-7 No socket connection to license manager server
-8 Invalid (inconsistent) license key.
The license-key and data for the feature do no match.
This usually happens when a license file has been altered
-9 Invalid host.
The hostid of this system does not match the hostid
specified in the license file
-10 Feature has expired
-11 Invalid date format in license file
-12 Invalid returned data from license server
-13 No SERVER lines in license file
-14 Cannot find SERVER hostname in network database.
The lookup for the hostname on the SERVER line in the
license file failed. This often happens when NIS or DNS
or the hosts file is incorrect. Workaround: Use IP-Address
(e.g., 123.456.789.123) instead of hostname
-15 Cannot connect to license server.
The server (lmgrd) has not been started yet, or
the wrong port@host or license file is being used, or the
port or hostname in the license file has been changed.
-16 Cannot read data from license server
-17 Cannot write data to license server
-18 License server does not support this feature
-19 Error in select system call
-20 [Obsolete]
-21 License file does not support this version
-22 Feature checkin failure detected at license server
-23 License server temporarily busy (new server connecting)
-24 Users are queued for this feature
-25 License server does not support this version of this feature
-26 Request for more licenses than this feature supports
-27 [Obsolete]
-28 [Obsolete]
-29 Cannot find ethernet device
-30 Cannot read license file
-31 Feature start date is in the future
-32 No such attribute
-33 Bad encryption handshake with daemon
-34 Clock difference too large between client and server
-35 In the queue for this feature
-36 Feature database corrupted in daemon
-37 Duplicate selection mismatch for this feature
-38 User/host on EXCLUDE list for feature
-39 User/host not on INCLUDE list for feature
-40 Cannot allocate dynamic memory
-41 Feature was never checked out
-42 Invalid parameter
-43 *No FLEXlm key data supplied in initializing call
-44 *Invalid FLEXlm key data supplied
-45 *FLEXlm function not available in this version
-46 [Obsolete]
-47 Clock setting check not available in daemon
-48 *FLEXlm platform not enabled
-49 *Date invalid for binary format
-50 *FLEXlm key data has expired
-51 *FLEXlm not initialized
-52 FLEXlm vendor daemon did not respond within timeout interval
-53 Checkout request rejected by vendor-defined checkout filter
-54 No FEATURESET line in license file
-55 Incorrect FEATURESET line in license file
-56 Cannot compute FEATURESET data from license file
-57 +socket() call failed
-58 [Obsolete]
-59 Message checksum failure
-60 Server message checksum failure
-61 Cannot read license file data from server
-62 Network software (tcp/ip) not available
-63 You are not a license administrator
-64 lmremove request before the minimum lmremove interval
-65 *Unknown VENDORCODE struct type passed to lm_init()
-66 *FLEXlm include file/library version mismatch
-67 [Obsolete]
-68 [Obsolete]
-69 [Obsolete]
-70 [Obsolete]
-71 Invalid TZ environment variable
-72 *Old VENDORCODE (3-word) struct type passed to lm_init()
-73 Local checkout filter rejected request
-74 Attempt to read beyond end of license file path
-75 +SYS$SETIMR call failed (VMS)
-76 Internal FLEXlm Error — Please report to Globetrotter Software
-77 Bad version number — must be floating point number, with no letters
-78 *FLEXadmin API functions not available
-79 FLEXlm internal error -79
-80 FLEXlm internal error -80
-81 FLEXlm internal error -81
-82 Invalid PACKAGE line in license file
-83 FLEXlm version of client newer than server
-84 USER_BASED license has no specified users — see server log
-85 License server doesn’t support this request
-86 License object already in use (Java only)
-87 Checkout exceeds MAX specified in options file
-88 System clock has been set back
-89 This platform not authorized by license
-90 Future license file format or misspelling in license file.
The file was issued for a later version of FLEXlm than this
program understands.
-91 ENCRYPTION_SEEDs are non-unique
-92 feature removed during lmreread, or wrong SERVER line hostid
-93 This feature is available in a different license pool.
This is a warning condition. The server has pooled one or more
INCREMENT lines into a single pool, and the request was made on
an INCREMENT line that has been pooled.
-94 Attempt to generate license with incompatible attributes
-95 Network connect to THIS_HOST failed.
The license file indicates THIS_HOST, and the server is
not running on this host. If it’s running on a different host,
THIS_HOST should be changed to the correct host.
-96 Server node is down or not responding.
See the system administrator about starting the server, or make
sure the you’re referring to the right host (see LM_LICENSE_FILE).
-97 The desired vendor daemon is down.
1) Check the lmgrd log file, or 2) Try lmreread.
-98 This FEATURE line can’t be converted to decimal format
-99 The decimal format license is typed incorrectly
-100 Cannot remove a linger license
-101 All licenses are reserved for others.

The system administrator has reserved all the licenses for others. Reservations are made in the options file. The server must be restarted for options file changes to take effect.

Источник