The specified user could not be found

  • 25 February 2015
  • 4 replies
  • 4 views

Badge +9

Hi,

I had a workflow stopping working from this morning

I am updating Item Permissions and suddenly I get this error

The specified user 0#.f|membership|test-xx-xxx@xxxxxx.xx could not be found

Even when I try with my name, same issue

I can log, open the Library,  send a message and so on with this specified user.

I have created another workflow in another library, same issue.

When I log the user before the Update Item Permission action, I get Created by: i:0#.f|membership|test-xx-xxx@xxxxxx.xx

Do I need to care about the i in front of it?

Best regards,

Christophe Raucq


4 replies

Badge +9

I have tried in a complete different tenant: Same issue.

Is it Nintex or Sharepoint?

Futur will tell.

To make a summary

In O365, I add the action Update Item Permission and I get this error

The specified user 0#.f|membership|test-xx-xxx@xxxxxx.xx could not be found even the specified user is myself.

Inherit permissions from parent is set to No

Remove existing permissions is set to Yes

If

Inherit permissions from parent is set to Yes

Remove existing permissions is set to No

then there is no issue ... because I believe this is the default setting and the document/item does not need to be processed.

Badge +9

Hi Anatoliy,

Is your workflow running without issue before?

Some feedback from Nintex Support.

Nintex is just using the code of SharePoint.

I have tried to change the permissions with a SP Designer workflow.

I have the same kind of issue.

Here is the error I get.

InternalServerError to https://xxxxxx.sharepoint.com/sites/demo/CV/SPSession/_api/web/lists(guid'0e28b367-9b8d-4869-8f42-9986f66025a2')/Items(3)
Correlation Id: 029fb4c7-6415-8c58-894d-fb244f043364 Instance Id:
1a2d4706-835d-4e47-b275-fedd424a7ccb
Invalid URL: i:0#.f|membership|my.name@mycompany.com

I cannot find anything on internet about this.

We have created a Support Ticket to Microsoft.

Maybe good to do it on your side also.

Best regards,

Christophe

Badge +9

Hi,

There is a workaround:

You need to re-add the field for which you want to add the permission inside the 'update permissions'  workflow action (in the user or group section) by using the 'Advanced lookup' link.

Next you need to click the 'fx' icon and choose 'Email address' instead of 'login name' that is default.

If you click 'Insert', you'll not notice something different, it's still ‌‍{CurrentItem:Created By}‍‌ but in the system behind,
he'll pick the email address which will be recognized in the workflow action to set the permissions.​

Thansk Davy,

Best regards,

Christophe

Badge +8

Working with AD or ADFS? Any recent changes in this structure?

What could also resolve your issue (temporarily but not best practice) is creating variables for the different users. I haven't tested it with this issue so I'm not a 100% sure it will work. Before your set permissions action, use the set a variable action and occupy this variable of type person with the display name of the user you would like to give access to. Next use this variable to give permissions to the user in your set permissions action.

Reply