Centralized Administration > Virtual Printer Driver (VPD) > Administration > SAP Integration

This chapter deals with the topic Troubleshooting for resolving configuration problems and errors at runtime.

The SAP system calls the steadyPRINT script in order to be processed in SAP via the defined submit command. The script gathers some information to provide them to the steadyPRINT OMS. Then the print job and all related meta information are transferred to the file server. From there the Windows-side steadyPRINT Server service takes over the print job to be further processed and finally forwards it to a print queue defined on the Windows print server.

The following table shows all error patterns as well as the appropriate checks and solutions:

Status/Error message

Problem

Check and solution

Job remains in status „in progress“

The print job including meta information was not transferred correctly to the file server.

	Print job files not available/complete in the specified directory on the file server. The following files must exist in a subfolder (JobID):

o	[File name].[SystemID]

o	steadyprint.log

o	XOMCMD_SAPmetadata_[JobID]_[PrintServerID].txt

	Make sure that the submit command corresponds to the steadyPRINT Center SAP profile and is correct.

	Check the log entries from /home/sap/bin/sP/spErrorLog.csv.

	Check the correctness of the entries in /home/sap/bin/sP/config.ini.

	Check whether the line ends for the steadyPRINT scripts are correct. If they are incorrect, the scripts cannot be run. The conversion procedure with the command dos2unix was explained in the instructions for setting up the scripts.

Job remains in status „in progress“

The print job including meta information was transferred correctly to the file server but could not be processed.

	Has the steadyPRINT Server service been started on the stored Windows print server?

	Is the steadyPRINT Server service running correctly on the stored Windows print server?

	Ensure the installation of the steadyPRINT Server service on the stored Windows print server.

	Restart the steadyPRINT Server service on the stored Windows print server.

	Check the steadyPRINT logs on the Windows print server (see https://www.steadyprint.com/knowledge-base_en/20142/).

Tip: Provide redundant servers for a steadyPRINT reliability including the Windows print servers (see Reliability).

Error (copyToWindows in spErrorLog.csv)

The print job could not be transferred to the file server.

	Check the log entries from /home/sap/bin/sP/spErrorLog.csv.

	Check the specified file server in /home/sap/bin/sP/config.ini.

Error (copyToWindows; NT_STATUS_HOST_UNREACHABLE in spErrorLog.csv)

The print job could not be transferred to the file server.

	Check the log entries from /home/sap/bin/sP/spErrorLog.csv.

	Check the specification for serverip and vpdprintjobpath in /home/sap/bin/sP/config.ini.

Error (copyToWindows; NT_STATUS_LOGON_FAILURE in sPErrorLog.csv)

The print job could not be transferred to the file server.

	Check the log entries from /home/sap/bin/sP/spErrorLog.csv.

	Check the specifications for userdomain, userpassword and userdomain for login to the file server in /home/sap/bin/sP/config.ini.

Error ([…] Open printer \\[PRINTSERVER]\[PRINTERNAME] with access mask […])

The print job was terminated with an error.

The specified host printer does not exist on the Windows print server.

Error (The fallback user '' was not found in the Active Directory.)

Der Druckauftrag wurde mit Fehler beendet

	The registered SAP user could not be found in steadyPRINT. In order to be found, the specified user must have a valid printer assignment or started the steadyPRINT Agent at least once.

	A fallback print job owner SAP configuration file was not defined. The fallback is to ensure that the print job can in any case be assigned to a valid user. For this, the specified user must have a valid printer assignment or started the steadyPRINT Agent at least once.

Note: In case the user cannot be assigned during printing and no valid fallback exists, the print job will be cancelled.

Error with login (No RFC authorization for function module RFCPING.)

The specified user to RFC communication is not able to log in.

Check whether the specified user is authorized to perform RFC functions.

Complete (Successfully printed)

The print job has been successfully processed by steadyPRINT OMS and sent to the Windows print spooler and printed without error.