Integration Manager 2016 ERROR: Unable to open source queries because Query 'XXXXX' is not found in the database. - ADO Field is nothing.

(0) Share

Report

Posted on by WCJMON

We receive the "ERROR: Unable to open source queries because Query 'XXXXX' is not found in the database. - ADO Field is nothing". When attempting to integrate multiple batches from a SQL DB. I have researched the this error and have check off every possible cause that I have found so far. It seems to be a timeout issue as the integration seems to only fail when there are lots of batches. When we decrease the number of batches it goes through fine. I have had no luck in finding if there is a way to increase the timeout in IM.

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (0)

Richard Wheeler 75,848 Moderator on at

Like (1)

Report

Try UseOptimizedFiltering=False. You willfind this in your Microsoft.Dynamics.GP.IntegrationManager.ini & the Microsoft.Dynamics.GP.IntegrationManager.IMRun.ini files

Was this reply helpful? Yes No
WCJMON 55 on at

Like (0)

Report

Hi Richard. Thanks for the reply. I was hoping you could shed a little more light on what that will do. I have a decent idea, just from the wording, but I wan't to make sure I understand how that could possibly address our issue. (Not an expert in IM)

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

IM has trouble with large amounts of data. So the less you ask it to do the better the chance for success. Whenever I see IM acting in an odd way I turn this option off.

Was this reply helpful? Yes No
WCJMON 55 on at

Like (0)

Report

I cannot find this file, Microsoft.Dynamics.GP.IntegrationManager.IMRun.ini on the server. Is there a specific path I can find that file under?

I was able to edit the Microsoft.Dynamics.GP.IntegrationManager.ini but that had no affect.

Was this reply helpful? Yes No
WCJMON 55 on at

Like (0)

Report

I copied the Microsoft.Dynamics.GP.IntegrationManager.ini and created the "IMRun.ini". Unfortunately, this still did not correct our issue. I've even increased the CommandTimeout in hopes that would help.

Was this reply helpful? Yes No
Suggested answer

Frank_Heslin 895 on at

Like (0)

Report

Both ini files should be in the same folder. There are also a client-side versions of these files.

Was this reply helpful? Yes No
WCJMON 55 on at

Like (0)

Report

Thanks Frank.

Both ini files are indeed in the same folder and are located on the clients machine. However, being that you made the distinction between the client-side and presumably the server-side. Should the files be edited on the Server-side as well?

Was this reply helpful? Yes No
WCJMON 55 on at

Like (0)

Report

Looks like we narrowed the issue down to a long running source SQL view that the Integration calls. We are looking at ways to improve that, but in mean time would like to increase the time out in IM. I edited the CommandTimeout in both .ini files on the client side, but it doesn't seem to be taking affect. Do I need to do the same on the server side?

Was this reply helpful? Yes No
Frank_Heslin 895 on at

Like (0)

Report

I haven't had to change the timeout in forever, but I would make sure the settings are the same on the server & the client to avoid conflict.

Was this reply helpful? Yes No