Reliability function active without registered backup print server

Description of the problem

Due to a timimg problem when starting the steadyPRINT Server, the fallback mode might erroneously be activated. This problem will be solved with the new release 5.1.1 which will be available in November!

Explanation

Should the steadyPRINT Server be about to start and the print spooler not yet be running for at least 2 minutes, the internal warmup check fails and the master print server will be recognized as “offline”. Thus, in Version 5.1.0, the print spooler switches into the fallback mode. The warmup check is to guarantee that the Windows print spooler actually provides necessary information. If an external component tries to call up information immediately after the start, this procedure mostly fails as the information has not yet been completely loaded.

Solution

Workaround – In order to avoid this problem, the following points should be realized

The realization of the workaround includes three points which must be carried out in the sequences described below.

Configure steadyPRINT Server Service

Set the starting type to “delayed start” in the service settings.

SQL-queries to avoid the warmup check

Note: Should the name of the steadyPRINT database not be PrinterMap, replace it according to its naming in the following SQL queries.

INSERT INTO [PrinterMap].[dbo].[Settings](OptionName, OptionValue) VALUES('SteadySuite.SteadyPrint.Commons.Settings.Names.Server.MgmtTool.GeneralSettings.Spooler.MinimumUptime.Value', '1');

INSERT INTO [PrinterMap].[dbo].[Settings](OptionName, OptionValue) VALUES('SteadySuite.SteadyPrint.Commons.Settings.Names.Server.MgmtTool.GeneralSettings.MinimumFreeMemory.Value', '0');

INSERT INTO [PrinterMap].[dbo].[Settings](OptionName, OptionValue) VALUES('SteadySuite.SteadyPrint.Commons.Settings.Names.Server.MgmtTool.GeneralSettings.MinimumDiskFreeSpace.Value', '0');

INSERT INTO [PrinterMap].[dbo].[Settings](OptionName, OptionValue) VALUES('SteadySuite.SteadyPrint.Commons.Settings.Names.Server.PrintServer.CheckIntervals.BackupServerAvailability.Value', '0');

Manual correction of fallback mode

Note: Should the name of the steadyPRINT database not be PrinterMap, replace it according to its naming in the following SQL queries.

Perform the following SQL query for all affected print servers and replace 'PRINT SERVER NAME' by the respective print server name before:

UPDATE [PrinterMap].[dbo].[PrintServers] SET steadyAction = 0 where DistName = 'PRINT SERVER NAME'

To see which print servers are currently in the fallback mode, carry out the following SQL query:

SELECT [DistName],[Dom],[steadyAction] FROM [PrinterMap].[dbo].[PrintServers] where steadyAction = 1

Removal of entries from the steadyPRINT database after update to Version 5.1.1

Note: Should the name of the steadyPRINT database not be PrinterMap, replace it according to its naming in the following SQL queries.

After the update, the Settings for the warmup check have to be removed from the database with the following SQL queries:
DELETE FROM [PrinterMap].[dbo].[Settings] where OptionName = 'SteadySuite.SteadyPrint.Commons.Settings.Names.Server.MgmtTool.GeneralSettings.Spooler.MinimumUptime.Value'

DELETE FROM [PrinterMap].[dbo].[Settings] where OptionName = 'SteadySuite.SteadyPrint.Commons.Settings.Names.Server.MgmtTool.GeneralSettings.MinimumFreeMemory.Value'

DELETE FROM [PrinterMap].[dbo].[Settings] where OptionName = 'SteadySuite.SteadyPrint.Commons.Settings.Names.Server.MgmtTool.GeneralSettings.MinimumDiskFreeSpace.Value'

DELETE FROM [PrinterMap].[dbo].[Settings] where OptionName = 'SteadySuite.SteadyPrint.Commons.Settings.Names.Server.PrintServer.CheckIntervals.BackupServerAvailability.Value'

For any questions and support relating to the workaround described above, please contact the support.

ID: 20079 | Zur deutschen Version