Hello:
I'm testing Integration Manager for GP 2013 R2, and it is failing due to "query timeout" errors.
The integration's query is an Advanced ODBC connection pointing to a database that is in a separate instance from the Dynamics GP databases.
The integration is actually failing due to a "Before integration" script that is, indeed, pointing to a Dynamics GP company database in GP's SQL instance. The script is trying to run a stored procedure within that database, but that stored procedure references data in a database in a separate instance.
I know that this is a broad question. But, I'm not finding anything online that speaks to a remedy.
Is there a fix for this?
This is the latest version of Integration Manager for GP 2013 R2. (Integration Manager is at version 12.00.1753).
Thanks!
John
*This post is locked for comments
I have the same question (0)Hi John,
Are you able to run the procedure manually in a reasonable length of time? Are you able to remove the script, and the error goes away in IM?
It sounds like SQL might be the culprit.
Community Member
2
babubaskaran@outloo...
2
Yng Lih
2