Slow Opening Windows In Microsoft Dynamics GP

Microsoft Dynamics GPI recently implemented Microsoft Dynamics GP for a client who is a UK subsidiary of an American company. This client is a heavy user of the Inventory Control module with over 30,000 items (you’ll see the relevance of this soon).

Shortly after the go-live, users started reporting that windows were opening very slowly; for example, it was taking almost 2 minutes to open the Sales Transaction Entry window. I sat with one of the users and looked at the problem with them; it took a few minutes, due to the slowness, of checking various windows before realising that it was the windows with an Item Number field on them which were slow opening.

I did a quick search online and found a post on Dynamics Code Blocks by Tim Wappat where he had encountered a similar issue which was being caused by the AutoComplete function; this would make sense as by default the AutoComplete will remember 10,000 entries per field.

Which with over 30,000 items and a couple hundred sales orders being processed everyday meant the AutoComplete was quickly building up for each user.

Tim’s solution seemed to be a little more convoluted than I woulr have expected and involved deleting files in the Windows profile. I did a test with one of the users, by deleting the AutoComplete entries via User Preferences (Microsoft Dynamics GP menu >> User Preferences) and clicking the AutoComplete button (ringed in red):

User Preferences

Continue reading

Integration Manager – Cannot Create ActiveX Component

Microsoft Dynamics GPI’ve probably said this before, but Integration Manager can be both very useful and also most infuriating, because when you get an error the error message usually isn’t useful.

However, my most recent problem with Integration Manager did actually produce a useful error message:

Integration Manager - Integration 'Invoices' is not ready to run due to the following problems: The destination could not be initialized due to the following problem: Cannot create ActiveX component.

Integration Manager

Integration 'Invoices' is not ready to run due to the following problems:
- The destination could not be initialized due to the following problem:

Cannot create ActiveX component.

I did a search and found a most useful KB article from Microsoft which detailed the problem (Microsoft Dynamics GP hadn’t been written to the registry correctly) and also the solution.

I read the whole article and decided to try a shortcut of starting with step 3 of re-registering the Dynamics.exe. To do this open a Run or Command Prompt and type the following (this particular problem was encountered with Microsoft Dynamics GP 20103 R2):

"C:\Program Files (x86)\Microsoft Dynamics\GP2013\Dynamics.exe" /regsrver

When I retried the integration, it ran through without further problems.

Transfer Old RM Statement Emails to New Email Fields

Microsoft Dynamics GPI’ve been involved with a recent upgrade of Microsoft Dynamics GP 10 to 2015. Two of the new features we helped introduce is the use of Word Templates and the Email Documents to replace the old statement email functionality which was dependent on Adobe Writer.

To help the client make the transition from the old to the new, I created an SQL script to transfer the email addresses from the table, RM00106 (RM Statement Emails) used by the old Adobe Writer to the SY01200 (Address Email Master) used by the Email Documents functionality.

Continue reading

When Installing The Web Client Reboot Your Server First

Microsoft Dynamics GPThis probably seems like an obvious one, but when you’re going to install the web client for Microsoft Dynamics GP make sure that any previous installs have had a reboot done.

I had this come up recently when trying to do an install. Earlier that day I had installed a new feature on the server (in this case the Windows Authentication feature of the Internet Information Services IIS role), but not done a reboot as one wasn’t asked for.

However, the web client installation ended prematurely and it was only when I checked the Windows Event Viewer that I found the error relating to the pending reboot.

This was particularly annoying as the premature end was only after I clicked on the Install button after entering all of the required information at the preceding steps.

Based on this error, and when it appeared, from now on I am going to reboot the server I’m installing the web client before starting.

Word Templates XML Update – Make Sure Word Is Closed Before Modifying

Microsoft Dynamics GPWe had a peculiarity the other day when updating a Word template for a client. We added some new fields via Report Writer and then created a new Word Template; when then modifying the Word template the fields usually show in the XML schema, but this time we found they weren’t.

After a couple of fruitless minutes checking the modified report and creating a new version of the Word template without success I started wondering about already open applications. In particular MS Word itself was already running with an unrelated document open.

I closed down all open Word documents and, in Template Maintenance (Administration >> Reports >> Template Maintenance), clicked the Modify button; when the Word template opened the new fields were showing in the XML schema.

This is something I have experienced before without being able to pin down why which caused..shall we say…a certain level of frustration. I’m not sure why having Word open caused the XML schema not to be refreshed when creating a new document, I am pleased that at least I can void the problem by making sure all open instances of Word are closed before starting.

