SOLVED

Multiple entries matched, please click to resolve

%3CLINGO-SUB%20id%3D%22lingo-sub-130219%22%20slang%3D%22en-US%22%3EMultiple%20entries%20matched%2C%20please%20click%20to%20resolve%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130219%22%20slang%3D%22en-US%22%3E%3CP%3ESeeing%20the%20following%20when%20attempting%20to%20share%20from%20ODFB%20-%20clicking%20to%20resolve%20as%20suggested%20does%20nothing.%20These%20users%20exist%20in%20another%20tenant%20that%20I%20am%20also%20a%20member%20of.%20They%20are%20not%20defined%20in%20my%20own%20tenant%20from%20which%20I'm%20attempting%20to%20share%20this%20document.%20It's%20as%20if%20ODFB%20is%20confused%20as%20I%20have%20an%20account%20in%20both%20the%20source%20and%20target%20tenant.%20Anyone%20encountered%20this%20%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20327px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F24552i947F1BA89C32276F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22snip_20171121162357.png%22%20title%3D%22snip_20171121162357.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-130219%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOneDrive%20for%20Business%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-156269%22%20slang%3D%22en-US%22%3ERe%3A%20Multiple%20entries%20matched%2C%20please%20click%20to%20resolve%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-156269%22%20slang%3D%22en-US%22%3E%3CP%3ECheck%20deleted%20external%20deleted%20emails%20on%20your%20admin%20center.%20If%20they%20show%20there%20restore%20them!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-130310%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Multiple%20entries%20matched%2C%20please%20click%20to%20resolve%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130310%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20certainly%20sounds%20feasible%2C%20thanks%20again%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-130307%22%20slang%3D%22en-US%22%3ERE%3A%20Multiple%20entries%20matched%2C%20please%20click%20to%20resolve%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130307%22%20slang%3D%22en-US%22%3Ethe%20logical%20explanation%20would%20be%20that%20when%20you%20created%20them%20as%20internal%20users%2C%20and%20assigned%20some%20permission%20to%20them%2Fshared%20something%20from%20your%20onedrive%2C%20there%20was%20an%20entry%20done%20on%20the%20user%20info%20table%20with%20a%20unique%20id...%20Now%20that%20you%20are%20trying%20to%20share%20with%20them%20as%20%22external%20users%22%20the%20user%20info%20table%20already%20has%20an%20entry%20for%20them%20as%20internal%20users%2C%20and%20that%20might%20have%20caused%20the%20clash..%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-130305%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Multiple%20entries%20matched%2C%20please%20click%20to%20resolve%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130305%22%20slang%3D%22en-US%22%3E%3CP%3EI%20think%20in%20the%20past%20I%20did%20create%20them%20directly%20in%20Azure%20AD%20but%20then%20removed%20them.%20They%20seemed%20to%20linger%20on%20as%20SharePoint%20users.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-130303%22%20slang%3D%22en-US%22%3ERE%3A%20Multiple%20entries%20matched%2C%20please%20click%20to%20resolve%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130303%22%20slang%3D%22en-US%22%3EHard%20to%20say%20hehe..%20Could%20have%20been%20stale%20entries%20on%20the%20User%20Information%20table%20or%20the%20possibility%20that%20these%20were%20first%20created%20as%20internal%20users%20then%20shared%20external%20OR%20vice%20versa...%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-130302%22%20slang%3D%22en-US%22%3ERe%3A%20Multiple%20entries%20matched%2C%20please%20click%20to%20resolve%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130302%22%20slang%3D%22en-US%22%3E%3CP%3EBingo%20!%20The%20users%20were%20indeed%20listed%2C%20removed%20them%2C%20and%20sharing%20worked.%26nbsp%3B%20What's%20actually%20going%20on%20here%20%3F%20Thanks%20for%20your%20help%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-130228%22%20slang%3D%22en-US%22%3ERe%3A%20Multiple%20entries%20matched%2C%20please%20click%20to%20resolve%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130228%22%20slang%3D%22en-US%22%3E%3CP%3EHave%20you%20ever%20shared%20anything%20with%20these%20users%20before%3F%3CBR%20%2F%3EIf%20you%20go%20to%20following%20page%20%3A%3CBR%20%2F%3EGo%20to%20your%20onedrive%20for%20business%20site%3A%3CBR%20%2F%3ESite%20Settings%20%26gt%3B%20People%20%26amp%3B%20Groups%3CBR%20%2F%3EEdit%20the%20URL%20and%20change%20the%20%22MembershipGroupId%3D%3CNN%3E%22%20to%20%22MembershipGroupId%3D0%22%3CBR%20%2F%3EDo%20you%20see%20any%20of%20the%202%20users%3F%3C%2FNN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-130226%22%20slang%3D%22en-US%22%3ERe%3A%20Multiple%20entries%20matched%2C%20please%20click%20to%20resolve%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130226%22%20slang%3D%22en-US%22%3E%3CP%3EBoth%20accounts%20shown%20are%20in%20error.%20Both%20were%20typed%20in%20manually%2C%20in%20full%20-ie%20any%20autocomplete%20was%20ignored%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENo%20alternate%20addresses%20defined%20and%20indeed%20I'm%20not%20sure%20where%20you'd%20define%20these.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'm%20pretty%20sure%20I%20can%20get%20around%20this%20issues%20by%20pre-creating%20the%20accounts%20in%20Azure%20AD%20but%20obviously%20that's%20not%20always%20desirable.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-130222%22%20slang%3D%22en-US%22%3ERe%3A%20Multiple%20entries%20matched%2C%20please%20click%20to%20resolve%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130222%22%20slang%3D%22en-US%22%3E%3CP%3E1.Which%20is%20the%20account%20out%20of%20the%20two%20that%20is%20creating%20a%20problem(from%20the%20screenshot)%3F%3C%2FP%3E%0A%3CP%3ECan%20you%20share%20with%20one%20entry%20at%20a%20time%20so%20that%20you%20can%20pin%20point%20on%20the%20actual%20problematic%20account.%3C%2FP%3E%0A%3CP%3E2.You%20mentioned%20having%20an%20account%20on%20both%20tenants.%3C%2FP%3E%0A%3CP%3ELets%20assume%2C%20tenant%201%20which%20is%20the%20tenant%20that%20you%20are%20sharing%20from%3B%20user%40ten1.com%20AND%20tenant%20two%20is%20%3A%20user%40ten2.com.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOn%20tenant%201%2C%20for%20the%20user%20user%40ten1.com%2C%20is%20the%20alternate%20email%20address%20set%20as%20user%40ten2.com%20%3F%3C%2FP%3E%0A%3CP%3EI%20recall%20seeing%20an%20error%20like%20this%20sometime%20back%20and%20it%20was%20related%20to%20alternate%20email%20addresses.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Regular Contributor

