I'm not honestly sure when this bug arose, but I'm leaning toward post Feb Cumulative Updates. The problem is with the people picker found on the Central Admin -> Applicaiton Management ->Site Collection Owners -> Site Collection Administrators page ONLY.Background info:People Picker picks up domain/machine users on all other uses under central admin; it's only on this page that it no longer identifies or even extends the search to domain/machine users.My Central Admin web.config hasn't changed (and to be sure I've compared versions).All of my sites are extended for FBA and the database users are currently the only ones showing up on this people picker.I've tested removing FBA, in this case the people picker finds no users.I can easily add my site collection admins(that are domain users)via stsadm without a problem (and is what I'm now resorting to for the time-being)This is just a single server environment running MOSS Enterprise Edition.Prior to the Feb Update, the only MOSS update I applied to the server was SP1.Again, the people picker is ONLY faulty on the Central Admin -> Applicaiton Management ->Site Collection Owners -> Site Collection Administrators page I'm completly stumped. Am I the only having this probelm? Does anyone have any suggestions for things to try? Any ideas would be appreciated!Thanks!

Hi, I am experiencing exactly the same issue. (see http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/da0d231c-0b00-4283-accc-99aececfc38d) - posted 2 hrs before yours.I have tried removing the Central Administration website, and recreating it; running Configuration Wizard, but there was no change.rgdsWarren

I've updated to SP2 and the problem is still persistent.Additional info from error log:04/30/2009 16:33:59.47 w3wp.exe (0x1A1C) 0x1210Windows SharePoint Services General 72e9Medium Error in resolving user 'domain\username': System.ComponentModel.Win32Exception: Unable to contact the global catalog server at Microsoft.SharePoint.Utilities.SPActiveDirectoryDomain.GetDirectorySearcher() at Microsoft.SharePoint.WebControls.PeopleEditor.SearchFromGC(SPActiveDirectoryDomain domain, String strFilter, String[] rgstrProp, Int32 nTimeout, Int32 nSizeLimit, SPUserCollection spUsers, ArrayList& rgResults) at Microsoft.SharePoint.Utilities.SPUserUtility.ResolveAgainstAD(String input, Boolean inputIsEmailOnly, SPActiveDirectoryDomain globalCatalog, SPPrincipalType scopes, SPUserCollection usersContainer, TimeSpan searchTimeout, String customFilter) at Microsoft.SharePoint.Utilities.SPActiveDirectoryPrincipalResolver.ResolvePrincipal(String input, Boolean inputIs... 04/30/2009 16:33:59.47*w3wp.exe (0x1A1C) 0x1210Windows SharePoint Services General 72e9Medium ...EmailOnly, SPPrincipalType scopes, SPPrincipalSource sources, SPUserCollection usersContainer) at Microsoft.SharePoint.Utilities.SPUtility.ResolvePrincipalInternal(SPWeb web, SPWebApplication webApp, Nullable`1 urlZone, String input, SPPrincipalType scopes, SPPrincipalSource sources, SPUserCollection usersContainer, Boolean inputIsEmailOnly, Boolean alwaysAddWindowsResolver). Any ideas for things to try with this new info?

FWIW I have the same exact problem started AFTER installing SP2I get InvalidOperationException :: "The value for the property PageSize cannot be set.">System.DirectoryServices.dll!System.DirectoryServices.DirectorySearcher.DoSetSearchPrefs(System.DirectoryServices.Interop.UnsafeNativeMethods.IDirectorySearch adsSearch, System.DirectoryServices.Interop.AdsSearchPreferenceInfo[] prefs) + 0x3a9 bytesSystem.DirectoryServices.dll!System.DirectoryServices.DirectorySearcher.SetSearchPreferences(System.DirectoryServices.Interop.UnsafeNativeMethods.IDirectorySearch adsSearch, bool findMoreThanOne) + 0x164f bytesSystem.DirectoryServices.dll!System.DirectoryServices.DirectorySearcher.FindAll(bool findMoreThanOne) + 0xc1 bytesMicrosoft.SharePoint.dll!Microsoft.SharePoint.WebControls.PeopleEditor.SearchFromGC(Microsoft.SharePoint.Utilities.SPActiveDirectoryDomain domain = {Microsoft.SharePoint.Utilities.SPActiveDirectoryDomain}, string strFilter = "(&(objectSID=removed actual SID))", string[] rgstrProp = {string[11]}, int nTimeout = 30, int nSizeLimit = 200, Microsoft.SharePoint.SPUserCollection spUsers = null, out System.Collections.ArrayList rgResults = Count = 0) + 0x218 bytesMicrosoft.SharePoint.dll!Microsoft.SharePoint.WebControls.PeopleEditor.GetUserPropCollectionBySIDJN

I have reverted my virtual PC to an Infrastructure Update patched MOSS installation, and then upgraded to SP2, and also have the same problem.If it helps anyone trying to identify the cause ... I can say that the problem manifested after installing the WSS SP2 (which was installed before the MOSS SP2).

I have the problem after applying WSS SP2 and MOSS SP2 too.I am not sure if the problem affects just the picker. I am not able to create another SSP and the error is the same - the user cannot be resolved. I posted about it to http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/da0d231c-0b00-4283-accc-99aececfc38d.Any new about this would be very much welcome.Thanks,Ferda

@samwids - Many thanks for the tip - it was the IIS Application Pool Identity !! The following has more details than you may need but have included them here so as to elaborate on all the details involved in fixing this issue in case anyone needs to them. Even though many posts on other sites indicated I needed to use STSADM command line tool to set the peoplepicker- searchadforests to the proper domain and user (etc) , it turned out that that was not the issue at all. I removed the values that I had previously added to peoplepicker-searchadforests so that the property value no longer exists. (to remove the property - just assign a blank value when adding in the property - the following link indicates how to SET or GET propery values http://technet.microsoft.com/en-us/library/cc262988(office.12).aspx ) Yes - the issue was incorrect IIS Application Pool credentials, where the current Identity did not have the abiltiy to query the Active Directory. It started when I deployed content from one farm to another farm and the pool credentials selected during deployment did not have rights to query the Active Directory. After changing the IIS Application Pool Identity to the Network Service then found ou the site no longer had the proper credentials to query the database in SQL. I then also had to add the Network Service tothe list of Users who have login credentials to the SQL database as well. I also had to set the schema for the Network Service to the Schema used by the previous user as well in SQL. If you have multiple Share Point databases then use SP admin to find the db name that is used by the SP site in question.