Background:
When using the MPICH distributed parallel feature in CFX 5 on a Windows network, the MPICH daemon must be installed on all the hosts involved in the run. ADDITIONALLY on the MASTER node, details of a user with access to all the hosts must now be set. (DOMAIN username & password). [Refer to the User Manual for more details]
Problem:
Every time the WINDOWS DOMAIN user name and/or password is changed (which most networks require every 30 days etc.), the details should be reset on the MASTER node. On some machines, everything works fine on initial setup. BUT after the password is changed, when trying to reset the MPICH user registration, it causes an error as detailed below:
1) User un-registers info using "cfx5parallel -unregister-mpich-user" from the command line.
2) User changes password, and logs into his master node.
3) User tries to re-register with new password:
-------------------------------------------------------------------------
>cfx5parallel -register-mpich-user
Starting the MPICH User Registration tool. You will need to give a user
account and password which can be used to log into the other machines in a
distributed parallel run. For network users, you can include the domain
name and a backslash preceding the user, eg "BEDROCKFred". If you do not
choose the information to be persistent, you will have to re-do this
process every time the machine is rebooted.
No user information is currently registered.
account: akpaul
password:
confirm:
Do you want this action to be persistent (y/n)? y
SetupCryptoClient:CryptAcquireContext(...) failed, error: -2146893809
Error Text: Object already exists.
Error: Unable to setup the encryption service.
The new password was not successfully encrypted.
------------------------------------------------------------------------
NOTE: A similar error happens if the user tries to re-register without un-registering first.
Solution:
According to the MPI maintenance team at Argonne Nationa
|
Background: When using the MPICH distributed parallel feature in CFX 5 on a Windows network, the MPICH daemon must be installed on all the hosts involved in the run. ADDITIONALLY on the MASTER node, details of a user with access to all the hosts must now be set. (DOMAIN username & password). [Refer to the User Manual for more details] Problem: Every time the WINDOWS DOMAIN user name and/or password is changed (which most networks require every 30 days etc.), the details should be reset on the MASTER node. On some machines, everything works fine on initial setup. BUT after the password is changed, when trying to reset the MPICH user registration, it causes an error as detailed below: 1) User un-registers info using "cfx5parallel -unregister-mpich-user" from the command line. 2) User changes password, and logs into his master node. 3) User tries to re-register with new password: ------------------------------------------------------------------------- >cfx5parallel -register-mpich-user Starting the MPICH User Registration tool. You will need to give a user account and password which can be used to log into the other machines in a distributed parallel run. For network users, you can include the domain name and a backslash preceding the user, eg "BEDROCKFred". If you do not choose the information to be persistent, you will have to re-do this process every time the machine is rebooted. No user information is currently registered. account: akpaul password: confirm: Do you want this action to be persistent (y/n)? y SetupCryptoClient:CryptAcquireContext(...) failed, error: -2146893809 Error Text: Object already exists. Error: Unable to setup the encryption service. The new password was not successfully encrypted. ------------------------------------------------------------------------ NOTE: A similar error happens if the user tries to re-register without un-registering first. Solution: According to the MPI maintenance team at Argonne National Labs (ANL), this seems to be a bug with the mpich registration code, which shows up on some machines. They have provided us with the attached fix to clear all registry entries. After running the attached fix (executable), users should be able to re-register the details without any problem. This process will have to be repeated every time the user change their DOMAIN password. |
||
|