|Component:||INFOAS400 - AS/400 Information|
CLIENT ACCESS AND MICROSOFT WINDOWS 2000
** Last updated on April 5, 2002 **
NOTE: The latest modifications are marked with a "*" in the
This Information APAR defines IBM's support for
running Client Access on Microsoft Windows 2000
These two clients are covered in this info APAR:
- Client Access Express for Windows
- Client Access for Windows 95/NT
Client Access for Windows 95/NT (5763-XD1)
There are no plans to support the Windows 95/NT client on
Windows 2000 workstations or servers.
Client Access Express for Windows (5722-XE1 and 5769-XE1)
Client Access Express V5R1M0, V4R5M0, and V4R4M0 are
supported with all released version of Windows 2000.
(The V4R4M0 Express client requires service pack SF60698 or
For information on how to acquire the latest Client Access
service pack, see this web page:
For information on AS/400 Operations Console, the Operations
Console Setup document has been updated with Windows 2000
information. Go to the following web page and take the first
link for updated Operations Console documentation:
Known Client Access Express Problems on Windows 2000
The install process will freeze if you select to install
one of the Secure Socket Layer (SSL) components in Client
Access Express for Windows V4R4M0. To verify that your
install is in a frozen state, please wait at least 10
If you want to selectively install an SSL component, you must
first install Client Access Express service pack SF58121 or
later your PC.
If you want to install an SSL component during the initial
install, you will need to obtain and install Client Access
Express PTF SF59005 for product 5769-XE1 on the AS/400 that
you will be installing from. SF59005 updates the install
image on the AS/400. It does not get installed on
If you still encounter problems after these PTFs are
applied, you may be able to circumvent the problem by
adding an entry into the SSL's SETUP.INI file. You must
be extremely careful about editing this file. Do not
remove, add or modify anything else.
a. Find the SSL's SETUP.INI file. This is located in
the following directories on your AS/400 depending
on which SSL component you are installing.
- Client Encryption: 128-bit
- Client Encryption: 56-bit
- Client Encryption: 40-bit
b. Add the following into the SETUP.INI file under the
CmdLine=ClientAccess us_EN -s
When making connections to the AS/400 using SSL, it may take
several minutes before the connection is established. Once
established, performance of the connection is fine.
There is a workaround for this problem that involves changing
the following DWORD registry value:
NOTE: This registry entry spans two lines!
\Disable Performance Counters=1
This key defaults to 0 if it is not specified.
Problem 3 - fixed in base V5R1 and V4R5, and in V4R4
service pack SF59557 or later:
Client Access Express desktop icons cause an error with
Explorer.exe when selected or an option is selected from
the icon's context menu. The properties of the icon
cannot be viewed but the application associated with the
icon (e.g., Operations Navigator, PC5250) does execute.
If you have problems with AS/400 Operations Console, go to
the following web page and take the first link for the setup
Problem 5: FIXED IN SERVICE PACKS LISTED BELOW
The AFP and SCS printer drivers trap (you get a
blue screen) when you attempt to install them on
A fix for the SCS printer driver is available in the
following Client Access Express service packs:
For V4R4M0 - SF63638 or later
For V4R5M0 - SF62213 or later
* For V5R1M0 - fixed in the base
* A fix for the AFP printer driver is in the following
* Client Access Express service packs:
* For V4R4M0 - SF64474 or later
* For V4R5M0 - SF64217 or later
* For V5R1M0 - fixed in the base
Problem 6 - fixed in base V5R1 and V4R5, and in V4R4
service pack SF59557 or later:
The Microsoft Windows 2000 operating system includes a new
version of ADO, version 2.5, which is used by the Client
Access Express OLE DB provider. When using this version
of ADO with the Client Access Express OLE DB provider,
attempting to set any properties of a Connection object
before calling the Connection.Open method may cause
the following error:
"Multiple-step operation generated errors. Check each status
value. No work was done."
If you re-install Client Access Express on Windows 2000, you
may see an informational message "Client Access Express could
not install Remote Command Service. Call your next level of
support". Please ignore the message by clicking "OK" and the
installation process will continue successfully.
Do not use silent installation to re-install Client Access
Express on Windows 2000 if the Incoming Remote Command
component has been installed by the original installation.
The silent installation will fail. If you uninstall Client
Access Express before re-installing it, you should not see
Problem 8: (Fixed in service packs listed below)
Windows 2000 Restricted User class profiles cannot start a
PC5250 session if Windows 2000 and Client Access Express are
installed on an NTFS partition. For further information,
see APAR SA88797.
A fix for this problem is in the following service packs:
For V4R4M0 Express, SF65706 or later
For V4R5M0 Express, SF66513 or later
For V5R1M0 Express, fixed in the base
To see a history of service packs for each release and to
download the latest one, refer to:
If Client Access is already installed on a Windows 95,
98 or NT 4.0 PC, an upgrade of the operating system
to Windows 2000 is not supported. Client Access must
be uninstalled, and then reinstalled after Windows 2000
installation is complete.
The one exception to this is if you are upgrading from
Windows NT 4.0 and the PC5250 and SSL components are
not installed. Upgrade to Windows 2000 should work okay
then. If these two components are installed, uninstalling
them and reinstalling after the upgrade should also work.
When Restricted Users try to access the AS/400 through Secure
Sockets Layer (SSL), they might receive an error message
(CWBCO1034 RC=20002). This usually means that the restricted
user does not have read/write authority to the pc SSL key
database. By default the pc SSL key database is cwbssldf.kdb
and is located in the Express install directory.
There are at least two ways to avoid this restricted user
-Change the location of the pc SSL key database using
the Express control panel and create a new pc SSL key
database in that location using IBM KeyMan or copy the
default one, cwbssldf.kdb and cwbssldf.sth to that
location. The location should be open to read/write for
the restricted users/groups.
-Use Windows Explorer to change the security properties of
cwbssldf.kdb and cwbssldf.kdb to be read/write for the
Windows 2000 Support for Functions Associated with Client
- For AS/400 NetServer support, see Information APAR II11938
* - Regarding the Express TCP/IP software for twinax cards,
* refer to the following web site for the latest 5250
* Hardware Support Package.
* Here is a note about Windows 2000 from that web site:
* "Windows 2000 Users: Your only option at present is TCPIP
* over Twinax. This package will detect your Windows 2000
* installation and install only the TCPIP over Twinax driver.
* You also get the Native Diagnostics and Twinax Config v3
* during this installation. "
Migrating from Client Access for Windows 95/NT (5763-XD1)
to Client Access Express (5769-XE1)
The recommended approach for upgrading both the Client Access
product and upgrading to Windows 2000 is the following:
1) Migrate to Client Access Express (5769-XE1). This will
2) Upgrade to Windows 2000.
If you did not follow this recommendation, you will still be
able to install Client Access Express successfully: Client
Access Express contains a function to migrate from Client
Access for Windows 95/NT (5763-XD1), however you could
experience the following problem when the PC automatically
The migration function takes several steps. One of these
steps is to automatically uninstall Client Access for Windows
95/NT (5763-XD1) and then reboot. Since there are
outstanding daemons in Client Access for Windows 95/NT, you
could encounter a hang problem during this reboot.
To recover from this problem, manually power off the PC and
power it back on.