We are trying to use eConnect with our GP2016 install. The GP2016 app and eConnect are on one server and the GP 2016 database is on other server. The GP database is a named instance on the SQL server. We have all the correct security settings for the user we are using for the connection between eConnect and the SQL Server. We set up eConnect properly using the named instance as the server and Dynamics as our System database. However, when eConnect trys to log on to the SQL server it is going to the Default instance and not the named instance. We can see this in the default instance SQL Logs where the login fails because of course that user doesn't exist in the default instance. Is there some configuration change we are missing in eConnect to make it go to the named instance instead of the default instance?
Thank you!
*This post is locked for comments
I have the same question (0)
