Annoying problem with Qt Creator software after update
-
C Christian Ehrlicher moved this topic from General and Desktop
-
I guess the update has switched the license server from using a local file to checking the license online.
Tryqtlicd.exe --mode cli --log-level silly -
@Axel-Spoerl said in Annoying problem with Qt Creator software after update:
qtlicd.exe --mode cli --log-level silly
where do i write this?
-
On the command line. The executable is in your Qt installation directory under
...\Tools\LicenseService.
My guess is that your internet connection / firewall doesn't allow the license server to call home.
If the log output supports this assumption, you can set the environment variableQTLICD_LICENSE_IMPORT_PATHto your local license file. -
i have no "LicenseService"
-
In
Qt\LicenseService? -
found it, what do i do here?
-
@Axel-Spoerl there is no
qtlicd.exeinside that folder -
That’s the license directory, not the one I asked you to look up.
Here it is on my PC:
-
@Axel-Spoerl weird i dont have that folder...
-
How have you installed Qt Creator then?
-
@Axel-Spoerl Qt Online Installer for Windows (x64)
-
@Axel-Spoerl i uninstalled Qt and about to install it again but i dont see the "Licenses Manager Tools" in the installer
-
@Kris-Revi said in Annoying problem with Qt Creator software after update:
i uninstalled Qt and about to install it again but i dont see the "Licenses Manager Tools" in the installer
By default, Qt License Service is automatically installed as an on-demand service when you install any Qt or Quality Assurance product with Qt Online Installer.
However, sometimes you might need a different launching method for Qt License Service. In these cases, you can install Qt License Service manually. Manually installed Qt License Service can operate either as a system service, as an on-demand service, or as a user-space process.
( https://doc.qt.io/qtlicenseserver/qls-how-to-install-service.html )
And... I mean... If you don't find it, it can't be stuck or the reason why your QtCreator isn't working properly, right?!
