Why does the Mekorma check print process take a long time or appear to freeze?
If the check printing process unexpectedly freezes or slows down and you are seeing the Check Password window, please review the following:
Note: The Check Password window is an expected Mekorma modal window that typically appears for a brief moment often undetectable to the eye. In cases where the print job performance is hindered the window may take longer to disappear after displaying, a symptom of a network related problem.
A few questions based on reports of Mekorma print job interruption:
1. Can you recreate the issue using the Mekorma test check feature?
2. When did the symptom(s) begin to present and have there been recent updates to the operating system whether by upgrade or updates that would correlate to the presentation of the issue?
3. What is the network print job topology? Do you print redirected via Terminal Server or is this an Azure environment, or is the setup locally with GP/workstation/printer? If not the latter, do you have a way to test to rule out a network issue?
4. What is the make, model and printer driver in use?
5. Do you have insight into the changes that may have taken place when the issue began? e.g. Windows updates, network and/or print topology changes.
6. When you print the job to pdf file, does the problem resolve?
7. Are you experiencing any issues related to printing of graphical objects on Mekorma checks/stubs including signatures, logos and/or MICR line regio
8. If the issue appears along with the Check Password (modal) window hanging and/or 'Print Queue Initializing' message on the Mekorma Check Printing window and you have the Mekorma Image Archive enabled (verify this at Mekorma>System>System Options then please report the following results from MSSQL (company level):
- select COUNT (*) from ME240447
- select COUNT (*) from ME240457
To provide context on this topic, since the initial release of the Archive System many years ago we have optimized data archiving process. Therefore, if you had been on an old install (2013 and prior) for many years you would likely inherit the issue. For more information on the Archive please see Knowledgeable article:
If you would please take note of the above and report to us as complete as possible, this will help expedite the troubleshooting process.
Also, a word on printing in Terminal Server with Mekorma:
The Mekorma print engine is not supported with the Microsoft EasyPrint driver. Please change the EasyPrint driver policy to first find a suitable printer driver to install to the target printer. The Mekorma Print Engine makes API calls for the Mekorma print job that other applications do not call. Also of consideration, there is a layered system where the .net print document class, operating system and local print driver require information to be translated. The Microsoft EasyPrint driver likely provides instruction the printer cannot understand based on the way our software utilizes the API and communication among software components. Please use the printer manufacturer's native print driver and disable the Microsoft EasyPrint driver in order to print Mekorma checks.
Configuring the Group Policy:
Log in as Admin and go to the Group Policy settings that have been added for Terminal Services printing. These policy settings are located in the following node of the Local Group Policy Editor: At the start key type gpedit.msc
The path is: Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Printer Redirection
To: For Use Terminal Services Easy Print printer driver first <-- We recommend that you set this to: Disabled
Disabled: If you disable this policy setting, the Terminal Server will try to find a suitable printer driver to install to the client printer. If the terminal server does not have a printer driver that matches the client printer, the server will try to use the Terminal Services Easy Print driver to install the client printer. If for any reason the Terminal Services Easy Print driver cannot be used, the client printer will not be available for the Terminal Services session.
Log out and log back in.
Once you log back in you will see that your printer is using its native print driver (from Control Panel), and Mekorma MICR checks will print.
The technical website for this information is: http://technet.microsoft.com/en-us/library/cc753853(v=ws.10).aspx
Please note:
A policy value set as "Not Configured" will IGNORE any previous settings made by policies lower in the chain.
So if your LOCAL policy sets a Target Group, and your Organizational Unit policy has client-side targeting (and group names) set to "Not Configured", the LOCAL policy setting will remain in force.