Design and content by 4-Tech-Engineering © 2024                                                                                                                           
Unix, Google, Zebra, Windows 7/8/10/11/Server and Android are trademarks under CopyRight of the relevant companies.

GDPR / DSGVO Policy

Impressum

Software Engineering Services ... simplify your business

Error Messages


In the vast majority of installations you will not see any error messages. Nevertheless, faults may occur if unforeseen circumstances in the system environment lead to restrictions on resources, access rights or remote accessibility. You may also check the AutoPrint.log and AutoPrintService.log file for former error messages. Not all error messages are critical, some just inform about temporary faults which usually disappear with the triggering event after a short time.

The following list provides helpful information on the most important error messages Applies to present versions 8+                   For previous versions see below.

E1:  AutoPrint message: “The Target Printer <printer name> is not defined”  Applies only to versions 7 and below.

This message is issued if a printer that was successfully set up before, is no more accessible while AutoPrint in active modus, especially when running as Windows service.


E2:  System messages: “Unable to load FreeImage32.dll” or “Unable to load MSVCR100.dll” or “Systemfehler. Code: 126”
        or eqivalent content
Applies only to versions 7 and below.


These or similar messages may show up on newly installed Windows systems and with AutoPrint versions up to 7.01 published until Nov 2017.


Although AutoPrint comes with its own FreeImage32.dll, it needs the system MSVCR100.dll to properly handle it.

The MSVCR100.dll is part of the Microsoft Visual C++ 2010 Redistributable Package (x86) which is normally installed and registered by many other applications, which usually live on a today’s Windows computer.


You may close the gap by downloading and installing the MS Visual C++ 2010 Redistributable Package (x86) through the related Microsoft support link: http://www.microsoft.com/en-au/download/details.aspx?id=5555

Error No

Error message

Known causes

Recommended action


[E000]


Access permissions in the AutoPrint database are insufficient for the current user

Message persists on every AutoPrint start.


(1) Recent Windows OS updates or
    Group Policy modifications

(2) AutoPrint was started by a
    different user (even administrator)
    with insufficient privileges.


(1) Reboot the computer/server. This action will update the access policy base.
     

(2) Manually adjust the access privileges for the currently logged-in user.
     Full access is required for the hidden directory  C:\ProgramData\AutoPrint8
     and its files and sub-folders.
     For more information see also the Installation guide.


[E015]


Database blocked by another process.


(1) The database is temporary busy.

(2) The local AutoPrint database
     is write protected.



(3) There was an error during a
     database write attempt.


(1) Update to the latest AutoPrint relase version 8.6.1 or above.

(2) Check if the database is currently accessed by another application, i.e. by a
     external SQLite-database-manager.
     Check if the files in C:\ProgramData\AutoPrint8 are ready for
     reading/writing under the current user account.

(3) No action yet. Just wait a few seconds.
     If the message persists for minutes, close and restart AutoPrint.
     If the message persists, check the print file name for unsupported characters.


[E201]

Input file is not yet accessible or occupied by another process.

(1) The input file arrived in the input
     folder, but is not yet released
     by the sending process.
     This may happen with huge
     files and/or slow network or cloud
     attached connections.


(1) Wait a few seconds, AutoPrint will keep retrying frequently until the file is
     completed.
     If the message persists, check the input folder (file arrival, folder and file access
     privileges).

[E400]

Printer is currently not accessible. Please check your Windows setup.

This message usually warns about temporary printer path bottlenecks.
It can be ignored if it shows up only rarely
and all print jobs are finally being completed.

(1) The target printer is (currently)
     not available or not responding.
     This may happen with remote
     printers and/or  slow network
     connections or if high loaded
     printers respond delayed.

(2) The printer spooler reports a
     temporary busy-condition, either
     for itself or for the local or
     remote printer.

(1) Normally, no action is required. Just wait another few seconds.
     If the message persists for minutes, check if the printer is online and all right
     through the Windows printer control panel.
     
     Recommendation 1 - Update to the latest AutoPrint relase version
     Especially if your current version is below 8.6.1 the update can help avoiding
     apparently random unhandled input files under frequent E400 conditions.

     Recommendation 2 - Spooler monitoring
     For a better control of the printer load balance each AutoPrint channel can be setup
     to go into pause while the printer spooler is reporting a certain number of open print
     jobs.
     Open AutoPrint > Setup > Input folder and set a max. number >0

     
 
     Recommendation 3 - Local printer driver
     If the printer is accessed through a remote print server, all print data is often being
     sent to the remote server driver/spooler. Consider the installation of a local printer
     driver/spooler on the AutoPrint computer.

[E750]

AutoPrintPC
Process could not be started.

 

The application/service was not able to launch the temporary child process AutoPrintPC.exe, which is responsible for the printing output.
It is very likely that there are system policies or security functions that block this process.

(1) Start the AutoPrint application with admin privileges and compare.
(2) Check the Windows Group Policies for  possible restrictions for applications to start
     secondary child processes. Eventually explicitly allow AutoPrint.exe or
     AutoPrintService.exe to launch AutoPrintPC.exe.

(3) Check any virus scanners for blockages when calling AutoPrintPC.exe

(4) Check any 3rd-party security endpoint software for blockages when calling
     AutoPrintPC.exe

[E751]

AutoPrintPC
Process could not be completed.

 

The temporary child process AutoPrintPC.exe, which is responsible for the printing output, stopped working unexpectedly and for no apparent reason.
It was terminated forcibly.

It is very likely that the print job failed.

(1) Start the AutoPrint application with admin privileges and compare.
(2) Check the Windows task manager for possible resource flaws during printing.
(3) For huge or multi-page input files: increase the processing timeout value
     to allow a longer processing time (Setup > System > Printer spooler).
(4) If the error occurs after a long period of trouble-free operation, a recent OS update
     is probably the cause. Please reboot the computer/server.

[E752]

AutoPrintPC
Process was forced to terminate.

The temporary child process AutoPrintPC.exe, which is responsible for the printing output,
did not close properly due to a transient inter-process communication fault.
The affected process was to be terminated forcibly, although the print job is still being completed correctly.

(1) Update to program release version 8.12.10 or higher.


E1:  AutoPrint message: “The Target Printer <printer name> is not defined” Applies only to versions 7 and below.
E2:  System messages: “Unable to load FreeImage32.dll” or “Unable to load MSVCR100.dll” or “Systemfehler. Code: 126”  Applies only to versions 7 and below.