While you are connecting a local console to a server, you
might encounter local console connection problems.
The errors consist of software configuration problems or unrecognizable
service tool user IDs.
- Verify that you are entering a valid service tools user ID and
password during the configuration wizard. For example, you just performed
a scratch installation and the console is not coming up after the
code was restored. The PC being used has a user-created service tools
device ID. In this case, the only valid service tools device ID is QCONSOLE since
all of the user-created service tools device IDs were removed or reset
as part of the initialization of the load source hard disk drive.
You must delete and then recreate a connection using QCONSOLE as
the service tools device ID.
- Verify that your server and Operations Console are installed with
the same version of IBM® i and System i® Access for Windows®, respectively.
If you are running different versions and are creating a new service
tools device ID, the password becomes the name of the service tools
device ID in uppercase, just as if the device ID were to be reset.
For example, if the client is running IBM i V5R4 and the server
is running i5/OS V5R3 and you are creating a new service tools device
ID for a new PC to connect, the PC asks for a password for the device
ID. You might name the device "system1", for example. When you
create this on the PC, you are prompted for a password. You must use "SYSTEM1" because the system cannot assign a different password for this name.
The V5R4 code, at either end, cannot assign a password since the password
is automatically made the same as the name in uppercase.
You might also receive an error message regarding a secure connection.
For information about this error, see Error message: Connection to
system is not secure.
Subscribe to this information