Dim10: After upgrade to Dimensions 10.1.2, error of PRG5401204E Failed to initialize server context occurs when logging into Desktop Client and Web Client
In desktop client logon screen, entering database name in the DB Name field with a space at the end of the db name will produce: "ACL4500016e error Failed to start Dimensions server process on host 192.168.92.60." Dimensions should ignore a space as a final character in the DB Name field - or any logon field for that matter.
User is trying to logon to Dimensions from a Windows client, and receives the following error: Failed to connect to the Dimensions server Invalid user name or password
When logging into the Desktop Client with SSO enabled, the following error is being received: Failed to connect to the Dimensions server. PRG7700105E Error: Multiple users have been found in LDAP
However, when user tries to open the Deployment area to view its contents some time later, after logging off Desktop client and then logging back on, cursor goes to hourglass for a number of seconds, then client presents a "Dimensions" error box with a "Operation completed" message. When user clicks OK it then presents the Remote Node Log In dialog box. The node, userid and pwd fields are already filled in.
After running the CRDB command with the /basedon option, the above error occurs during logging into the Desktop Client and/or after creating a new project and opening this project. The error is:
By default, the Dimensions Agent installs a Dimensions Listener server which is started by the Local System Account. If this is changed to use a another account, for example dmsys@mycompany.com , the Dimensions service will stop and will show the following in the dmpool log and/or event viewer logs : DMPOOL 2014/09/15 20:14:31 E P25832 T10488 Start dmlibsrv failed, process 1195463507.
Communications error has occurred Error message when trying to log into DMDBA: Duplicate Message numbers starting from 3500 in <$DM_ROOT>\cm\msg\orig_dbwrite_sql_uk.msb and <$DM_ROOT>\cm\msg\dbwrite_sql_uk.msb
The attached screenshot shows a sample where the REXEC is executed 3 times. In desktop client , a folder is created with the node name (par-jm-vm11 in this sample) and also a sub-folder named with the template name (hello.tplt in this sample).