Ramblings of a Dynamics GP Consultant
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
In this post I discussed changing the password in eConnect 10. However, changes were made to eConnect 11 which means the password is not changed in the same way when using Microsoft Dynamics GP 2010.
eConnect 10 is a COM+ application while eConnect 11 is a Windows Communication Foundation (WCF) service-oriented application. This means the password change is a different process although it must still be done in two places. Continue reading
When we install Microsoft Dynamics eConnect 10 we also do so using a specially created Windows Domain user, DynamicsGPUser, which has the password policy disabled so the password never changes.
It turns out that despite this user only being used by the eConnect service, some client’s still prefer to change the password occasionally. Changing the password is a relatively simple thing to do, so long as you’re aware that the password is stored in two places. 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
We use eConnect to post journals from external systems into Microsoft Dynamics GP. After working fine for over a year, a customer site recently had transactions posted via eConnect vanishing.
There were no entries in the Journal messages under eConnect_Incoming Private message queue in Computer Management or in the eConnect section of the Windows Event Viewer. Once the message had left the client machine no trace could be found.
