Are you starting the same shortcut on the client PC multiple times, or are these different shortcuts ?  If these are different, can you show us the target commands ?

This only happens to me when I use different WindX versions (say v12 and v16) on the client PC to connect to the host.  So if the first connection uses WindX v12 and the second (and all following) one(s) use v16, it will consume 2 licenses.

AFAIK, that listbox shows registered ActiveX controls that have a 'Control' subkey.  In other words, when you start REGEDIT and go to HKEY_CLASSES_ROOT\WOW6432Node\CLSID, all keys in there that have a 'Control' subkey, like for example:

HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{CA8A9780-280D-11CF-A24D-444553540000}\Control

(Adobe PDF Reader).  So if one PC shows sigsign.sigsignctrl.1 and another one shows sigplus.sigplusctrl.1, I would expect the registry entries to be different.

When you connect to the server and click the icon in the upper left corner of the window and select 'About PxPlus' in the menu that appears, does it show serial number 799995 or something else ?

Allright - change line 20 to:

0020 OPEN (CHAN,OPT="CONNECT="+"'"+CONNSTRING$+"'")"[ODB];;"

(add ;; after [ODB]).

Are you using a 64-bit PxPlus (as you're using the 64-bit ODBC driver) ?

One more thing: the 'Starting directory' *must* be your docroot directory, for example c:\apps\coasttec\docroot .

You're correct - the EzWeb install program installs a server for iNomads.  I've attached a slightly changed version called 'webster' (save as *ezweb/webster) that will install/update/delete an EzWeb server for Webster+.  I've used the v20.10 *ezweb/install program source.

I'm getting the same messages in the log file when I run the EzWeb server as a service on Windows 11.  The EzWeb service still  works as expected and the Winsock messages only appear once after every start of the server (so I assume these are for information purposes only).  What happens when you try to run one of the included transactions, for example http://127.0.0.1:8088?txid=test .

Without knowing what's in the PFILEBOX program, it's impossible to tell why this isn't working all of the time.  Also, your PxPlus version looks pretty old (I'm guessing v11 or older) - you could check if the problem still happens when using a current version of PxPlus.

Can you explain what you mean by "uploading a file in the system" ?  Are you using iNomads or the webserver or Webster+ ?  Or is it an FTP upload ?  Do you have a screenshot of the popup ?

As this appears to be a Nomads application, can't you use a concurrent window instead of spawning a new (but completely separate) session ?

A temporary work-around is to downgrade the mariadb3 package to version 3.1.13-3.30.1 - the PxPlus MYSQL interface works correctly with that version.

PvxPlus Technologies is looking into this.

Can you tell me the Linux version that you are using (I assume it's the 64-bit version of both the OS and PxPlus) ?