I've added two new users to a collection but when I go to add them to a Data Connection in Gallery their names won't appear.
Hi @eliberatore ,
Have you tried searching for the users using the last name or their ad userid?
Best,
Jagdeesh
Hi @JagdeeshN ,
Searching on last name and user ID did not work either.
@eliberatore
I've had similar issues before and one thing that sometimes works for me is to type in the first letter then * then a space then backspace to just the first letter. If it works, you should see a list of everyone with that letter in their name
so if I was searching for you, I'd key:
e*<space>
<backspace><backspace>
Hope this works for you!
-Jimmy
I had a similar problem when I realized that each user had to be assigned to a Data Connection after my upgrade past 2020.4.
What worked for me, though it was kind of a hassle, was that I had to go to each user, change a setting (schedule jobs from off to on), press save, and the user then appeared in the list. I'm not sure if this had to do with their role or if it's just a bug from upgrading server.
Things seem stable at the moment.
@eliberatore I just saw this post. For what it's worth, I've had a support ticket opened since October 2020 where we can't add some users to Data Connections. There is something weird going on where we can add any of the first ~500 users, but then ~500+ can't be added. We've been able to leverage the server's internal api to get around the issue for the time being. Our server has been on 2020.2 and 2021.2 with both versions having the issue. Given that more people haven't run into the issue, I suspect there's something funny in our specific environment/setup.
Alteryx Support provided our organization with a rather quick and simple resolution that involved re-indexing our Gallery MongoDB. Maybe your support contact on the case can elaborate on a solution like this and/or why it may or may not be applicable to your environment.
Hope yours gets resolved soon.
Best wishes.
Hey @patrick_digan ,
Were you able to find a solution for this problem?
I have a client in 21.3 with the same issue in the PROD Server but not in the DEV, both using the same version.
Fernando Vizcaino
@fmvizcaino we're still experiencing the same issue in 2021.2 and support has said that they thought 2021.3.3.63061 had a fix for the issue. Our workaround is the attached workflow which is replicating the front end API calls from the web. You'll need the Data Connection ID, the user ID, and the Server Name. We use windows auth, and so you'll also need to add a curators user name and password in both download tools on the connection tab. It makes 2 calls, one to get a session ID and then a second call to actually add the user to the dataconnection. Once it completes, you can see the user from the front end screens like normal. While I've never had a problem with this workflow, you should obviously start in Dev and make sure you're comfortable with the calls that are being made before you actually run it.
This is great, you are amazing @patrick_digan !!
Thanks a lot for the prompt response!!! Our client is in 21.3.2 and was open for an upgrade luckily 😁
We're on Server and Designer 2022.1.1 and also having this problem. I wasn't able to get the workflow @patrick_digan created to run. I'm not familiar at all with the API. Any other ideas or suggestions for how to resolve this?
I am experiencing the same issue as @gpmyers111 after just upgrading to 2022.1.1 from 2021.1.4.
I am familiar with the API, but I do not have the time/bandwidth to write the call(s) required to make this work.
Any guidance on this?
I worked on an environment that had this issue and discovered that the problem was due to an attribute in the MongoDB collection.table AlteryxGallery.users that was missing on some record documents.
There was an attribute named "IsPasswordMigrated" that was showing NULL for some and EMPTY for others. I found that the ones that were EMPTY is because the attribute didn't exist in their record document. I corrected those documents by adding the attribute and setting it with a NULL value, which did resolve the problem.
Note that it is NOT recommended that you manually alter tables in MongoDB and you should create a case with Alteryx to have their support team work with you to identify and correct. Doing so may cause irreparable damage to your environment.
If you'd like the script I used and familiar with MongoDB, shoot me a DM.
Thanks @jrgo. I reached out to Alteryx support and was able to get this resolved using a combination of the steps they provided and resources on the Alteryx Community.
Basically, you need to re-index the MongoDB that powers Alteryx Server.
Here are the steps I took:
C:\> cd "C:\Program Files\Alteryx\bin" <-- Change this to wherever Alteryx Server is installed C:\Program Files\Alteryx\bin> alteryxservice getemongopassword Admin: *********** Non-Admin: ******** <-- Use this password to connect to the Mongo DB below C:\Program Files\Alteryx\bin>mongo mongodb://localhost:27018/AlteryxGallery -u user -p {Non-Admin Password} <-- Enter your Non-Admin password here MongoDB shell version v4.2.22 <-- Version will vary depending on your installation connecting to: mongodb://localhost:27018/AlteryxGallery?compressors=disabled&gssapiServiceName=mongodb Implicit session: session { "id" : UUID("6fa8e3c2-dc4a-48d1-ac9e-c9720779db42") } MongoDB server version: 4.2.22 > use AlteryxGallery switched to db AlteryxGallery > db.locks.remove({}) WriteResult({ "nRemoved" : 3 }) <-- This number will vary from 0 to 2 (or 3 in this case) WriteResult({ "nRemoved" : 3 }) > db.commandQueueItems.remove({}) WriteResult({ "nRemoved" : 0 })
For more information regarding the commands above, check out Step 2 of this article on the community: https://help.alteryx.com/20193/server/server-host-recovery-guide#step-1-stand-up-a-new-server
Alteryx support also recommended clearing the "locks" collection within the AlteryxGallery_Lucene database. However, I was not able to access that database and everything still worked fine without completing that step. They also recommended downloading a tool called Robo3T which makes a lot of this easier; however, if you are working within a proxy or firewall, the steps above might be easier.
Hope this helps!
So we've been having this problem for about 6 months now even after upgrading versions. Re-indexing as described above works, but the problem comes back very fast... within a few days.
Is this expected or should I open a ticket to look for the root cause?
@kgalbert I would reach out to Alteryx support. If they aren't able to provide any solutions beyond what I've described above, you could try automating these steps using something like PowerShell, Python, or even Alteryx From there, schedule these steps to run once per week (or every day if you're having this issue more frequently).
Full transparency - I have not tried automating this, so I'm not sure what all this would entail.
Hope this helps.
The problem has been there for at least 2 years, Alteryx still have not yet fixed it nor provided any easy workaround.
