Export (0) Print
Expand All
4 out of 6 rated this helpful - Rate this topic

Site Server - LDAP Troubleshooting Guide

September 1999 

Introduction

Most problems with the Lightweight Directory Access Protocol (LDAP) Service occur when appropriate hot fixes are not applied or when the components are installed in the wrong order. In addition, poor performance or failure can be caused by incorrect configuration of the underlying systems (adding invalid Service Packs or configuring the underlying SQL database incorrectly). To use LDAP successfully, you must first understand the system components and how they interact, then thoroughly plan your entire configuration before installing any part of the software.

This troubleshooting guide consists of the following sections:

  • Troubleshooting procedures

  • Software components 

  • Knowledge Base articles

  • LDAP service events 

  • LDAP administration events 

Troubleshooting Procedures

The diagnostic questions in this section will help you identify the problem when LDAP doesn't appear to be operating correctly. The questions can be grouped into the four categories shown in the following table:

Troubleshooting Category

Diagnostic question

System setup

· Have you loaded the necessary service packs?
· Does the equipment meet the minimum requirements?

Configuration

· Are LDAP, AUO, and SQL located on the same or separate machines?
· What are the computer names and IP addresses?
· Are there any firewalls installed between components?
· What was the order of installation? (For the correct order of installation, see the "Software Components" section.)
· What has changed?
· Did you just install a hot fix or service pack? If so, did you run the update script?
· What is the SQL configuration?
· Have you set up named pipes and TCP/IP sockets on port 1433?
· Can you telnet to port 1433?
· If you're using Microsoft® SQL Server™ 6.5, have you installed Service Pack 4 and the 297 hot fix?

Error identification

· What error(s) are occurring? (Check the event log.)
· Is the error in a script on the computer running AUO?
· Is the error occurring because LDAP isn't connecting to the DS?
· Is the LDAP service running?
· Check the control panel. If the LDAP service isn't running, start it. If it still won't start, try rebooting the system.
· Check MMC: Personalization and Membership to make sure LDAP is running.

SQL settings

· Are the SQL settings correct?
· Have you given SQL as much memory as possible?
· Were Open Objects set to 2000?

Software Components

The following list contains the latest versions of software that make up a complete membership system with LDAP. Always install the listed software in the order shown:

  1. Microsoft® SQL Server™ 7 

  2. MDAC 2.1 

  3. ADSI 2.5

  4. Microsoft Site Server 3 RTM P&M components

  5. Site Server 3 Service Pack 2, available at http://www.microsoft.com/siteserver/commerce/DeployAdmin/default.htm

Knowledge Base Articles

You can search for available Knowledge Base articles on various support topics on http://support.microsoft.com/default.aspx?scid=fh;EN-US;KBHOWTO .

LDAP Service Events

This service provides a Lightweight Directory Access Protocol (LDAP) interface for industry-standard, platform-independent access to the Membership Directory. This service can generate the events listed in this section.

396 The evaluation period for this product has expired and could no longer be started. 

Type: ErrorRecommended Action:Acquire a released version of the product.

397 LDAP server could not establish SSL channel. 

Type: ErrorRecommended Action:Make sure the proper certification is installed correctly.

398 Cannot allocate %1 because there is not enough memory available. 

Type: ErrorRecommended Action:Increase memory.

399 Cannot allocate %1 because the preallocated limit has been reached. 

Type: ErrorRecommended Action:Increase the maximum number of dynamic objects allowed.

400 LDAP Service cannot initialize its security. 

Type: ErrorRecommended Action:Check the Microsoft® Windows NT® Server configuration and restart the computer.

401 LDAP Service cannot initialize the socket library. 

Type: ErrorRecommended Action:Check the TCP/IP configuration.

402 LDAP Service rejected the connection attempt because there are too many users connected. 

Type: WarningRecommended Action:Increase the available connections on the General tab of the LDAP Properties dialog box in MMC.

404 LDAP Service cannot open the LDAP/TCP service. The data area, shown below, contains the return error code. 

Type: ErrorRecommended Action:No action is required.

405 LDAP Service cannot create the main connection socket. The data area contains the return error code. 

Type: ErrorRecommended Action:Validate TCP/IP configuration and connectivity.

408 A call to a system service failed unexpectedly. The data area contains the return error code. 

Type: ErrorRecommended Action:No action is required.

417 LDAP Service cannot open the LDAP registry key %2. 

Type: ErrorRecommended Action:Refresh the installation of the LDAP Service.

418 LDAP Service cannot read registry key %2 

Type: ErrorRecommended Action:Refresh the installation of the LDAP Service.

481 The LDAP Service cannot initialize the following object: %1. 

Type: ErrorRecommended Action:No action is required.

485 A system call (%1) failed unexpectedly. The data area contains the return error code. 

Type: WarningRecommended Action:No action is required.

530 LDAP Service has been started. 

Type: InformationalRecommended Action:No action is required.

531 LDAP Service has been stopped. 

