"PRIMARYTSAFAILEDPROCESSING User could not be created in CC4" error message in RM Unify Audit log
Published Date : 24 Sep 2021
Last Updated : 04 Oct 2024
Content Ref: TEC8134769
Operating System
(none)
Part No
(none)
Summary
Explains the cause of RM Unify Audit log error "User could not be created in CC4".
Symptoms
You have a Community Connect® 4 (CC4) network and are using RM Unify Network Provisioning. An RM Unify user account has failed to create in CC4, with the following RM Unify Audit log error:
"PRIMARYTSAFAILEDPROCESSING. User: <username>. User could not be created in CC4 and there is no record of the user within the CC4 system.. Further checking of CC4 has shown it to be stable, and this issue is localised to this User.. [CC4]: ***ATTENTION REQUIRED: An error was reported creating the User account. [CC4]: ***ATTENTION REQUIRED: A scan of the AD could not find a User called '<username>'. [CC4]: ***ATTENTION REQUIRED: This Username is NOT being added to the 'BLACKLIST' as it should be safe to use. [CC4]: ***ADVISORY: The Target System '[CC4]' was responsible for attempting to create the account. It cannot be assumed that this system will now allow the User to be created even though there is no AD account."
An attempt to manually create the user directly in the CC4 RM Management Console also fails.
Cause
This can occur when the username has previously been used on the network and is still referenced as an active user in the CC4 database, even though the AD user account no longer exists.
Procedure
Please raise a service call with your CC4 network support team, so that they can make further checks and manually remove orphaned references from the CC4 database where applicable.
If this article has not helped provide a solution then it is also possible to
log a call...
Document Keywords: mgt console, auditing, user audit, event type, rm unify audit, audit log, rmunp, PRIMARYTSAFAILEDPROCESSING, failure, User could not be created in CC4, TEC8134769