I got this error message forwarded to me by one of the clients after he tried to login to do some testing;
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);
Clients who have upgraded to Microsoft Dynamics GP 2010 can use the new remember user and password functionality, but what about those who have not yet upgraded?
Well, in Microsoft Dynamics GP 10, and before, you can use a login macro to automate the login process. A macro can be created by pressing Alt + F8 on the login screen and following the normal login process before pressing Alt + F8 again to stop recording. Continue reading “Automate Login To Microsoft Dynamics GP 10”
I have recently been upgrading an existing client to Microsoft Dynamics GP 2010 R2 from GP 10 SP1 on their test system. As they have lagged somewhat on versions I needed to upgrade them to GP 10 SP5 before then upgrading them to GP 2010 R2.
The databases were also being moved from a server running Microsoft SQL Server 2000 to one running SQL Server 2008; I would have preferred to move them to SQL Server 2008 R2 but due to some other business critical software to be installed on the same server, it needed to be SQL Server 2008 R1. Continue reading “Missing Data Source When Installing Microsoft Dynamics GP 2010”
We heard back from the Development Team in Fargo, who David Musgrave contacted regarding the issue we encountered with the Microsoft ActiveX Data Objects 2.7 Library.
They recommend that packages should be moved around using the Customisation Maintenance (Microsoft Dynamics GP menu » Tools » Customise » Customisation Maintenance) to Import/Export the modified reports. Rather than doing this, which runs the potential risk of leaving client machines with an outdated REPORTS.dic we have been pointing the clients at a centralised REPORTS.dic on a server and copying only the Dynamics.vba to each client (we change the reports more often than the VBA).
Using Customisation Maintenance to Import the package file to each client would have prevented the problem as it would use the Microsoft ActiveX Data Objects 2.7 Library reference on the local machine. Doing it the way we do, by copying the VBA, transfers the reference within the VBA file.
This is an issue for internal discussion and we perhaps need to change the process we use for dictionary files.
I implemented the VBA workaround for cheque remittances on a test system for another client site, to make sure they don’t see the undefined symbol error, the other day after I upgraded Microsoft Dynamics GP 10 to GP 2010 and tested the remittance to ensure it worked. amend VBA on Server 2008 R2 SP1
When the client came to test the remittance themselves on the test Citrix Server they got a type mismatch error;
It seems it is a week for Integration Manager errors. Another client has logged an error when using Integration Manager. In this case, they were attempting to load a payroll journal using the GL Trx One Source File integration Continue reading “Integration Manager Error: ADO Field Is Nothing”
We have a few customers who use it for importing journals or invoices into the system from elsewhere and occasionally they encounter errors which are more than an incorrectly formatted file so they contact the helpdesk to log a call.
One such involved the below error message regarding the source document ‘GJ’ not existing Continue reading “Integration Manager Error: Source Document ‘GJ’ Does Not Exist”