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 messages when you run an integration in Integration Manager for Microsoft Dynamics GP

Error messages when you run an integration in Integration Manager for Microsoft Dynamics GP

View products that this article applies to.

Symptoms

When you run an integration in Integration Manager for Microsoft Dynamics, you may receive one or more of the following error messages.

Error message 1

The destination could not be initialized due to the following problem: Object reference not set to an instance of an object.

Error message 2

The destination could not be initialized due to the following problem: Unable to cast COM object of type 'System_ComObject' to interface type 'Dynamics Application'. This operation failed because the Queryinterface call on the COM component for the interface with IID '{6D016638-BA35-11CF-827E-00001B27AB13}' failed due to the following error: Error loading type library/DLL. (Exception from HRESULT: 0X80029C4A (TYPE_E_CANTLOADLIBRARY))'

Error message 3 The destination could not be initialized due to the following problem. 'DOC 1 ERROR: Unable to cast COM object of type 'MSScriptControl.ScriptControlClass' to interface type 'MSScriptControl.IScriptControl'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{0E59F1D3-1FBE-11D0-8FF2-00A0D10038BC}' failed due to the following error: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)).'

↑ Back to the top

Resolution

  1. To resolve this problem, use the appropriate resolution.

    Resolution 1

    To resolve this problem, obtain the latest update for Integration Manager. Follow the instructions that are in the Readme.txt file that is included in the update. To obtain the update, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

    GP 10.0

    Partners

    https://mbs.microsoft.com/partnersource/downloads/releases/integration_manager_10_downloads_for_microsoftdynamics10.htm?printpage=false

    Customers

    https://mbs.microsoft.com/customersource/support/downloads/servicepacks/integration_manager_10_downloads_for_microsoftdynamics10.htm?printpage=false



    GP 2010

    Partners & Customers

    https://mbs.microsoft.com/customersource/support/downloads/servicepacks/mdgp2010_integrationmanager.htm?printpage=false



    Resolution 2

    Integration Manager for Microsoft Dynamics GP 10.0

    To resolve this problem, use the Add or Remove Programs item in Control Panel to repair Microsoft Dynamics GP 10.0.

    To do this in Windows Vista or Windows 7, click Start, type control in the Start Search box, and then click Add or Remove Programs in the Programs list. Click Microsoft Dynamics GP 10.0, click Change, and then click Repair.



    Integration Manager for Microsoft Dynamics GP 2010

    To resolve this problem, use the Add or Remove Programs item in Control Panel to repair Microsoft Dynamics GP 2010. 

    To do this in Windows Vista or Windows 7, click Start, type control in the Start Search box, and then click Add or Remove Programs in the Programs list. Click Microsoft Dynamics GP 2010, click Change, and then click Repair.


    Note If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.

    Resolution 3

    To resolve this problem, reregister the MSScript.ocx file. To do this, follow these steps:
1. Log on to the computer as the domain administrator. The domain administrator must have full administrator permissions.

2. Register the MSScript.ocx file. To do this, click Start , click Run , type regsvr32 C:\Windows\System32\MSScript.ocx in the Open box, and then click OK
Note If you are on a 64-bit computer, use this command: regsvr32 C:\Windows\sysWOW64\MSScript.ocx .

3. Run an integration as the domain administrator.


↑ Back to the top

Keywords: kbexpertiseadvanced, kberrmsg, kbmbspartner, kbexpertisebeginner, kbtshoot, kbmbsmigrate, kbprb, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 942750
Revision : 1
Created on : 1/7/2017
Published on : 7/2/2013
Exists online : False
Views : 179