Troubleshooting
Problem
This document describes a problem where IBM Access for Windows PC5250 or IBM i Access Client Solutions 5250 connection fails with an error message e8925.
Resolving The Problem
This document describes a problem where IBM Access for Windows PC5250 or IBM i Access Client Solutions 5250 connection fails with an error message e8925.
There are times when error message E8925 - Creation of device failed is the result when trying to configure a new 5250 session, using a named device. Using no workstation name, and defaulting to QPADEVxxxx, the session is created successfully.
From the IBM i, the following troubleshooting steps can be used to identify the problem:
- WRKJOB QTVDEVICE
- Select each of the ACTIVE jobs, one at a time
- Display the joblog
- Look for messages directly related to the device name in question
The following messages are likely to be found:
Message ID . . . . . . . . . : CPD0043
Message file . . . . . . . . : QCPFMSG
Library . . . . . . . . . : QSYS
Message . . . . : Keyword IGCFEAT not valid for this command.
Cause . . . . . : A keyword was specified on a command that has no
corresponding parameter.
Recovery . . . : Correct or omit the keyword, and then try the command
again.
Message ID . . . . . . . . . : CPDA4A8
Message file . . . . . . . . : QCPFMSG
Library . . . . . . . . . : QSYS
Message . . . . : CRTDEVDSP command failed. See previous messages.
Cause . . . . . : The following command string was issued and failed: &2
Recovery . . . : See previous messages for the error. Fix the error and
try the command again.
Technical description . . . . . . . . : This command was issued from within
another command. The information given here is to give the command string
that was issued for problem determination.
This message indicates they have a custom CRTDEVDSP command that is not compatible with the system CRTDEVDSP command
Performing a WRKOBJ OBJ(*LIBL/CRTDEVDSP) OBJTYPE(*CMD) indicated another CRTDEVDSP command.
In this scenario, the CRTDEVDSP command was a custom object in a library ahead of QSYS. Using the IBM-supplied command resolved the issue.
Historical Number
597750278
Was this topic helpful?
Document Information
Modified date:
18 December 2019
UID
nas8N1011564