SQL Server Collation
Description of the problem
CreateSteadyDB does not install a new Database and fails with the error “Error installing a new Database: Invalid object name ‚information_schema.columns‘.
Importing a new license
Description of the problem
We have extended our license volume by additional Windows CAL licenses so that steadyPRINT can be provided to all users in our company. We have realized, however, that after the import of the new licenses some clients are still unable to apply the license and thus to get the printers connected. Could you provide further assistance?
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.
Creating printer connections based on FQDN
Problem description Due to an internal changeover, we would like to create the printer connections with the FQDN, e.g. „\\printserver01.steadyprint.com\printer01“. Is it possible to adjust the name when connecting the printers via steadyPRINT?
Branch Office print server no longer available
Description
If you are using Branch Office Server licenses, please contact your account manager or our support team as these licenses have been eliminated and the functionalities are now provided in a different way.
Incorrect Client name after taking over session
Description of the problem
It may sometimes happen that in a terminal server environment the client name is not correctly determined when reconnecting the session from another computer.
Scenario:
- The user logs on to the terminal server. The client name is correctly identified.
- The user logs on to the terminal server via another computer and takes over the existing/disconnecte session. In this case the client name from the first session might remain.
If computers are now assigned via the client name, they will possibly be incorrect as the new client name has not been determined correctly.
Required ports for Communication
Description of the problem
steadyPRINT needs a range of shared ports for the communication with different systems.
Database backup with steadyPRINT Center fails
Description of the problem
We use the automatic steadyPRINT Agent Distribution and tried to perform a backup of the steadyPRINT database. Unfortunately, we receive the error message „[…] Access denied. […]“. Can you provide further assistance?
Agent remains in offline mode after update
Description of the problem
Since the update of our steadyPRINT database to Version 5.2.0, the old steadyPRINT Agents (Version 5.1.0) can no longer access the database and remain in offline mode (grey symbol in task bar).
Relocation of database
Description of the problem
This article describes the relocation of the steadyPRINT database to another database server.
