0
0 Comments

Hello,

I had my fair share of issues with SharePoint but the one I’m experiencing right now is one I cannot figure out.

So, we have a SharePoint 2013 environment which we want to configure for an additional domain. We did all the necessary steps to configure this and it’s actually working … for a part.

– Central Administration works! People from the other domain can be resolved without issues
– The regular Intranet webapp does not work. We implemented the exact same settings… users cannot be resolved.

We verified a lot of things:

– Application pool accounts: Central Admin runs under a different account than the Intranet webapp. We changed this so both run under the same application pool account. No change. We tried running both under the app pool account of CA => Works for CA, not for Intranet webapp. We tried the app pool account of the intranet webapp => still works for CA, not for the Intranet webapp!

– We checked the access to the “Secure” registry key on the WFE where the apppassword is stored. Both app pool accounts have full control.

Now, the odd thing…

We created a brand new webapplication which runs under the same app pool account as the intranet webapp and applied the same peoplepicker settings and IT WORKS! Users from the other domain can be resolved without issues.

The intranet webapp however still doesn’t want to resolve them.

So, Central Admin works, the new webapplication works, the intranet webapp doesn’t.

When we use Wireshark to see the LDAP traffic which is going on, we can see that in the intranet webapp, a result is returned from the other domain but the peoplepicker doesn’t return it.

We compared the peoplepicker settings from both webapplications and both are the same. We compared web.config files, webapplication properties, everything is the same. We tried to remove the peoplepicker settings and reapply them… nothing works.

The annyoing part is… this is a test environment. We already have the same webapplication running on PROD (did a DB detach/attach to get to PROD) and we see the same issue occuring on PROD as well. So, creating a new webapplication and detach/attach the DB doesn’t help either.

Is there any other thing we can try or check? Because it basically works… except for the webapplication where it SHOULD work.

Thanks in advance,

Bart

(Visited 323 times, 1 visits today)
Add a Comment