Issue description  

When generating a report in ADManager Plus (configured with a Microsoft SQL database), the data may initially appear but then disappear, displaying a No Data Available message.

This issue can occur if the connection between ADManager Plus and the database fails during the report generation process. Since the data fetched from AD is temporarily stored in the database, any disruption in the database connectivity can result in the report displaying as empty. Ensuring stable and consistent database connectivity is essential for accurate report generation.

Possible causes  

This issue may occur due to one or more of the following reasons:

1. Missing or incompatible bcp.exe file: The bcp.exe utility from the SQL Server installation is either missing or incompatible. Ensure that the correct version is placed in the ADManager Plus bin folder for proper database operations.

2. Incorrect ODBC driver or SQL command-line utilities: The correct ODBC driver and SQL command-line utilities must be installed, corresponding to the SQL Server version.

3. Connectivity issues: Firewall rules or network restrictions may be blocking the connection between ADManager Plus and SQL Server.

4. Insufficient service account permissions: The ADManager Plus service account may lack the required database access permissions.

Prerequisites  

Before troubleshooting, ensure:

• The SQL Server is accessible from the ADManager Plus server.

• The necessary ODBC drivers and SQL command-line utilities are installed.

• The service account used for database communication has the required permissions.

Resolution  

Step 1: Verify connectivity to the SQL Server

1. Open the Command Prompt in the ADManager Plus server.
   
2. Run the following command to check if the SQL Server is reachable:

• telnet <SQL_Server_Hostname> <Port>
  

• The default port for SQL server is 1433, but it may be customized.

Before troubleshooting, ensure:

• The SQL Server is accessible from the ADManager Plus server.

• The necessary ODBC drivers and SQL command-line utilities are installed.

• The service account used for database communication has the required permissions.

• If the connection fails, check the firewall rules and network configurations.

3. Ensure that the SQL Server allows remote connections.

• Open SQL Server Configuration Manager > SQL Server Network Configuration and enable the protocols for SQL Instance.

• Enable TCP/IP and restart the SQL service.

Step 2: Update the service account password  

1. Stop the ADManager Plus service.
   

2. For SQL authentication:
   

• Navigate to the bin folder.

• Open the Command Prompt and run:

updateMSSQLPassword.bat

This updates the service account password.

3. For Windows authentication:

• Update the password in services.msc.

• If the account is not configured, ensure it is set up properly.

Step 3: Verify the service account permissions  

1. Log in to the SQL Server using SSMS.

2. Navigate to Security > Logins, and find the ADManager Plus service account.

3. Right-click on the account and go to Properties > Server Roles.

4. Ensure the account has the sysadmin role.

5. Alternatively, if minimal permissions are preferred, assign the following:

• db_datareader, db_datawriter, and db_ddladmin (via user mapping).

• Provide Execute permissions on the database.

 Tips 

• If using an external database, ensure the connection string in ADManager Plus is correct.

How to reach support