Receiving an error when attempting to access TCM through Munis stating:
Tyler Content Manager Server Connection Warning
Tyler Content Manager web service call encountered:
HTTP Error 401 () Contact Administrator to check TCM Server responsiveness.
(This message will only be displayed once per Munis sessions)
- Munis
- Enterprise ERP
- EERP
- Tyler Content Manager
- TCM
- Permissions
The user ID receiving the error needs TCM permissions configured and/or the TCM permissions have not yet synced to the TCM Full Client.
1. Verify that the user ID is in a Munis role that links to a TCM MU_xxx security group:
- Tyler Menu
- System Administration > Security > User Attributes > Search on affected user ID
- Click on the Data Access tab
- Scroll to the way bottom and double-click on TylerCM group access
- Under the User Access Detail tab, if you see one or more TCM MU_xxx groups, please follow step #2
- If you do not see any TCM MU_xxx groups under the User Access Detail tab, the user will need to have one of their Munis roles linked to one or more TCM MU_xxx security groups. Please contact TCM Support if you need assistance with this.
2. If the user is already in a Munis role that links to a TCM MU_xxx security group, please follow the below steps:
- Tyler Menu
- System Administration > Security > User Attributes > Search on affected user ID
- Under the Roles tab, click Update
- Click Accept in the ribbon
- Ask the user to test again.
3. If neither of the above steps were successful and the user is still receiving this error, please verify that the user ID has been synced to the TCM Full Client:
- Launch the TCM Full Client and sign in with administrative rights. If you are not familiar with how to access the TCM Full Client, please see these steps
- Navigate to Administration > Security Manager > search for the affected User ID. If you do not see the User ID listed, please follow these steps
If the user is still seeing the HTTP Error 401() error after completing the steps above, please contact TCM Support for further assistance and provide the user ID affected as well as which environment the error is occurring in (Live, Test, Train, etc).
0 Comments