Design and content by 4-Tech-Engineering © 2017                                                                                                                           


Unix, DOS, Windows 7/8/10,Server and Android are trademarks under CopyRight of the relevant companies.

Impressum

Software Engineering Services
... simplify your business
AutoPrint

Known Issues


K1: AutoPrint does not print when running as Windows service. As a desktop application everything works fine.



Error Messages

The following messages may show up during the setup procedure or while in active operation modus. You may also check the AutoPrint.log file for recent error messages.


E1:  AutoPrint message: “The Target Printer <printer name> is not defined”

E2:  System messages: “Unable to load FreeImage32.dll” or “Unable to load MSVCR100.dll”






E1:  AutoPrint message: “The Target Printer <printer name> is not defined”


This message is issued if a printer that was successfully set up before, is no more accessable 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
        eqivalent content



These messages may show up on newly installed Windows systems.


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



K1: AutoPrint does not print when running as Windows service. As a desktop application everything
       works fine.


Some users reported related issues, especially when AutoPrint is installed on Windows Vista, 7 or higher. The problem is usually caused by the fact that the designated printer is not accessible for the owner of the service. By default the service owner is a local system account with no printers. This gap can be closed easily by the following steps.

(1) If AutoPrint Professional is yet running as Windows service: first Stop service and then...

(2) Uninstall the service through the AutoPrint General setup tab.

(3) Now re-install the service: before klicking the Install service button enter the Account name and Password of a registered Windows user, who owns all necessary
     privileges to use the designated printer and to modify its driver settings. You may double-check the privileges on the printer properties side (Windows).


The later change of  the service owner settings may alternatively be performed by using the standard Windows Services management console.