I once had the issue that a user was shown as “Inactive” when trying to add the user to an existing community. There´s a KB entry which shows the way how this problem can be resolved:

https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0127855

To verify this discrepancy, you can run the following SQL query against the SNCOMM database:

SELECT * FROM SNCOMM.MEMBERPROFILE WHERE EMAIL = ‘user@example.com‘;

If the STATE column returns a value of 1, the user is flagged as inactive in the Communities application, even if they are active elsewhere.

Cause
This issue is typically caused by a one-off synchronization failure between the Profiles database and the Communities database. This can happen if a user was deactivated and reactivated in quick succession, or if a transient network/database interruption occurred during a scheduled synchronization task.

Resolution
To resolve this discrepancy, you will need to perform a manual synchronization of the user’s data from Profiles to the other component databases using wsadmin commands.

Open the wsadmin command line on the Deployment Manager or a node running the Profiles application.

Initialize the Profiles administrative environment:
execfile(“profilesAdmin.py”)

Attempt to push the user’s data to all components:
ProfilesService.publishUserData(“user@example.com“)

If the user still appears inactive, perform a manual cycle of inactivation and reactivation to reset the state:
Inactivate the user:
ProfilesService.inactivateUser(“user@example.com“)

Reactivate the user (replace GUID with the user’s actual external ID):
ProfilesService.activateUserByUserId(“GUID”, email=”user@example.com“)

Publish the data again:
ProfilesService.publishUserData(“user@example.com“)

Verify the user can now be added to the Community.