Integration Manager Syntax Error (Missing Operator) In Query Expression

Microsoft Dynamics GPA client recently logged a problem with our Service Desk to report that an Integration Manager integration wasn’t working; when trying to run the integration they received an error message on every line of the integration:


Opening source query...
Establishing source record count...
Beginning integration...
DOC 1 ERROR: Syntax error (missing operator) in query expression 'UCase(DATE#######) = UCase('' AND [RUN NUMBER] = ')''.
DOC 2 ERROR: Syntax error (missing operator) in query expression 'UCase(DATE#######) = UCase('' AND [RUN NUMBER] = ')''.
.
.
.
DOC 10 ERROR: Syntax error (missing operator) in query expression 'UCase(DATE#######) = UCase('21 January 2015') AND UCase([RUN NUMBER]) = UCase('HP33')'.
DOC 11 ERROR: Syntax error (missing operator) in query expression 'UCase(DATE#######) = UCase('21 January 2015') AND UCase([RUN NUMBER]) = UCase('HP33')'.
ERROR: Max Errors Exceeded at 11, Integration Canceled
ERROR: Integration canceled during document integration.
Integration Failed
Integration Results
    100 documents were read from the source query.
    11 documents were attempted:
        0 integrated without warnings.
        0 integrated with warnings.
        11 failed to integrate.

After doing some debugging of the integration, we identified the problem as being caused by the source column headers; all of which had multiple # at the end.

For example, as you can see in the above error message, DATE was displaying as DATE#######.

We went through the source removing all of the # symbols and were then able to run the integration without receiving more errors.

Enter/Match Invoice – “You must close the Select Purchase Order Items window before continuing.”

Microsoft Dynamics GPI had an oddity reported by a client just after an upgrade from Microsoft Dynamics GP 10 to Dynamics GP 2013 R2. After opening Enter/Match Invoice, entering the header information and clicking Auto-Invoice they received the following error:

Microsoft Dynamics GP - You must close the Select Purchase Order Items window before continuing.

Microsoft Dynamics GP

You must close the Select Purchase Order Items window before continuing.

I connected to their system and attempted to reproduce the error. My first few attempts failed and everything worked as expected. However, the problem did finally occur and I was able to see the problem happen a few times although it took a few minutes for me to realise the pattern.

The error message appeared when the cursor was in the lines scrolling window; if the cursor was still in a header field the error was not produced.

I have tested this on some of my test systems and the error appears to have been introduced between Dynamics GP 2013 SP2 and Dynamics GP 2013 R2.

The workaround is to make sure the cursor is not within the lines of the scrolling window and this message won’t appear.

Integration Manager Error: ADO Field Is Nothing

Microsoft Dynamics GPIntegration Manager is a great tool for getting information into Microsoft DYynamics GP, but it can also be infuriating at times with the error messages it produces when there are problems.

I recently received an error message when trying to integrate some debtors:

Show/Hide Error Message

Integration Log Integration: Debtors (ID: 1) Action: None Start Time: 09/10/2014 08:49:37 09/10/2014 08:49:37 Source: IIntegrationEngine_Run, Status Code: 0 Opening source query... 09/10/2014 08:49:38 Source: Microsoft.Dynamics.GP.IntegrationManager.IMProvider, Status Code: 33624151 ERROR: Unable to open source queries because Query 'Debtors' is not found in the database. - ADO Field is nothing. Unable to open source queries because Query 'Debtors' is not found in the database. - ADO Field is nothing. ADO Field is nothing. 09/10/2014 08:49:38 Source: FinishIntegration, Status Code: 3 Integration Failed 09/10/2014 08:49:38 Source: FinishIntegration, Status Code: 3 Integration Results 0 documents were read from the source query. 0 documents were attempted: 0 integrated without warnings. 0 integrated with warnings. 0 failed to integrate. Finish Time: 09/10/2014 08:49:38 Source Total: 0 Successfully Integrated: 0 Integrated With Warning: 0 Failed: 0 Completion Status: Incomplete Integration Status: No Documents Succeeded

Continue reading

Error Configuring The Management Reporter 2012 Legacy Connector

Microsoft Dynamics GPWhile trying to configure the legacy connector in Management Reporter 2012 recently I received an error message while the entered settings were being validated:

Validation Messages - Database configuration: The master password could not be validated against the password policy
Validation Messages - Database configuration: The master password could not be validated against the password policy

Continue reading