Ramblings of a Dynamics GP Consultant
I’ve spent a fair bit of time recently importing data into Microsoft Dynamics GP using Integration Manager with which I have encounterd a few different error messages (ADO Field Is Nothing, All GP Windows Must Be Closed and Source Document Doesn’t Exist).
The latest error I’ve encountered related to the MSScriptControl;
During a recent implementation I was using Integration Manager to load data into GP and on one occasion I got the following message in the progress window;
The morning opened with a feeling of déjà vu. A client testing Microsoft Dynamics GP reported that transactions they were posting in an external system were not appearing in GP.
After checking out the other issues I’ve seen recently (Domain Trust issues, Windows Updates restarting MSMQ and timeouts) without luck I expanded the investigation. Continue reading
A couple of weeks ago, a client was testing Microsoft Dynamics GP 2010 R2 and reported that some of their postings from an external system were not arriving in GP (these postings are transferred using eConnect).
When I installed eConnect I enabled Journalling on the econnect_incoming queue so we would have a record of messages which had been submitted. After receiving the error I went to make sure the messages had reached the GP server () Continue reading
As well as using eConnect to integrate journals from an external system into the GL, we also use it to integrate invoices into Payables Management. Overall we have far fewer problems integrating transactions via eConnect than we had in the past using Integration Manager, but we do still encounter some problems; usually with transactions being posted in the external system and then disappearing.
This is sometimes a more exotic reason but is usually an issue with the eConnect service needing to be restarted. When we first started using eConnect we often had problems when the server was rebooted as the eConnect service was starting before the MSMQ service and didn’t then function correctly.
To fix this issue we added a dependency to MSMQ on the eConnect service which ensures the eConnect one does not start until MSMQ is ready. This particular fix has just resulted in a site posting invoices in an external system which didn’t arrive in Microsoft Dynamics GP. Continue reading
Earlier today Microsoft launched their Microsoft Office 365 productivity suite which combines Office, SharePoint, Exchange and Lync in a cloud based version of their earthbound variant.
The service, which replaces Microsoft Business Productivity Online Suite, was launched today by Microsoft CEO Steve Ballmer in a live webcast with over 20 partners already signed up to resell the service alongside their own services.
Kurt DelBene, president, Microsoft Office Division said, “Our partners represent some of the best-known, most-trusted brands in their local markets. Our customers will be able to rest easy knowing their cloud services are backed by Microsoft and some of the greatest service providers in the world.”
Microsoft Dynamics GP and Office 365 work together now! Microsoft Dynamics GP leverages Office 365’s functionality, such as reporting and Excel-based analysis, presence and instant messaging, transaction initiation through Lync, and many of the other features of Office that you have come to enjoy when deployed on-premises, but now available through the Cloud with Microsoft Office 365.
With Microsoft Dynamics GP, you build a foundation for the future that goes beyond standalone applications to extend their traditional ERP systems throughout their organization and into the cloud.
