- Have other users logged in and had their printers build fine? If so, the problem may be specific to the client machine. Please continue reading through this document for additional troubleshooting.
- Is the spooler service running on the server? If not, ScrewDrivers v3 will not build printers as the product is designed to work in conjunction with the spooler service.
- Are users connecting to an RDP (Remote Desktop Protocol a.k.a. Microsoft Terminal Services) session through the web by using the TSAC (Terminal Services Advanced Client)? If so, has the correct entry been added to either the "connect.asp" page or the "default.htm" page so that our client-side RDP dll can be called? Please refer to this link for more information.
- Are there printers (network or local) installed on the client machine?
If not, ScrewDrivers v3 will not build any into the terminal session.
- Was the client-side component installed while there was an active terminal session (ICA or RDP)? If so, the installation would not have taken. Please remove the client-side component through Add/Remove Programs, reboot the machine, and then reinstall without any active terminal sessions.
- Was the client-side component installed using Add/Remove programs under the control panel? If so, the
installation may not have taken. Please remove the client-side component through Add/Remove Programs, reboot
the machine, and then reinstall by just double-clicking the executable file.
- Was the client-side component installed on a Windows NT, 2000, or XP machine without being logged in as an Administrator? The ScrewDrivers v3 product adheres to the Microsoft requirement for being an Administrator when installing software on the Windows NT, 2000, or XP platforms.
- If the client machine is a Windows NT, 2000, or XP machine, is the spooler service running locally?
- This next set of questions only apply to environments running Citrix (Metaframe "1.8" or "XP" & the ICA
"Full Program Neighborhood Client", "Web Client", or "Program Neighborhood Agent"). The ScrewDrivers v3
has a search functionality built into the client-side component so that selection of a directory path or choice of client-side executable is not necessary. The new functionality will search all local harddrives and partitions for instances of the "module.ini" file that we make edits to so we can access the virtual channels established during a Citrix terminal session. Since, the three afore mentioned Citrix clients have a "module.ini", ScrewDrivers v3 will be able to work with any or all of them.
- Is the ICA Client that is in use at least version 6.xx.xxxx?
If not, it will need to be upgraded. ScrewDrivers v3 no longer supports legacy ICA Clients
(namely 4.xx.xxx versions).
Directory Path Reference for ICA Client Installations:
ICA "Full Program Neighborhood Client" installation defaults to C:\Program Files\Citrix\ICA Client
ICA "Web Client" installation defaults to C:\Program Files\Citrix\icaweb32
ICA "Program Neighborhood Agent" defaults to C:\Program Files\Citrix\PN Agent
- Now, based upon which ICA Client is installed, was the correct ScrewDrivers v3 client-side component used?
In addition to the client-side installation that performs a search, there are also client-side component installs available that default to specific ICA Client directory paths. One client-side component defaults to the "Full Program Neighborhood Client" path and the other defaults to the "Web Client" path. There has never been an install built for the "Program Neighborhood Agent" as it is not widely used. Please refer to the triCerat support page to obtain these specific installation executables.
So, if the "Full Program Neighborhood Client" is in use, make sure that corresponding ScrewDrivers v3 client-side component install is being used. The same applies if the "Web Client" is in use on the client machine. To determine whether or not the correct client-side install executable is being used, it is best to start the installation and take a look at the directory path location indicated on the fourth dialog box and then reference the paths mentioned above for the different ICA Clients. If necessary, it is possible to cancel the installation of the client-side component after determining which one is being used. Using the filename of the executable is another method, but that may or may not be reliable as those names are easily changed and may not have been renamed accurately.
- Have all necessary edits been made to the "module.ini" file so that we can access the virtual channels in the Citrix terminal session? The "module.ini" for each of the ICA Clients in use on the client machine will need to be checked. Use the following references to locate and check the "module.ini" for any or all of the ICA Clients in use on the client machine. The "module.ini" will reside in the last folder of each of the paths indicated by the Directory Path Reference. The second reference indicates what edits will need to be verified within the "module.ini" file.
Directory Path Reference for ICA Client Installations:
ICA "Full Program Neighborhood Client" installation defaults to C:\Program Files\Citrix\ICA Client
ICA "Web Client" installation defaults to C:\Program Files\Citrix\icaweb32
ICA "Program Neighborhood Agent" defaults to C:\Program Files\Citrix\PN Agent
"module.ini" Edit Reference for ScrewDrivers v3 Client-Side Component Installations in Citrix Environments:
//Find the section: [ICA 3.0]
--At the end of the VirtualDriver key a "ScrewDriversFXP" entry should exist as follows:
VirtualDriver= (existing entries...), ScrewDriversFXP
//Find the section: [VirtualDriver]
--You should see a key with no value as follows:
ScrewDriversFXP=
--At the end of the entire file you see the following entries:
[ScrewDriversFXP]
DriverNameWin32=sdica6.dll
- Is the ICA Client that is in use at least version 6.xx.xxxx?
If not, it will need to be upgraded. ScrewDrivers v3 no longer supports legacy ICA Clients
(namely 4.xx.xxx versions).
Copyright © 1997-2003 triCerat, Inc. All rights reserved.