Database cache in the steadyPRINT reporting

Description of the problem

In the following, the steadyPRINT reporting function as of version 7.0.0 is to be specified.

Read more

Acceleration of the start process

Description of the problem

As in some environments there might be delays during the login process of the steadyPRINT Agent due to different libraries and program dependencies, Microsoft offers the option to have *.dll-files loaded to the so-called Global Assembly Cache (for more information click here.

Read more

Updating printer properties of BranchOffice printers

Description of the problem

We are comprehensively using BranchOffice assignments in steadyPRINT. We have noticed that settings made on the print server are transferred to the Client and then to the BranchOffice printer with a delay. Generally this is not a problem for us but we would like to find out the reason.

Read more

Print spooler hangs and uses high amount of memory

Description of the problem:

We have noticed that our print spooler sometimes hangs on a terminal server and no one is able to print. Moreover, we have realized that the memory usage of the affected spoolsv.exe partly grows to 1 GB. In some cases this problem even leads to the freezing of the whole system. Could you please provide further assistance?

Read more

When does steadyPRINT update printer connections?

Description of the problem

The steadyPRINT Agent is responsible for connecting printers on the Client. The assigned data from the database is analyzed and finally the respective printer connections are created. Generally this means that the steadyPRINT Agent is mandatory for the printer administration on the Client via steadyPRINT. Currently, there is no other way to provide printers.

Read more

High load on database server despite high values in performance profiles (fixed in Version 6.5.0)

Known Issue Version 6.1.3

Description of the problem

We are a company with more than 2000 users and the database is unnecessarily loaded due to the number of used steadyPRINT Agents. By default, the database is queried every 15 seconds to identify modifications to the printer configuration. Therefore, we configure the query values in the performance profiles as follows:

– Update printer connections: 86400 seconds (1x per day),
– Update session information: 86400 seconds (1x per day).

Unfortunately, the configuration of the values has not led to any improvements of the database performance. Could you please provide further assistance?

Read more

Print server communication slow

Description of the problem

Under Windows, the print server communication is set up in a blocking and synchronous way. How fast the individual print server functions are finally performed depends on the network as well as on the print server configuration and printer driver implementation. This might result in long lasting queries for the determination of information related to a printer and print server.

Read more

Connecting printers takes a long time

Description of the problem

We have realized that it sometimes takes a long time to connect printers partly via steadyPRINT or via the Windows “devices and printers”-view. Moreover, the setting of the pre-defined default printer via steadyPRINT is delayed. After restarting the print spooler on the Client, the default printer is immediately set. Can you provide further assistance?

Read more

Bandwidth consumption by steadyPRINT

Description of the problem

Bandwidth consumption determined for steadyPRINT Agent:
Broadcast: 94 bytes per second
Reception: 32 bytes per second

Read more