eConnect OutGoing Service: Cannot open database "TWO" requested by the login. The login failed. Zillions of errors in the event log.
Naturally, the database does not exist in our installation. It must have been deleted in SQL Server but not in GP
eConnect OutGoing Service: Cannot open database "TWO" requested by the login. The login failed. Zillions of errors in the event log.
Naturally, the database does not exist in our installation. It must have been deleted in SQL Server but not in GP
The 'new' ClearCompanies script can be found at this article:
How to remove a company that is no longer being used - Dynamics GP | Microsoft Learn
The direct download link to it is here:
Thanks
In my case the issue was that there remained references to sample database 'TWO' in the eConnect config files. I replaced those with references to our production database and the errors stopped filling up the event log.
In my case also, TWO already did not exist in [DYNAMICS].[SY01500]. Still, I am sure that ClearCompanies is invaluable in other cases. Can you point me to the latest version of the script? All I have been able to find is
www.gpug.com/.../DownloadDocumentFile.ashx
Thanks for your help.
If the TWO database shows in the GP system tables, but does not exist in SQL Server, I'd run the ClearCompanies script to remove it, that way nothing is seeing TWO mentioned and then looking for it, causing problems.
For example, this would cause GP Utilities to hang looking for the database should you try and do an upgrade.
Once you do that, then I'd see if that resolves or changes this eConnect Outgoing error.
Thanks
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,280 Super User 2024 Season 2
Martin Dráb 230,214 Most Valuable Professional
nmaenpaa 101,156