The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,733 other followers

Even perpetual Delphi licenses require an active maintenance support or contacting the Sales/Renewal team to allow re-install on a fresh machine

Posted by jpluimers on 2019/06/11

Edit 20190612

It seems all the fuzz sort of got restored: if you have an old product, not under maintenance support, then the registration count has been bumped and can be bumped further through the sales/renewal department.

This got posted a few hours after my blog post got live (the WayBack link does not archive all comments, sorry for that, that’s why I quoted toe comment):

[WayBack] From the GM: New Updates and Changes to the Registration “Bumps” Policy [UPDATED] – Blog – Developer Tools – IDERA Community

Policy Update: We still receive occasional comments on this and want to make sure we are clear on our Policy. Registration limits were introduced a long time ago with very valid use cases, but many of these are now outdated. We still do them, just now they get approved by Account Management (Sales/Renewals) vs. Support. Further, we have done several auto-bumps for everyone that should limit these issues altogether (and will do more as needed). As communicated, over the summer, we will work on a more automated way to increase registration limits through the self-service portal.

Original article 20190611

Last month, people found out that retroactively, Embarcadero has changed the terms of the license agreements on products sold with a perpetual license:

In order to re-install those products, often a bump in license count is needed. That bump now requires an active maintenance subscription which has a substantial yearly cost.

This is yet another sign that Embarcadero parent company Idera is on their way towards becoming like Oracle or Computer Associates: hiding information behind account walls, and by all means trying to squeeze out money of older products.

I think the move is illegal in several countries, especially with products sold to private persons. Uwe Raabe agrees with me on that:

I am not sure they would get away with that – at least here in Germany. As long as the customer actually paid for the perpetual license (this excludes the CE), the ability to use it legally cannot be prohibited just because there is no current support contract. At least a reasonable fee for the registration bump would perhaps be acceptable, but definitely not denying it completely.

If you still own Delphi licenses, and are on maintenance for them, a path you might take is to switch to a local installation (on a separate machine, preferably virtual machine) of the ELC (formerly Belise) licensing server together with a named license.

That requires your machines to be in touch with that ELC service (you can reach it over a network connection, even via a tunnel) every 30 days to stay active.

Another way is to :

  • always install in virtual machines, and keep a backup-history of those virtual machines at hand
  • use different user names for doing different Delphi work (but be aware that a lot of Delphi tools and component suites still insist on installing as Administrator, therefore putting all the settings in that administrative user)

Note that :

  • a Delphi license is bound to a Windows computer NAME, not a physical fingerprint of the machine
  • it is likely easier to keep backups of the ECL/Belise server than of a full development machine
  • ELC/Belise requires Java (JRE 1.5 or higher according to ELC Admin Guide.pdf ), which has it’s own licensing issues
  • Though ELC stands for “Enterprise License Server”, it works for one-man shops equally well as for enterprises (heck: for enterprises it is likely more work as they usually want multiple groups of licenses users)

So renaming a machine will already invalidate your license (but you can usually restore that).

Background reading:

Downloads (.bin files are for Linux x86 or x86_64; .exe files for Windows Win32 or Win64):




Enterprise License Center (ELC) und neue Lizenzen (Update Subscription)

Posted by Matthias E on in Tools
Enterprise License Center (ELC) und neue Lizenzen (Update Subscription)

Es kommen hier fast täglich Fragen zum Enterprise License Center (ELC) und aktualisierten Lizenzen. Daher mal eine kleine Anleitung bzw Hilfestellung, was häufiger für Konfusion sorgt: Man hat sich eine 10.1 Berlin Edition gekauft, die automatisch mit einer Update-Subscription daherkommt. Jetzt muss man (wie bei jedem neuen Release), die Lizenzen aktualisieren, um die letzte, aktuelle Version benutzen zu können.

Ich zeige das hier an einem praktischen Beispiel.


  • Dies betrifft nur Lizenzen, die man aufgrund einer aktiven Subscription verlängern kann oder muss
  • Dies trifft nur auf Netzwerk-Lizenzen zu
  • Dies trifft nur auf den ELC (Embarcadero License Center) Version 4.x oder 5.x zu


  • Man hat sich n Lizenzen von 10.1 Berlin gekauft
  • Man möchte jetzt 10.2 Tokyo installieren
  • Man versucht die SLIP Datei von 10.1 Berlin zu importieren….. und schlägt fehl

Das Problem, was viele Benutzer irritiert: Man versucht auf dem ELC (die Version 5.x kann das automatisch) die Lizenzen zu aktualisieren und sieht weiterhin folgenden Screenshot (Licenses bzw Licenses -> License Files):

Auch wenn man unter Licenses -> License Files auf das “Update licenses” klickt, ändert sich nicht an der Anzeige!

License update status:

-There are no updates found for the license. (<Lizenznummer>)


Unter der Haube wurden die neuen SLIP Dateien angefordert (dies setzt natürlich voraus, daß der Lizenzserver auch Internet-Zugang hat).

Man sieht das auch im Datei-Verzeichnis an dem aktuellen Datum (hier: 20. April 2017):

In diesen Lizenzen steckt auch (bei aktiver Subscription) das letzte/aktuelle Release (10.2 Tokyo). Es wird aber weiterhin “10.1 Berlin” angezeigt. Das mag verwirren. Ist aber leider normal. Es gibt keinen Weg für den Endkunden/Lizenzverwalter herauszufinden, was nun wirklich in den SLIP Dateien steckt….

Die Lizenzen kann man herunterladen (Licenses -> License files -> Download Button (kleiner, blauer Pfeil nach unten).. Das sollte man tun und die darin enthaltene SLIP Datei (NAMED bzw CONCURRENT_xxx.SLIP für die Clientinstallation von Delphi/C++Builder/RAD Studio nutzen)

Ich hoffe, damit für etwas Aufklärung gesorgt zu haben :-)

(Wenn man mir das ZIP Archiv an meine eMail Adresse schickt: Ich kann für Sie / ich kann für euch da reinschauen)


ELC 4.x

Für den ELC 4.x muss man sich die Dateien mit den passenden Zugangsdaten (acct-1234567890 / <geheimes Passwort> [1234567890 ist nur ein Beispiel]) hier herunterladen:


Daher empfehle ich generell den Einsatz vom ELC 5.x (Download siehe weiter oben; Migration ist ist möglich: Die SLIP Dateien sind kompatibel. Achten Sie bitte auf den Port 4467 vs 5567!)


3 Responses to “Even perpetual Delphi licenses require an active maintenance support or contacting the Sales/Renewal team to allow re-install on a fresh machine”

  1. KMorwath said

    Delphi as ransomware, a “new” business model, it looks. That show how much desperate they became, and how many customers they lost and are losing. It won’t help to get more and back, I guess. The last thing you want and need is a totally unreliably “business partner” that attempts to change contracts retroactively. It’s years they are trying any shady attempt to make the remaining users pay more just with licensing changes.

    Quite illegal in most jurisdictions, even Adobe released non-expiring keys when it shut down the registration servers for its products pre-CS3, and when in the past week stopped access to some older versions due to licensing reason, it didn’t touch the perpetual licenses.

  2. maria said

    pretty easy to decompile the slip part.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: