"Object reference not set..." appears when setting up Active Directory server connection on AD server

"Object reference not set..." appears when setting up Control Manager (TMCM) / Apex Central Active Directory (AD) server connection to AD server

- Updated:
- 6 Apr 2020
- Product/Version:
- Apex Central 2019
- Control Manager 6.0
- Control Manager 7.0
- Platform:
- Windows 2003 Enterprise
- Windows 2003 Server R2
- Windows 2003 Standard
- Windows 2008 Enterprise
- Windows 2008 Enterprise 64-bit
- Windows 2008 Server R2
- Windows 2008 Standard
- Windows 2008 Standard 64-bit
- Windows 2012 Server R2
- Windows 2016 Server

The error message “Object reference not set to an instance of an object” sometimes displayed as “System.NullReferenceException: Object reference not set to an instance of an object,” is an indication that the TMCM application cannot find the information it is seeking.

To resolve this, modify the Application Pool identity of IIS:

Open IIS Manager.
In the Connections pane, expand the server node and click Application Pools.
On the Application Pools page, select the application pool that you want to specify an identity. Click Advanced Settings in the Actions pane.
On Identity properties, click the ... button to open the Application Pool Identity dialog box.
If you want to use a custom identity:
1. Select the Custom account option then click Set. The Set Credentials dialog box opens.
2. Type the custom account name in the User name field.
3. Type a password in the Password field.
4. Retype the password in the Confirm password field then click OK.
Select Local System then click OK.
Click OK to dismiss the Application Pool Identity dialog box.

Need More Help?

"Object reference not set..." appears when setting up Control Manager (TMCM) / Apex Central Active Directory (AD) server connection to AD server