web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Need help in resolving: Internal Error in Microsoft.Dynamics.GP.IntegrationManager

(0) ShareShare
ReportReport
Posted on by 200

Hi All,

System is Dynamics GP 10 on XPsp3 with all current patches.

Has anyone seen this error (listed below), or know what causes it?  Steps I have tried to resolve the error:

  • Uninstall Integration Manager -> remove remaining program folders & reg entries -> reinstall and patch to Service Pack 5
  • Uninstall/Reinstall of GP
  • System restore back to date where Int Manager was working.

All of these were unsuccessfull.  At this point, I was just going to rebuild the machine, but would like some insight as to what could possibly causing this.  Only affects this particular machine (which was a recent build that is approx 2 mo old).  No software or MS updates applied from the time it was working (9/22) to the time it stopped working (9/26).

Any help would be appreciated,

Mike

Error Details:

Internal Error in Microsft.Dynamics.GP.IntegrationManager....

Source: Microsoft.Dynamics.GP.IntegrationManager.IMProvider.IntegrationContext.Initialize

Message: Retrieving the COM class factory for component with CLSID {0E59F1D5-1FBE-11D0-8FF2-00A0D10038BC} failed due to the following error: 80040154.

Number: -2147221462

Call Stack:

IntegrationContext.Initialize
Integration.IIntegration_PrepareIntegration
MenuAction.IntegrationRun
MainMod.TimerCallbackMenFunction

 

*This post is locked for comments

I have the same question (0)
  • Mike Metzler Profile Picture
    200 on at

    This is still an issue that crops up occasionally.  Anyone else experienced this?

  • L Vail Profile Picture
    65,271 on at

    I've seen this on 64-bit systems, are you running on 32 or 64?

  • Vinutha Holla Profile Picture
    705 on at

    To resolve this problem, re-register the MSScript.ocx file by completing the following steps:

    First, verify the file exists on your machine.  The file is typically located in C:\Windows\System32, or on a 64bit machine C:\Windows\SysWow64.

    Once you confirm the location, go to Start > Run

    In the Run Dialog, enter in the command regsvr32.exe C:\Windows\System32\MSScript.ocx

    (substitute your path if it is different than the above example)

    You should get the message "DllRegisterServer in C:\Windows\System32\MSScript.ocx succeeded."  Then try your integration again.

  • L Vail Profile Picture
    65,271 on at

    Great!

    It will be interesting to see if this works. I usually get the COM.CAST error (something like that) when I need to register the script.

    Leslie

  • Mike Metzler Profile Picture
    200 on at

    This issue is occuring on a WinXP 32bit system.  Unfortunately, Re-Registering the MSScript.ocx did not solve the issue.   Uninstall and Reinstall of GP Dynamics and/or Integration manager also does not solve the issue.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Community Member Profile Picture

Community Member 2

#2
mtabor Profile Picture

mtabor 1

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans