Hi Eduard,

another step further...

The installation worked. but the error with cryptodomex is still present.
It doesn't matter, the functionality should still be there.

Thanks for your help.

E:\HealthConnect\20201\bin>irispip install e:\HealthConnect\20201\Mgr\python\pycryptodome-3.18.0-cp35-abi3-win_amd64.whl --target e:\HealthConnect\20201\Mgr\python\ pycryptodome --no-binary :all --no-index
Processing e:\healthconnect\20201\mgr\python\pycryptodome-3.18.0-cp35-abi3-win_amd64.whl
Installing collected packages: pycryptodome
Successfully installed pycryptodome-3.18.0

E:\HealthConnect\20201\bin>irispip install e:\HealthConnect\20201\Mgr\python\pycryptodome-3.18.0-cp35-abi3-win_amd64.whl --target e:\HealthConnect\20201\Mgr\python\ pycryptodomex --no-binary :all --no-index
Processing e:\healthconnect\20201\mgr\python\pycryptodome-3.18.0-cp35-abi3-win_amd64.whl
ERROR: Could not find a version that satisfies the requirement pycryptodomex (from versions: none)
ERROR: No matching distribution found for pycryptodomex

With kind regards

Armin

Hi Eduard,

Thanks, then I am not completely wrong after all :) 

my understanding is that the CryptodomeX is the same package as the Cryptodome package. 
The difference is that the Cryptodomex package must be addressed as "Cryptodome" in the code. And without this parameter the package can be used as a "fork" for the Crypto package. Therefore it can be called later as "crypto".

See: https://pycryptodome.readthedocs.io/en/latest/src/installation.html

 When I try to do this, it still tries to connect to the Internet. This then ends in a timeout.

E:\HealthConnect\20201\bin>.\irispip install E:\HealthConnect\20201\Mgr\python\pycryptodome-3.18.0-cp35-abi3-win_amd64.whl --target e:\HealthConnect\20201\Mgr\python pycryptodomex --no-binary :all
Processing e:\healthconnect\20201\mgr\python\pycryptodome-3.18.0-cp35-abi3-win_amd64.whl
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', ConnectionResetError(10054, 'Eine vorhandene Verbindung wurde vom Remotehost geschlossen', None, 10054, None))': /simple/pycryptodomex/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', ConnectionResetError(10054, 'Eine vorhandene Verbindung wurde vom Remotehost geschlossen', None, 10054, None))': /simple/pycryptodomex/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', ConnectionResetError(10054, 'Eine vorhandene Verbindung wurde vom Remotehost geschlossen', None, 10054, None))': /simple/pycryptodomex/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', ConnectionResetError(10054, 'Eine vorhandene Verbindung wurde vom Remotehost geschlossen', None, 10054, None))': /simple/pycryptodomex/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', ConnectionResetError(10054, 'Eine vorhandene Verbindung wurde vom Remotehost geschlossen', None, 10054, None))': /simple/pycryptodomex/
ERROR: Could not find a version that satisfies the requirement pycryptodomex (from versions: none)

We had the case that the ACK of an operation always changed in case of an error and the following messages always threw an error although everything was ok. A restart has then always helped until the next error.
Solution was to catch the ACK in the router and check it. If the error was found a TRACE was executed in which ##class(Ens.Director).EnableConfigItem() was called.

Return Value is the status ;)