Answer: This behavior can be caused by a defect in RSM R16.x which is fixed in R17.0. If the RSM User Proxy log (located in the temp-directory) contains one of the following error messages •Exception getting UserProxy interface: Exception getting UserProxy interface: Access denied to UserProxy running as … •Failed to decrypt token: The padding is invalid and can’t be removed, the failure is likely caused by this defect. In this case, try the following workaround: •The functionality that might lead to the error can be turned off by setting the environment variable ANSYS_RSM_UPDEV. •On Linux machines, this should be done in the file …/AnsysBaseDir/v16x/RSM/Config/tools/linux/rsmuserproxy: Insert the lines ANSYS_RSM_UPDEV=1 export ANSYS_RSM_UPDEV in the following location: … ANSYS_RSM_UPDEV=1 export ANSYS_RSM_UPDEV RUNWB2=”$AWPROOTDIR/Framework/bin/$PLATFORM/runwb2″ echo $RUNWB2 -cmd mono $AWPROOTDIR/RSM/bin/Ans.Rsm.UPHost.exe $* $RUNWB2 -cmd mono $AWPROOTDIR/RSM/bin/Ans.Rsm.UPHos •On Windows machines, this should be done in the file C:Program FilesANSYS Incv161RSMConfigtoolswinrsmuserproxy.cmd: Insert the line set ANSYS_RSM_UPDEV=1 in the following location: … echo RSM_HOME=%RSM_HOME% set ANSYS_RSM_UPDEV=1 … •The modification must be done on the RSM manager machine and on the client machines. It is not required to implement the modification on all client machines at once. I.e., to test if it resolves the problem, it is possible to implement the modification only on selected clients. •A restart of the RSM services is not required, but the UserProxy processes must time out. With the standard settings, this happens after 10 minutes inactivity of the UserProxy process (i.e. no RSM data up-/downloads of the user).