Loading...
Loading...
The validation of domain service account fails when trying to install a new MID Server. The following error message is displayed after providing the information in the "Configure MID Server Service Settings" window: Invalid Service Account The root cause of this issue is that the windows API(ValidateCredentials) for validating the credentials of domain service account is throwing an exception. Exception during service account validation. Exception: System.DirectoryServices.Protocols.DirectoryOperationException: The server cannot handle directory requests. The issue could be caused by some Active Directory configurations on the customer environment. Steps to Reproduce 1. Download the MSI installer. 2. Run the installer. 3. Give the requested details on the screen. 4. On Configure MID Server Service Settings window, provide the inputs and click on Validate settings button. Though the credentials are correct, the Invalid Service Account error pops up.
This problem has been fixed. If you are able to upgrade, review the Fixed In section to determine the latest version with a permanent fix your instance can be upgraded to. If a workaround is needed: 1. Download the MSI installer 2. Install the MID server using Local Service account 3. Go to Services 3.1 Select the MID service 3.2 Right Click and Open Properties 3.3 Change the Log On User as Domain User 3.4 Restart the service If this workaround does not fix the issue, install the MID manually. Related articles: MID Server MSI installer fails to check if any groups the user is a member of have the Logon as service right - blocking install: Service Account does not have the "Logon as Service" right Mid server startup failed with error 1053: The Service did not Respond to the Start or Control Request Create a Windows service account with "Log on as Service"
PRB1552837
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.