J
jrposte
We had an issue where the search worked when we were developing the system,
but failed when we deployed to the general user population.
Out SP farm used multiple URLs for multiple Web Apps on the server. The top
level site on the server was not set up for user access, it was just a dummy
site that needed to be there to publish to subordinate sites on the server.
Our subordinate subsite in question was setup for general user access.
For example:
http://abc - server, and context target
http://abc/sites/projects - SP application site where we applied an
alternate access mapping of http://abcprojects
Search Failed on our original configuration for the users configured on and
using http://abcprojects
We found that we had to give users at least Read level access to the dummy
http://abc site which we were using for Context. When we did that the
"search failed" problem disappeared and the Contact Selector worked for all
of the users on http://abcprojects.
It may sound obvious after the fact, but it was a bear to diagnose, so I'm
posting this solution here in case anybody else's "search failed" problems
are caused by Sharepoint permissions issues as ours were.
The reason that our developers had no problems is that they all had local
accounts on the http://abc server, so when they wanted to use the contact
selector, they already had read (and better) permissions on the abc machine,
so the context lookup worked for them, even though they weren't added in to
the abc dummy site in Sharepoint.
I hope this helps to keep others out of the swamp.
but failed when we deployed to the general user population.
Out SP farm used multiple URLs for multiple Web Apps on the server. The top
level site on the server was not set up for user access, it was just a dummy
site that needed to be there to publish to subordinate sites on the server.
Our subordinate subsite in question was setup for general user access.
For example:
http://abc - server, and context target
http://abc/sites/projects - SP application site where we applied an
alternate access mapping of http://abcprojects
Search Failed on our original configuration for the users configured on and
using http://abcprojects
We found that we had to give users at least Read level access to the dummy
http://abc site which we were using for Context. When we did that the
"search failed" problem disappeared and the Contact Selector worked for all
of the users on http://abcprojects.
It may sound obvious after the fact, but it was a bear to diagnose, so I'm
posting this solution here in case anybody else's "search failed" problems
are caused by Sharepoint permissions issues as ours were.
The reason that our developers had no problems is that they all had local
accounts on the http://abc server, so when they wanted to use the contact
selector, they already had read (and better) permissions on the abc machine,
so the context lookup worked for them, even though they weren't added in to
the abc dummy site in Sharepoint.
I hope this helps to keep others out of the swamp.