Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Error message when you run an integration or when you preview the source query in Integration Manager for Microsoft Dynamics GP 10.0: “ADO Field is nothing”

Error message when you run an integration or when you preview the source query in Integration Manager for Microsoft Dynamics GP 10.0: “ADO Field is nothing”

Source: Microsoft Support

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION THAT IS CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED TO SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

↑ Back to the top

Symptoms

When you run an integration or preview a source query in Integration Manager for Microsoft Dynamics GP 10.0, you receive one of the following error messages:
ERROR: ADO Field is nothing.
The following problem occurred while attempting to open Query ‘queryname’: ADO Field is nothing.

↑ Back to the top

Resolution

To resolve this problem, follow one of these resolutions:

Resolution 1:

Obtain the latest service pack for Integration Manager for Microsoft Dynamics GP 10.0.


Partners

https://mbs.microsoft.com/partnersource/downloads/releases/integration_manager_10_downloads_for_microsoftdynamics10.htm

Customers

https://mbs.microsoft.com/customersource/support/downloads/servicepacks/integration_manager_10_downloads_for_microsoftdynamics10.htm

Resolution 2:

Make sure that the column names in the source data contain no Microsoft Jet reserved words. For a complete listing of Microsoft Jet reserved words to avoid in your column heading, see the following:http://support.microsoft.com/kb/321266

Resolution 3:

Make sure that your column names in the source data contain no special characters. The column names must only consist of alpha-numeric characters.

Resolution 4:

This error can occur if the data type of a column was changed that is used in the Query Relationship window. Open the properties for each source and then click the Refresh Columns button on the Columns tab. After you refresh the columns, verify the mapping of the integration and the Query Relationship window are still correct.

↑ Back to the top

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.

THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

↑ Back to the top

References

↑ Back to the top

Keywords: kberrmsg, kbexpertiseadvanced, kbtshoot, kbprb, kbmbsquickpub, kbnomt, kbnoloc, kbmbspartner, kbmbsmigrate, kb

↑ Back to the top

Article Info
Article ID : 954632
Revision : 3
Created on : 3/30/2017
Published on : 3/30/2017
Exists online : False
Views : 79