Web Application Directory Trouble Screen

Unsuccessful Directory searches can occur for several reasons, from an inability to connect to the server for a search, to finding no Directory listings matching the search criteria. Any search-related problem displays as an error message on the Directory Trouble screen, shown below in Figure D-5.

Possible reasons for search failure and the resulting messages displayed on the Trouble screen follow in Table D-1.

Table D-1. Search Failure Causes and Corresponding Trouble Screen
Error Messages
Cause of Search Failure	LDAP Result Code	Trouble Screen Message
N/A. The corresponding LDAP Result Code represents a successful search.	0	No message displayed; search was successful.
Operations/Protocol error	1,2	Operations/Protocol error.
Server-generated time-out	3	Server timed out.
More than 96 entries match the Search criteria	4	Size limit exceeded.
Various unexpected errors. (These result codes should never be received).	5, 6, 10, 11, 12, 13, 14, 18, 19, 20, 21, 34, 36, 54, 64, 65, 66, 67, 68, 69, 71	Invalid response.
Authentication not accepted	7, 8, 48, 49, 50, 53	Authentication error.
Telephone Number not recognized	16, 17	Telephone Number not recognized.
Object not found	32	No results found.
Server responds with “null” as data	N/A	No results found.
Server not available	51, 52	Server not available.
Other, unspecified	80	An unknown problem has occurred.
If any of these system values are null (except DIRUSERID and DIRSRVRPWD, which are optional and hence may remain null), and the user tries to access the Directory Application, the Trouble Screen is presented to the user.	N/A	Insufficient Administrative Information.
The directory server does not respond at all within an administrable amount of seconds (default is 10 seconds)	N/A	Unable to contact server.
When the Directory Application receives a request for a Search screen, it will send a Search screen in response only if the minimum administrative information has been supplied. Otherwise, a Trouble Screen will be sent to the endpoint.	N/A	Insufficient Administrative Information.
When the Directory Application receives a request for a search from an endpoint, it will initiate a connection to the directory database server and, if successful, it will format and send a query to the database server based on the input received from the endpoint. If the input received from the endpoint is null, a Screen will be sent to the endpoint.	N/A	Insufficient Query Information.
If a connection to the database server cannot be established, or if the connection fails before a response is received, a Trouble Screen will be sent to the endpoint.	N/A	Connection Failure.
When the Directory Application receives a successful response from the database server, it sends a Successful Result screen to the endpoint. If no matching database entries are returned, it sends a No Match Result screen to the endpoint. If an error is returned by the database, a Trouble screen is sent to the endpoint.	N/A	No Match Result.
Cannot be determined	9, 22 - 31, 35, 37 - 47, 55 - 63, 70, 72 - 79, and 81 - 90	Unknown Error.