Let’s talk Alteryx Copilot. Join the live AMA event to connect with the Alteryx team, ask questions, and hear how others are exploring what Copilot can do. Have Copilot questions? Ask here!
Start Free Trial

Alteryx Server Discussions

Find answers, ask questions, and share expertise about Alteryx Server.

How can i delete a user from the embedded mongo db

NatSnook
8 - Asteroid

Hi All

not sure why i have emailed support@alteryx.com twice on this issue but have had no response hence the post here.

I have a gallery user whose profile in mongodb somehow seems to have become corrupted so they are unable to run any workflow or app in gallery using their own credentials even though they have all required permissions they get an unknown engine error everytime.

i'd like to delete them from mongodb completely and then get them to log back in thereby recreating their account.

they don't own any assets in gallery so removing them would have no other impact.

unfortunately as we're on server version 2022.1 the API fails to remove the profile as i believe there is a bug with our version.

Any help much appreciated

thanks

Nat

5 REPLIES 5
fmvizcaino
17 - Castor
17 - Castor

Hi @NatSnook ,

 

 

Before removing the user completely, I suggest you:

 

  1. Check the service logs and see if you find something there. I remember seeing this unknown engine error before but I don`t really recall. If the error is only when the user is running a workflow with his own credentials, it could be something related to the user not having enough permissions
    1. https://help.alteryx.com/20221/server/configure-required-run-user-permissions
    2. Another important step but this is when all users are not able to run workflows with their own credentials, verify the Secondary Logon service is running to allow alternative users to run other services.
  2. Access the users' collection inside your MongoDB and analyze the user, see if something doesn`t add up in his account
    1. https://help.alteryx.com/20221/server/alteryxgallery-mongodb-schema#
    2. You can access the information with robo3T, it is free and easy to use, but you need to be inside the Alteryx Server machine to do it.
      1. https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/How-to-Connect-to-an-Embedded-Server-...
  3. Run the pre-upgrade checks and correct the errors if any. This is usually done before performing an upgrade and it is basically checking your MongoDB for inconsistencies, perhaps it will find something there
    1. https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/Alteryx-Server-Pre-Upgrade-Checks/ta-...
    2. You need to run this from inside the Alteryx server machine
  4. Manually remove the user from MongoDB
    1. Save a backup first! Be aware that this is not supported by Alteryx and you would be doing at your own risk
      1. https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/Alteryx-Server-Backup-and-Recovery-Pa...
    2. Access the Gallery and delete the user from all the user groups, collections, data connections and delete his subscription if he is an artisan
    3. With Robo 3T`s help, you can remove the user

 

Best regards,

Fernando Vizcaino

NatSnook
8 - Asteroid

thanks @fmvizcaino this did work to remove the user from mongodb. it wouldn't work previously as the user was still part of a collection - However after removal and then the user logging back in and recreating their profile they still get the Unknown Engine error :(

NatSnook_0-1687262203761.png

 

I'm at wits end with this one

 

fmvizcaino
17 - Castor
17 - Castor

Is the user able to run workflows without using their own credentials?

NatSnook
8 - Asteroid

Yes @fmvizcaino if they use someone else credentials then it works fine.

fmvizcaino
17 - Castor
17 - Castor

I have seen this issue only once, but it happened with all the users because the secondary logon service was disabled. 

 

In your case, I would check the Logon as a batch job permission.

You can find more information here: https://help.alteryx.com/20221/server/configure-required-run-user-permissions

 

Best regards,

Fernando Vizcaino