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”
One of the issues which has annoyed me about Windows 7 for a while now has, since I started writing this blog, moved on from being an annoyance to being seriously aggravating. It’s a meme I don’t really like but it does perfectly convey my emotions;
This particular problem is going to occur if you either do not have Microsoft Office installed or, on an x64 OS, you have installed the x86 version of Microsoft Office when you try to install the Management Reporter Migration Wizard (in particular Microsoft Access);
I recently fielded a call from a client who had copied their live database across to test so they could do a reconciliation of Purchase Order Processing accruals to the General Ledger accrual account without having to chase a moving target as new transactions were processed. Continue reading “Problem Posting General Ledger Batches In Test Company”
I upgraded a customer to Microsoft Dynamics GP 2010 a couple of weeks ago and they have started to explore some of the new features. After fixing their payment run problem they enabled the new functionality for emailing remittances. Continue reading “Not Privileged To Run this Report Error in Payables Select Checks”
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.
I have just returned from customer site where I did an upgrade of Microsoft Dynamics GP 10 to Microsoft Dynamics GP 2010 (I wish they’d called it GP 11 as the current nomenclature confuses customers) and got the error I often get when upgrading or installing GP on Windows 7 or Windows Server 2008 systems and have forgotten to do one of two very simple things. The explanation of the two things later, but first, the error message;