When you add a NS/Router connection and start the Client Access Connections GUI, the mode information associated with that NS/Router is damaged. You can view the mode information by selecting the Advanced Properties button from the Common tab of the router properties. The corruption of mode information causes two problems:
v Deletion of Mode QPOPSRVR. This prevents you from logging on to the POP mail server over NS/Router connections.
v The damaged Session Limit value for mode QSERVER causes problems when viewing the Simple Mail Transfer Protocol (SMTP) properties via the AS/400
Operations Navigator. The result is COMM RC=0x17. Select Network, then Servers, then TCP/IP to view the property value.
Installing SF46891 on V3R1M3 prior to the upgrade, or installing any service pack for V3R2M0 after the upgrade, corrects these problems.
Note: Do not export your workstation information before you install one of these service packs and then import the workspace information.
v Your workspace information is corrupt. To correct this, do one of the following:
– Re-install the service pack
– Import SPMODE.REG from the Client Access directory.
You can upgrade from a previous release to a new release of Client Access for Windows 95/NT by using one of the following methods:
v IBM AS/400 Support for Windows Network Neighborhood (AS/400 NetServer (See
“Appendix A. IBM AS/400 Support for Windows Network Neighborhood (AS/400 NetServer) Information” on page 407 for more information.))
v The new release compact disc (CD-ROM) v A network drive
v The new release diskettes (See “Creating Client Access Installation and Service Pack diskettes” on page 189 for more information.)
v A peer server
Client Access Login Service Check checks for a new service pack on the managing AS/400 system and checks to see if there is a new release of Client Access. If a new release exists, Client Access Login Service asks if you want to upgrade. When you choose to upgrade, Client Access does an install of the newer release.
Note: If your install media does not contain a component that is currently installed on your system, the component is uninstalled from the PC.
During the upgrade:
v You cannot add or remove components. All components that are currently installed on your system are upgraded.
v Components that were selectively installed from the managing AS/400 system, like additional languages or third party plug-ins, are upgraded.
v Your system values (for example configurations, environments, that are managing systems and so forth) remain the same.
v AS/400 Operations Navigator is installed only with the sub-components that correspond to function in the previous release. There are Operations Navigator sub-components that are new in V3R2M0 that are not installed during an upgrade. To install these sub-components, use selective install after you complete the upgrade.
If you want to upgrade and have a service pack to install, do the following:
__ 1. Upgrade your PC.
__ 2. Restart your PC.
__ 3. Install the service pack.
__ 4. Restart your PC.
If the upgrade fails, do the following:
v Map a drive to the directory where the install image exists.
v Run setup UPGRADE=YES.
You can also copy the install image to another directory and run the above command.
Chapter 22. Migrating or Upgrading from a Previous Client Access Release 167
Chapter 23. Installing and Migrating Client Access on Your PC
Installation Notes and Restrictions:
1. If you delete Client Access for Windows 95/NT without uninstalling it correctly, follow these steps to get Client Access functioning again.
Client Access Version/Release/Mod Level Recovery Steps
V3R1M1 a. Run the setup.exe command exactly as
follows (make sure that it is in all uppercase and has no spaces except between EXE and UPGRADE):
SETUP.EXE UPGRADE=YES
b. Reinstall the service pack if you are not going to uninstall Client Access.
V3R1M2 a. Run the setup.exe command exactly as
follows (make sure that it is in all uppercase and has no spaces except between EXE and UPGRADE):
SETUP.EXE UPGRADE=YES
b. Reinstall the service pack if you are not going to uninstall Client Access.
V3R1M3 a. Run the setup.exe command.
SETUP.EXE
b. Reinstall the service pack if you are not going to uninstall Client Access.
2. Client Access does not install on hard disks that have been compressed using the Stacker program.
3. Do NOT cancel out of the setup program unless you really mean to cancel and go no further. If you cancel from the confirmation screen, you get an error.
4. When you copy the install image to a server, use a directory name that is 8 characters or less. You should not do a To Server install into a directory that uses the X.X format or long file names.
5. Only one Client Access install is required to set up the workstation for all the users that are defined to that workstation.
6. You have to install Client Access twice if you have a dual system with both Windows 95 and Windows NT. You cannot use the client if it is not installed on the operating system that is currently running.
7. Windows NT
v To install Client Access on the Windows NT system, you must have Administrator privileges.
v If you install Client Access on a Windows NT PC and do not see the Client Access icon on the desktop, run CWBICONS and restart your computer.
– Click on Start and go to Run.
– Type in the drive, folder (where you installed Client Access) then cwbicons.
© Copyright IBM Corp. 1995, 1998 169
d:\ibm\cwbicons – Click OK.
You see the icon after you restart.
8. Although Client Access can be installed without a license, you must have a license to be able to use the functions that require a license. See “License Information” on page 9 for more information.
9. If you have the McAfee WebScan V2.0.0 product installed on your Windows 95 PC, you may receive an error message similar to the following when you try to use Client Access/400 functions:
Error Starting Program
A required .DLL file, ADDCONN.DLL, was not found.
The WebScan software changes Windows 95 default behavior when it opens executable files. To avoid this problem, add the Client Access Shared directory to your PATH statement in your AUTOEXEC.BAT file. Remember that you should use the directory-short names. For example:
SET PATH=%PATH%;c:\PROGR˜1\IBM\CLIENT˜1\SHARED
where c is the drive where you installed Client Access.
DO NOT copy the files from the Client Access\Shared directory to your WINDOWS\SYSTEM directory. Client Access fails when upgrading to a new release or service pack level. If you have copied the Client Access DLL files to your WINDOWS\SYSTEM directory, make sure that you erase them from your
WINDOWS\SYSTEM directory.
In preliminary testing, the latest version of McAfee’s WebscanX does not appear to cause these problems.