Integration Manager Error – ADO Field Is Nothing

During a recent implementation I was using Integration Manager to load data into GP and on one occasion I got the following message in the progress window;

Integration Manager Error - ADO Field Is Nothing

I fiddled around with a few things, closing GP and reporting, closing Integration Manager and reopening it and at one point I got this error message;

Integration Manager Error - ADO Field Is Nothing

It was then that I realised that the file being used for the import was still open in Excel. Closing this file released the lock and allowed the import to run successfully.

It would have been nice if the error message was more explanatory that it was. But I just need to remember that ADO Field is nothing means a locked file.

Related posts:
Integration Manager Error: ADO Field Is Nothing
Integration Manager Error – You Must Close All Microsoft Dynamics GP Windows
Integration Manager Error: Source Document ‘GJ’ Does Not Exist
Fixing A Corrupt Account Index Master
Check Remittance Run-time error ’13′ – Type Mismatch: Follow Up
Check Remittance Undefined Symbol Error When Upgrading to Microsoft Dynamics GP 2010
Ian Grieve

About Ian Grieve

Consultant with over 8 years experience with Microsoft Dynamics GP, including related products such as Integration Manager, eConnect, FRx and Management Reporter.
This entry was posted in Dynamics, GP, Integration Manager, Microsoft and tagged , , , , , . Bookmark the permalink.

One Response to Integration Manager Error – ADO Field Is Nothing

  1. Pingback: Interesting Findings & Knowledge Sharing » Integration Manager Error – ADO Field Is Nothing | azurecurve

Leave a Reply

Your email address will not be published. Required fields are marked *

*

* Copy this password:

* Type or paste password here:

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>