Notifications
Announcements
No record found.
*This post is locked for comments
Hello Robyn,
Did you run the repair on the Dynamics GP client install as directed in step 2 of the KB article? You mentioned you ran a repair on the IM install, but what really needs to be repaired is the GP client.
This error typically occurs when the Dynamics.exe is not properly registered in the system registry. If the GP client repair does not do the trick, then manually reregister the Dynamics.exe by going to Start > Run. Clear out any text in the run dialog. Then browse out to the Dynamics.exe and drag it onto the run dialog. This will fill in the exact path and file name. Then after the text that was filled in add /REGSERVER.
You command should resemble the following, only you will most likely have a different path, so don't copy and paste my example:
If all goes well, you will not see any dialogs and your cursor will change to the Wait cursor for about 2 seconds. Then try your integration again.
Are you running a 64-bit machine? If you are, the msscript.ocx file that you need to register is located in the sysWOW64 folder.
Was this resolved? We are having the same issue? We can not do step 2 in the KB article as we have some customization. We have re-registered the EXE, has anyone heard of it losing this and having to re-register again?
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Community Member 2
mtabor 1
Victoria Yudin 1