Seeing the following when attempting to share from ODFB - clicking to resolve as suggested does nothing. These users exist in another tenant that I am also a member of. They are not defined in my own tenant from which I'm attempting to share this document. It's as if ODFB is confused as I have an account in both the source and target tenant. Anyone encountered this ?

 

 

snip_20171121162357.png

9 Replies

1.Which is the account out of the two that is creating a problem(from the screenshot)?

Can you share with one entry at a time so that you can pin point on the actual problematic account.

2.You mentioned having an account on both tenants.

Lets assume, tenant 1 which is the tenant that you are sharing from; user@ten1.com AND tenant two is : user@ten2.com.

 

On tenant 1, for the user user@ten1.com, is the alternate email address set as user@ten2.com ?

I recall seeing an error like this sometime back and it was related to alternate email addresses.

 

Both accounts shown are in error. Both were typed in manually, in full -ie any autocomplete was ignored

 

No alternate addresses defined and indeed I'm not sure where you'd define these.

 

I'm pretty sure I can get around this issues by pre-creating the accounts in Azure AD but obviously that's not always desirable.

best response confirmed by Ian Moran (Regular Contributor)
Solution

Have you ever shared anything with these users before?
If you go to following page :
Go to your onedrive for business site:
Site Settings > People & Groups
Edit the URL and change the "MembershipGroupId=<nn>" to "MembershipGroupId=0"
Do you see any of the 2 users?

Bingo ! The users were indeed listed, removed them, and sharing worked.  What's actually going on here ? Thanks for your help

Hard to say hehe.. Could have been stale entries on the User Information table or the possibility that these were first created as internal users then shared external OR vice versa...

I think in the past I did create them directly in Azure AD but then removed them. They seemed to linger on as SharePoint users.

the logical explanation would be that when you created them as internal users, and assigned some permission to them/shared something from your onedrive, there was an entry done on the user info table with a unique id... Now that you are trying to share with them as "external users" the user info table already has an entry for them as internal users, and that might have caused the clash..

That certainly sounds feasible, thanks again

Check deleted external deleted emails on your admin center. If they show there restore them!