Hello thebaz67,
Sometimes the method used to migrate data over can be the cause of such a problem. For example if you migrate the entire /usr/local/openvpn_as/ directory as a whole from the old server to the new server. That could confuse package managers when installing programs that are in that same directory - they might go 'oh the directory is already there' and not do their tasks. And in the past, with older Access Servers, that directory contained different things (only connect v2, and not connect v2 + connect v3). So you might have ended up with an inconsistent state for that directory when going to a newer version of AS. There may also be other ways it got messed up. I'm glad you were able to find the solution here on this forum. It is fortunately something that is relatively easy to resolve if those files are missing for some reason or another.
Just for reference, here is the guide on how to migrate data from one Access Server installation to another. It might help someone else to avoid a similar issue, possibly:
https://openvpn.net/vpn-server-resources/migrating-an-access-server-installation/
And for future readers with the exact same problem, here's a way to force a reinstall of the openvpn-as-bundled-clients package on an already installed Access Server that runs on Ubuntu/Debian (as root user):
apt --reinstall install openvpn-as-bundled-clients
Kind regards,
Johan
