we initially had single server deployment with 8 web app on WSS 3.0.
due to load, we now moved them to a new farm with 3 servers with following configuration:
1. all having wss 3.0 SP1
2. all patched with search server express 2008
3. search and query bieng served by server3

also not worthy here is that due to budget constraint and stuff, we dint had load balancing so we are doing context switchin with
4 app on server1 and 4 app on server2..
each of this app is turned off in IIS in other server and each app has own IP and DNS.
so the NIC of each server has 4 IPs

backup restore happened like a charm. the expected context swithcing happens like a charm. but now people picker goes in infinite “query bieng processed” and never fetches anything

this problem has become a red flag as this the 4th day and i could find nothing that worked.

I assume that GetEmpNbr() is your custom method that connects to the AD to get some extra info about the user. There are various reasons why it may be failing. For example you haven’t specified the correct domain name or organization unit, you haven’t connected to the right AD server.

I think that it is better if you ask this question in an AD specific group or try to search more about LDAP queries. I’m assuming you are using LDAP.

i used it in my webpart and seems doing fine. users can be seen from the people editor box. i have one method wherein I am getting the employee number based on the loginName of the user i selected from the people editor, the thing is, when i select the user from the peopleeditor, the user is there, but when the GetEmpNbr method is read, it throws an error “User cannot be found.”

do you know what might be causing the error?

also, isn’t it that when you specify “User” in the SelectionSet, it would get all AD Users, but why this time, I could select it from peopleeditor, but the AD could not find the user..

any thoughts on this?