Troubleshooting

A P P E N D I X C

Troubleshooting

Printer Caching

If a user changes the driver for a printer, the settings are not restored.

To restore the settings, use the same printer driver that was used when the settings were changed.

Caution - Use of a different driver, even if no settings are changed, can invalidate settings stored for that printer with any previous driver.

Printer Not Visible in Windows

If a Sun Ray printer specified on the Solaris or Linux command line is not available on Windows (not visible in the Printers and Faxes View), the user should confirm that the printer driver name is correct and installed on the Windows server.
See Making Sun Ray Printers Available to Windows.

Windows Printing

If a Windows job does not print, whether on a local or a network printer, the user should contact the Windows system administrator.

Solaris or Linux Printing

If a job fails and cannot be diagnosed and fixed with the ordinary Unix remedies (lpq, lprm, etc.), the user should contact the appropriate system administrator.

Sun Ray DTU Local Printing

Users can continue to send jobs from Solaris or Linux applications to printers locally attached to their Sun Ray DTU. To enable access to printers attached to the Sun Ray DTU for Windows jobs, the user must specify the printer with the uttsc CLI.
See Printing and the uttsc man page.

Error Messages

Sun Ray Connector error messages and their meanings are listed in TABLE C-1.

TABLE C-1 uttsc Error Messages
Message	Comments
`Error (%d): Unable to establish data store connection.`	The Sun Ray Connector was unable to open a connection to the Sun Ray Data Store. Ensure that the SRDS has been configured for Sun Ray software and is reachable. Also, ensure that the Sun Ray Connector has been successfully configured before launching it.
`Error(%d): Unable to determine SRSS version.`	SRWC could not determine SRSS version information. Ensure that SRSS 4.0 or above is installed and configured successfully.
`Error(%d):` Unable to launch Sun Ray Connector. `Only SRSS 4.0 and above are supported.`	SRWC 2.0 is supported only on SRSS 4.0 and above. Ensure that the correct version of SRSS is installed.
`Sun Ray session is not connected, please try again.`	Ensure that SRWC is being launched from a valid connected Sun Ray session.
`Cannot obtain DTU MAC address.`	SRWC was unable to contact the Sun Ray Authentication Manager to retrieve the DTUs MAC address. Ensure that this daemon is reachable.
`Error: Sun Ray Token ID cannot be determined. Sun Ray Connector can only be launched from a Sun Ray session.`	SRWC was launched from a non-Sun Ray session (e.g., telnet or console). It can only be launched from a connected DTU session.
Unable to create new audio device. Using default audio device.	`utaudio` failed to create a new audio device. Check the messages logged by utaudio for more information. SRWC will try to use the default audio device for the session.
Device <device_name> is not allocated. Audio will not work in this session. Continuing..	On Solaris Trusted Extensions platforms, if the default audio device is not allocated, then SRWC will not be able to use any new audio device or the default audio device. In this case, the SRWC session will proceed but without audio support.
Warning. Printer preferences will not be stored. Please run uttscadm to complete configuration before launching Sun Ray Connector.	If `uttscadm` has not been run before the Sun Ray Connector is launched, the printer preferences as sent by the Windows Terminal Server will not be stored and hence cannot be later reused. This is not a fatal error; the session will continue to be launched.
Unable to connect to Sun Ray Connector Proxy. Please ensure uttscadm has been run before launching the Sun Ray Connector.	Make sure the proxy daemon (`uttscpd`) is up and running. If the Sun Ray Connector is launched before `uttscadm` has been run to configure it, then the Sun Ray Connector Proxy is not reachable. This message can be seen on Solaris systems only.
Unable to launch Sun Ray Connector. Please ensure utconfig has been run before launching the Sun Ray Connector.	If Sun Ray Connector is launched without having configured Sun Ray Data Store using `utconfig` (from Sun Ray Server Software), then the connector cannot be used.