Welcome to our Knowledge Base
Enter your search terms below.
Release Notes steadyPRINT 7.5.3
steadyPRINT Bug Fixes in version 7.5.3
Bug Fixes
| Bug Fix | Description |
| steadyPRINT VPD: Documents are held in print spooler | In version 7.5.2, documents that are printed via the VPD printer are held in the respective print spooler on the client/terminal server. The reason for this is a missing permission for the user to manage the documents on the respective printer. Print processing and print output remain unaffected.
However, the problem results in the fact that the spool directory is filled up which might cause the spooler to become slow or not to react at all. A workaround would be to manually delete the remaining job files. The error of the missing permissions for managing the documents has been solved and the problem has been fixed. |
| steadyPRINT VPD: Printing to vPrinter results in error message “steadyPRINT VPD no longer works” | When printing via the VPD print spooler “steadyPRINT vPrinter”, the error message “steadyPRINT VPD no longer works” might occur:
Print processing and print output remain unaffected. The window can simply be closed. The problem has been fixed. |
| steadyPRINT: Different computer accounts with identical names in Active Directory cause problems | If a computer appears several times with the same name in the Active Directory, an error in the analysis of the computer principal will occur. At the same time, all assignments for printers, Agent profiles etc. performed on the computer name will no longer work.
A computer can appear with the same name in the Active Directory if different names have been chosen for the computer account under “computer name (Prä-Windows 2000)”. This problem has been fixed. |
| steadyPRINT Center: Report “Printed pages per month” leads to the error “input string was not in correct format” | The report “printed pages per month” might terminate with the internal error “input string was not in correct format” resulting in empty pages in the report.
This problem has been fixed. |
ID: 22168 | Zur deutschen Version
