The SmartConnect Configuration tool is used to Create/Install the eOne SmartConnect Service which runs the scheduled maps for SmartConnect.
The window seems fairly straightforward in that you enter the Service User and Domain credentials and then the password and then press the Validate Credentials.
The code behind the Validate Credentials uses the .net PrincipalContext() class to validate the user credentials before creating the service with a potentially invalid user/password.
AccountName is not a valid user or the password is incorrect.
We’d expect this to work as the Service User is entered (with just that value and not domain\user) but, as above, sometimes that fails for unknown reasons.
What we’ve have to do is sometimes try to change the user & domain settings in different ways to get it to validate as the “Save” button won’t be enabled until validation is successful.
In this example, the “Service User” was entered in as user@domain.com AND entering the Domain – but I’ve run into multiple times where validation would fail unless the service user was entered as domain\user and leaving the Domain field empty.
Because of this unusual configuration of Domain and User, this does give us a second issue when pressing the Save button for SmartConnect Configuration to create the service and add the account.
Leaving the window in this configuration and pressing the Save button, we get the error:
Could not Install Service. The account name is invalid or does not exist, or the password is invalid for the account name specified.
It is a bit puzzling that for the same configuration we get both success and failure but they are different APIs being used – one for user validation and another to create a Windows Service and SmartConnect is just reporting the results of each call.
To resolve this latest error, now that the Save button is enabled, SmartConnect Configuration Tool will allow us to change the credentials entered but leave the Save button enabled.
Finally, we were able to get the eOne SmartConect Service created and started.
Steps:
If the Validate Credentials fails with an error, verify that you are entering just the Service User in that field vs domain\user and that the Domain is correct as is typical.
If that seem correct – you might have to enter the credentials differently as your system is expecting to see until validation is successful.
Once that is validated successfully, if necessary, switch the credentials to be the “standard” User, Password, Domain per the screenshot and Save to create the windows service.
