Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
We are encountering the error "Microsoft Visual Basic Unexpected error (50001)" when we run the IM for GP2010 integrating to Sales Transaction. This happens to 2 other computers where we installed it. But if we run integration to other windows it is working.
Its seems to be an runtime error. When integrating to Sales transaction, a runtime error is thrown from some vba code, debug and find out the line of code. Then you will get an idea of the issue.
What's weird is that there is no error in my computer but is not working to the other computers. They have the same vba code in it.
Did you ever get an answer to this, I have the same problem.
Did you get resolution to this? My client is having the same issue occasionally but a few hours later it works fine.
This error possibly due to the Pathname inside VBA code, for your case, the VBA code pathname may be referring to your local system whereas it might not be the same in other Systems, please check if you are passing any hardcoded pathname values in VBA and try to replace it with Dynamics passage of values.
Start over with a new integration, and make it simpler. IM likes to crash on complicated integrations, or it likes to crash because it does like you... hard to say why sometimes. I use econnect sql procedures for this reason, I have more control and no crashes.
Business Applications communities