I’m running an integration to Dynamics GP and getting SQL login errors.
If you’d rather watch a video explaining this, click here.
The integration works fine on several machines, but fails from one machine with the error:
Login failed for user ‘NT Authority\System’
Sometimes the error message also fails but with the correct domain and the user is the name of the machine and not an actual user.
Login failed for user ‘eonedemo\EONE-2014$’
Why do most machines work but this one does not?
This is an eConnect SQL error and not something from SmartConnect. If it was from a Source or a SQL Tasks, SmartConnect would show the name of the task – but in this case since the error count incremented and we didn’t see a task name that it is failing at eConnect trying to log into the destination database.
This fails on this specific machine because eConnect must be installed on each machine running eConnect that will use GP destination maps.
The eConnect installation media forces you to use Window Authentication when installing the service and the installer will use whatever windows account that you enter. In order to get errors like these, the user on the eConnect for Microsoft Dynamics GP 20xx must have been changed after-the-fact.
To resolve, open up Windows Services and find your eConnect for Microsoft Dynamics GP 20xx that is installed.
In order to get the error messages listed, the Log On information must have been set to “Local System account”. Change that to a domain account per the screenshot to resolve the error as this is a Microsoft eConnect requirement. eOne would suggest reviewing the account used on the other machines’ eConnect Service and use the same account for consistency.
