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 “eConnect Messages Not Posting To GL”
I dealt with an issue yesterday where a manual payment had been entered into Payables Transaction Entry () but was not showing up in Bank Management’s Reconciliation screen ().
The reason for this is actually quite simple, but I can’t help but feel it is a little bug like. Only payments made directly via Transaction Entry or those produced during the payment run () are posted to Bank Management. If you need to do a manual payment into Payables, or a manual receipt into Receivables, then this needs to be done via CBM Batch Entry () Continue reading “Missing Transaction In Cashbook Bank Management?”
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 “Changing The eConnect Password In Microsoft Dynamics GP 2010”
In Microsoft Dynamics GP 2010, Microsoft introduced the Reporting Ledger functionality which allows journals to be posted to one of three reporting ledgers; base, local, or International Financial Reporting Standards (IFRS).
This functionality is controlled via the General Ledger Setup window ();
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 “Integrations Via eConnect Disappearing”
One of the undocumented features of Microsoft Dynamics GP is the ability to use a custom splash screen.
The standard splash screen displayed by Microsoft Dynamics GP 2010;
Well, I’ve just finished installing SQL Server 2008 R2 and Microsoft Dynamics 2010 R2 on the Windows 8 Developer Preview and GP is exactly like it is on Windows 7. Continue reading “Microsoft Dynamics GP 2010 R2 On Windows 8 Developer Preview”
A client testing Microsoft Dynamics GP 2010 R2 prior to going live rang to say they were getting a runtime error when logging in. I dialled in and checked the home screen and couldn’t see any problem with the dynsa home screen so asked for a screenshot showing the error;
The screenshot they sent showed the below error message;
Continue reading “Home Screen Connect Error – Server Error in ‘/lus’ Application.’”
I did a test upgrade for a client recently (yes, I’ve been doing a few of these) so they could make sure everything still works and allow them to check out some of the new features.
I got this error message forwarded to me by one of the clients after he tried to login to do some testing;
Continue reading “Earlier Version of Dynamics.dic Than Installed”
I upgraded a clients test system from Microsoft Dynamics GP 10 SP3 to 2010 R2 successfully on the main system such as installing the main client and upgrading the system and company databases.
The client has a few modified reports on the system which needed to be brought across to Microsoft Dynamics GP 2010. These reports were exported from Customisation Maintenance (Microsoft Dynamics GP menu » Tools » Customise » Customisation Maintenance);