Type: InformationalRecommended Action:No action is required.

532 LDAP Server instance %1 has been stopped. 

Type: InformationalRecommended Action:No action is required.

533 LDAP Server instance %1 has been paused. 

Type: InformationalRecommended Action:No action is required.

534 LDAP Server instance %1 has been unpaused. 

Type: InformationalRecommended Action:No action is required.

535 LDAP Server instance %1 has been created. 

Type: InformationalRecommended Action:No action is required.

536 LDAP Server instance %1 has been deleted. 

Type: InformationalRecommended Action:No action is required.

2133 The server has detected a previous instance and cannot boot until the old instance goes away. 

Type: ErrorRecommended Action:Try to start the service after 120 seconds.

2500 The server failed to startup due to an initialization error. 

Type: ErrorRecommended Action:Verify configuration; consult other log entries; refresh the installation.

2501 The server failed with a runtime error. 

Type: ErrorRecommended Action:Contact Microsoft Technical Support.

2502 LDAP Service: %1. 

Type: ErrorRecommended Action:The recommended action is message-dependent.

2600 LDAP Dynamic Replication failed due to an initialization error. 

Type: ErrorRecommended Action:Verify configuration.

2601 LDAP Dynamic Replication failed with a runtime error. Error description is: %1. 

Type: ErrorRecommended Action:No action is required.

2602 LDAP Dynamic Replication Info: %1. 

Type: ErrorRecommended Action:No action is required.

2603 LDAP Dynamic Replication Warning: %1. 

Type: ErrorRecommended Action:No action is required.

LDAP Administration Events

This section lists the administration events that can occur for the LDAP service.

300 An LDAP Service configuration has not been loaded. 

Type: ErrorRecommended Action:Verify configuration. Check the LDAP property page.

301 Could not create Remote DCOM object: %1. 

Type: ErrorRecommended Action:No action is required.

302 Could not create DCOM object: %1. 

Type: ErrorRecommended Action:No action is required.

303 Could not convert parameter value to string: %1. 

Type: ErrorRecommended Action:No action is required.

304 Could not convert parameter value to integer: %1. 

Type: ErrorRecommended Action:No action is required.

305 Could not convert parameter value to boolean: %1. 

Type: ErrorRecommended Action:No action is required.

306 The given IP address is not supported on the LDAP Service computer. 

Type: ErrorRecommended Action:Check the LDAP property page.

Port numbers must be above 100. 

Type: ErrorRecommended Action:Change the port number to #389 or any other valid port number above 100.

308 The given IP address is not valid. 

Type: ErrorRecommended Action:Recheck the IP address.

309 Could not initialize Winsock: %1 

Type: ErrorRecommended Action:Reinstall Winsock.

310 Could not obtain IP Address from Host Name. 

Type: ErrorRecommended Action:Check TCP/IP configuration, DNS configuration, and target host name.

311 The given parameter value must be positive. 

Type: ErrorRecommended Action:Validate the referenced parameter.

312 Invalid authorization mode selected. 

Type: ErrorRecommended Action:Consult the documentation.

313 Invalid Database type selected. 

Type: ErrorRecommended Action:Reset the database types on the Root Database tab and Directory Properties tab of the LDAP Properties dialog box in MMC.

350 LDAP Administration Failure: %1. 

Type: ErrorRecommended Action:No action is required.

400 Could not access configuration database: %1. 

Type: ErrorRecommended Action:No action is required.

401 Could not open server configuration information. Server instance may not exist. 

Type: ErrorRecommended Action:Recheck the server instance.

402 Failed to write to the configuration database. 

Type: WarningRecommended Action:No action is required.

404 Could not save configuration changes. 

Type: ErrorRecommended Action:No action is required.

405 Could not add new server instance to the configuration database. 

Type: ErrorRecommended Action:No action is required.

406 Could not obtain server installation directory: %1 

Type: ErrorRecommended Action:No action is required.

407 Could not create default data store: %1 

Type: ErrorRecommended Action:No action is required.

408 Could not delete server instance information. Specified instance may not exist. 

Type: ErrorRecommended Action:No action is required.

409 Data Store Administration Failure. 

Type: WarningRecommended Action:No action is required.

410 Could not obtain server host name. 

Type: ErrorRecommended Action:Check connectivity and network configuration.

411 Could not resolve server host to obtain IP address. 

Type: ErrorRecommended Action:Check connectivity and network configuration.

412 Only Access database can be Compacted/Repaired. 

Type: ErrorRecommended Action:No action is required.

413 The Compact/Repair operation has failed. 

Type: ErrorRecommended Action:No action is required.

414 Could not replace database with compacted version: %1 

Type: ErrorRecommended Action:No action is required.

415 Could not obtain server ID. Specified server instance may not exist. 

Type: ErrorRecommended Action:No action is required.

416 Could not obtain server state. Specified server instance may not exist. 

Type: ErrorRecommended Action: Recheck the server instance.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.