This section provides the Microsoft Windows NT events and system errors for ILS. The following events and errors display in the Windows NT Event Log. Many of the events will return the NT error code associated with the event. Text for event log messages contain a GetLastError()=xx string that shows the error code of the last error that occurred.ii
The following table contains some of the more common error codes.
|
Code |
Description |
Comment |
|
5 |
Access denied |
You should check the permissions set for the WWW service anonymous logon account and the permissions set for the LDAP service logon account. |
|
2 or 3 |
Path or file not found |
One of the files that ILS needs is not available or not found in the current path. Check your installation. |
|
8 or 14 |
Not enough memory |
The ILS server ran out of available memory. |
Windows NT has many other error codes. For a complete list, see the Windows NT documentation.iii
The following tables list all of the Windows NT event messages for ILS. The prefix for the error, IDS_ indicates an error generated from ILS. You may also see error messages with a prefix of WPQR_. These are equivalent to messages with the IDS_ prefix.
General Error | |
|
Source |
ILS |
|
ID |
1 |
|
Text |
General error:<description>. |
|
Severity |
Error |
|
Name |
IDS_EVENT_GLOBAL_ERROR |
|
Meaning |
An unspecified error occurred. |
|
Cause |
ILS encountered an unknown situation. |
|
Recommendation |
Check the servers, make sure that ILS is installed correctly, and use the ISM ILS Admin interface to check for more specific errors. |
Initialization Success | |
|
Source |
ILS |
|
ID |
4 |
|
Text |
The ILS core object was initialized successfully. |
|
Severity |
Information |
|
Name |
IDS_INIT_EVENT |
|
Meaning |
The ILS core object was initialized successfully. |
|
Cause |
Successful initialization. |
|
Recommendation |
This is informational only. No action is needed. |
Initialization Error | |
|
Source |
ILS |
|
ID |
6 |
|
Text |
The ILS core object cannot be initialized. |
|
Severity |
Error |
|
Name |
IDS_INIT_ERROR |
|
Meaning |
An error occurred during ILS initialization. |
|
Cause |
This is most likely due to an error reading the registry. The message should be accompanied by an event log error specifying what went wrong. |
|
Recommendation |
See the troubleshooting section. |
Invalid Initialization Parameter | |
|
Source |
ILS |
|
ID |
8 |
|
Text |
Invalid ILS initialization parameters: <description>. |
|
Severity |
Information |
|
Name |
IDS_INIT_PARAM_ERROR |
|
Meaning |
An error occurred during ILS initialization. |
|
Cause |
Initialization was attempted using an invalid parameter. |
|
Recommendation |
Check to see whether ILS is otherwise initialized. |
Cannot Open RegKey | |
|
Source |
ILS |
|
ID |
9 |
|
Text |
The ILS Server cannot open the ILS registry key <key name>. The Data area, shown below, contains the error. |
|
Severity |
Error |
|
Name |
IDS_EVENT_CANNOT_OPEN_REGKEY |
|
Meaning |
A required registry key or value was not found. |
|
Cause |
ILS is not set up correctly. |
|
Recommendation |
Run Setup again. |
Cannot Read RegKey | |
|
Source |
ILS |
|
ID |
10 |
|
Text |
The LDAP Server cannot read registry key <key name>. The Data area, shown below, contains the error. |
|
Severity |
Error |
|
Name |
IDS_EVENT_CANNOT_READ_REGKEY |
|
Meaning |
A required ILS registry key or value cannot be read. |
|
Cause |
Either the registry key does not exist or there is a security rights error accessing the database. |
|
Recommendation |
Make sure that the registry key/value exists. If it does not, run Setup again. If the registry key/value does exist, make sure that the LDAP service is running with an account that has sufficient access rights to read the registry. Check to see whether LDAP is running by using the Services applet in Control Panel. |
Cannot Write RegKey | |
|
Source |
ILS |
|
ID |
11 |
|
Text |
The ILS Server cannot write registry key <key name>. |
|
Severity |
Error |
|
Name |
IDS_EVENT_CANNOT_WRITE_REGKEY |
|
Meaning |
A required ILS registry key or value cannot be written. |
|
Cause |
Probably occurred because of insufficient permission settings on the account. |
|
Recommendation |
Make sure that the LDAP service is running with an account that has enough rights to write to the registry (through the control panel services applet). |
Cannot Initialize ILS Database | |
|
Source |
ILS |
|
ID |
12 |
|
Text |
The ILS Server cannot initialize the ILS database DLL. |
|
Severity |
Error |
|
Name |
IDS_EVENT_CANNOT_INITIALIZE_IDSDB |
|
Meaning |
The ILS database object cannot be initialized. |
|
Cause |
Possibly occurred because of a problem connecting to the ILS SQL server. |
|
Recommendation |
Using the ISM LDAP Admin user interface, make sure that all the SQL server parameters are correct for each data source in each partition. |
Resource Out of Memory | |
|
Source |
ILS |
|
ID |
51 |
|
Text |
Memory allocation failed in: <description>. |
|
Severity |
Error |
|
Name |
IDS_RESOURCE_OUT_OF_MEMORY |
|
Meaning |
The ILS server ran out of memory. |
|
Cause |
The ILS server cannot allocate enough memory to perform a task. |
|
Recommendation |
Stop and restart the service. Restart the server. Consider additional memory. |
Parameter Not Supported | |
|
Source |
ILS |
|
ID |
301 |
|
Text |
One or more parameters are not valid. |
|
Severity |
Error |
|
Name |
IDS_BAD_PARAMETERS_MSG_ID |
|
Meaning |
At least one parameter used is not valid. |
|
Cause |
One or more parameters are not valid. |
|
Recommendation |
Check the parameters and try again. |
Parameter Missing | |
|
Source |
ILS |
|
ID |
302 |
|
Text |
Cannot complete operation. One or more required parameters are missing. |
|
Severity |
Error |
|
Name |
IDS_MISSING_PARAMETERS_MSG_ID |
|
Meaning |
The operation that was requested cannot be completed because insufficient parameters were specified. |
|
Cause |
The command was given without sufficient parameters. |
|
Recommendation |
Check for required parameters and try again. |
No Match | |
|
Source |
ILS |
|
ID |
303 |
|
Text |
No entries meet the search criteria. |
|
Severity |
Warning |
|
Name |
IDS_NO_MATCH_MSG_ID |
|
Meaning |
The query was executed successfully, but no match was found. |
|
Cause |
No match exists for the specified criteria. |
|
Recommendation |
Check the query to make sure that the criteria are specified correctly. If they are, use this message for information. |
Too Many Search Results | |
|
Source |
ILS |
|
ID |
304 |
|
Text |
The search criteria matched too many entries to compile the result set. |
|
Severity |
Warning |
|
Name |
IDS_TOO_BROAD_MSG_ID |
|
Meaning |
The number of matches exceeded capacity. |
|
Cause |
Probably occurred because of the search criteria being too broad, resulting in too many options found. |
|
Recommendation |
Narrow the search and try the query again. |
Entry Exists | |
|
Source |
ILS |
|
ID |
306 |
|
Text |
The entry already exists in the database. |
|
Severity |
Warning |
|
Name |
IDS_DUPLICATE_MSG_ID |
|
Meaning |
An attempt was made to add an entry that already exists in the database. |
|
Cause |
Probably occurred in response to a create request for an entry that already exists in the database. |
|
Recommendation |
Check to make sure that the spelling of the entry is correct. If it is, use this message for information. |
Database Error | |
|
Source |
ILS |
|
ID |
307 |
|
Text |
ILS database error. |
|
Severity |
Error |
|
Name |
IDS_RESOURCE_ERROR_MSG_ID |
|
Meaning |
An error occurred while trying to search the database. |
|
Cause |
There may be insufficient disk space, the network may be down, or the database file may have become corrupted. |
|
Recommendation |
Check network connections and disk space and try again. |
Operation Canceled | |
|
Source |
ILS |
|
ID |
311 |
|
Text |
The operation has been canceled. |
|
Severity |
Error |
|
Name |
IDS_CANCELLED_MSG_ID |
|
Meaning |
The operation was canceled. |
|
Cause |
The user may have canceled the operation, or the error may be due to network connection problems. |
|
Recommendation |
Check network connections and try again. |
Command Not Yet Implemented | |
|
Source |
ILS |
|
ID |
312 |
|
Text |
The requested command is not yet implemented. |
|
Severity |
Error |
|
Name |
IDS_NOT_SUPPORTED_MSG_ID |
|
Meaning |
The command requested has not been implemented. |
|
Cause |
The user attempted to use a command whose functionality is not yet implemented. |
|
Recommendation |
Check the command for spelling errors. If there are none, use this message for information. |
Out of Memory | |
|
Source |
ILS |
|
ID |
313 |
|
Text |
Not enough storage is available to complete this operation. |
|
Severity |
Error |
|
Name |
IDS_OUT_OF_MEMORY_MSG_ID |
|
Meaning |
The operation has been halted because there is not enough memory available to complete it. |
|
Cause |
More operations are being requested than the server can process. Or, too many applications are loaded. |
|
Recommendation |
Distribute operations to other servers, close any unneeded applications, and try the operation again. |
General ILS Error | |
|
Source |
ILS |
|
ID |
314 |
|
Text |
General ILS error. |
|
Severity |
Error |
|
Name |
IDS_ERROR_MSG_ID |
|
Meaning |
ILS encountered a nonspecific error. |
|
Cause |
An error occurred because of a condition that is not already defined. |
|
Recommendation |
Check network connections, disk space, and ILS server configuration to determine a more specific cause. |
ILS Functionality Disabled | |
|
Source |
ILS |
|
ID |
317 |
|
Text |
Internet Locator Server functionality has been disabled on this server (objectClass=RTPerson). |
|
Severity |
Error |
|
Name |
IDS_ILSDB_DISABLED_MSG_ID |
|
Meaning |
No ILS functionality is available on the current server. |
|
Cause |
ILS functionality has been disabled on the current server. |
|
Recommendation |
Enable ILS. |
Maximum User Count | |
|
Source |
ILS |
|
ID |
318 |
|
Text |
The Internet Locator Server has set a maximum of <number> users. |
|
Severity |
Information |
|
Name |
IDS_ILSDB_USERCOUNT_MSG_ID |
|
Meaning |
The specified number of users is the maximum for ILS. |
|
Cause |
Either a status was requested or a create was attempted on an ILS database already containing the maximum number of users. |
|
Recommendation |
This is informational only. No action is needed. |
Invalid Password Used in Re-Logon Attempt | |
|
Source |
ILS |
|
ID |
319 |
|
Text |
A re-logon attempt was made to the following account with an invalid password: <password>. |
|
Severity |
Warning |
|
Name |
IDS_ILSDB_BAD_LOGON_ATTEMPT_MSG_ID |
|
Meaning |
The password used for a repeat attempt to log on is invalid. |
|
Cause |
A user attempted another logon, using the specified invalid password. |
|
Recommendation |
Monitor the occurrence of this event. Frequent occurrence may indicate a more serious condition. |
ILS Initialized Successfully | |
|
Source |
ILS |
|
ID |
320 |
|
Text |
The Internet Locator Server has successfully initialized. |
|
Severity |
Information |
|
Name |
IDS_ILSDB_SERVICE_INITIALIZED_MSG_ID |
|
Meaning |
The Internet Locator Server has been initialized successfully. |
|
Cause |
The command to initialize was given. |
|
Recommendation |
This is informational only. No action is needed. |
ILS Terminated | |
|
Source |
MSIABS |
|
ID |
321 |
|
Text |
The Internet Locator Server has terminated. |
|
Severity |
Information |
|
Name |
IDS_ILSDB_SERVICE_TERMINATED_MSG_ID |
|
Meaning |
The Internet Locator Server has been terminated. |
|
Cause |
The command to terminate was given. |
|
Recommendation |
This is informational only. No action is needed. |
iiThe following table lists possible return codes, the commands that may return the codes, and the circumstances under which the codes get returned.
|
Return |
Commands |
Description |
|
WPQR_SUCCESS |
All |
The requested command completed successfully. |
|
WPQR_BAD_PARAMETERS |
All |
The query parameters passed to the last command contain bad or missing information. |
|
WPQR_MISSING_PARAMETERS |
All |
The query does not include one or more required parameters. |
|
WPQR_RESOURCE_ERROR |
All |
System cannot allocate a required resource. |
|
WPQR_CONNECT_ERROR |
All |
System cannot connect to a required resource. |
|
WPQR_TIMEOUT |
All |
Request took too long to process. The value for the time-out length is set on the Service tab of the LDAP service properties in Internet Service Manager. The default is 600 seconds. |
|
WPQR_NOT_INITIALIZED |
All |
SQL server not working. |
|
WPQR_DATABASE_ERROR |
All |
An error occurred between the time the database request was sent and the results returned. Can be caused by a process deadlock or may indicate that the maximum number of connections to the database has been reached. Can also be a cable or connection problem that happened after the database request was sent. |
|
IDA_BAD_PARTITION |
All |
The command tried to access a database partition that does not exist. |
|
WPQR_ERROR |
All |
Unspecified operation error. |
|
WPQR_REFUSED |
Modify, Delete |
The requesting agent does not have the authority to request this command. |
|
WPQR_NO_MATCH |
Modify, Delete |
The record to be modified or deleted was not found. |
|
WPQR_DUPLICATE |
Create |
A duplicate listing already exists in the database. |
|
WPQR_NO_MATCH |
Find, Resolve |
The query parameters do not result in any matches. |
|
WPQR_TOO_VAGUE |
Find, Resolve |
The query parameters specified cannot be used for a search. Missing or bad data for required minimum parameters. |
|
WPQR_TOO_BROAD |
Find, Resolve |
The query parameters specified returned too many matches. Maximum result set can be specified using the LDAP Service Properties pages or using the Inetcfg Set_ABS_Settings command. |
|
WPQR_DATABASE_ERROR |
Find, Create, Modify, Retrieve |
Unspecified database error. |
|
WPQR_CANCELLED |
All |
Operation canceled for unknown reasons. |
|
WPQR_NOT_SUPPORTED |
Unknown |
Unknown. |