5

When using the System.DirecoryServices.DirectorySearcher how can you determine if a ClientTimeOut has occurred or that the search naturally returned an empty SearchResultCollection?

given the following snippet

 using (var searcher = new DirectorySearcher(adRoot))
                        {
                            searcher.Filter = "SomeFilter";
                            searcher.PropertiesToLoad.Add("givenname");
                            searcher.PropertiesToLoad.Add("sn");
                            searcher.PropertiesToLoad.Add("department");
                            searcher.PropertiesToLoad.Add("samaccountname");
                            searcher.ClientTimeout = TimeSpan.FromSeconds(10);

                            using (var results = searcher.FindAll())
                            {
                               //haldle results                            
                            }
                        }
                    }
flalar
  • 1,181
  • 3
  • 12
  • 23

1 Answers1

6

Setting the ClientTimeout is only useful when you set the Asynchronous property to true. Which you didn't do. The documentation for the unmanaged IDirectorySearcher interface is much more detailed. From the MSDN article:

The client time limit preference is useful when a client requests an asynchronous search. In an asynchronous search, the client makes a request and then proceeds with other tasks while waiting for the server to return the results. It is possible that the server can go offline without notifying the client. In this case, the client will have no notification of whether the server is still processing the query, or if it no longer live. The client time limit preference gives the client some control of situations like this.

Do note that this "some control of situations" is less than perfect when you use the managed classes. The SearchResultCollection wrapper class doesn't actually give you a clean way to search asynchronously, it doesn't have a "BeginMoveNext" method to iterate the next result. The "proceeds with other tasks" angle is rather theoretical. Best not to use the property.

Hans Passant
  • 922,412
  • 146
  • 1,693
  • 2,536
  • Thanks for your response. The ClientTimeout occurs if the search takes more than the 10 seconds even though the Async property is not set. If the DirectorySearcher "aborts" the search due to clienttimeout beeing reached, we would like to retry the search against on of the other domain controllers on the network. Seems one of the domain controllers is much slower than the rest and we need to "fail over" to another controller if the ten seconds is exceeded – flalar Jan 20 '14 at 13:06