Access Ibm Error Message
Contents |
Technote (troubleshooting) Problem(Abstract) CWBUNPLA error message when starting a connection with IBM Access for Windows. Resolving the problem Message CWBUNPLA is received when starting an
"an Odbc Error -1 Has Occurred"
IBM Access for Windows connection, such as with a PC5250 session. This message can be caused by several different issues: 1. On an IBM OS/400 command line, type the following: WRKREGINF Press the Enter key. Select Option 8, Work with exit programs, next to the following exit points: QIBM_QZRC_RMT QIBM_QZSC_LM, QIBM_QZSC_NLS, QIBM_QZSC_SM, QIBM_QZSO_SIGNONSRV If you do have an exit program registered to the exit point(s), ensure https://www.ibm.com/support/knowledgecenter/ssw_i5_54/rzatv/rzatvodbcerr.htm the user profile has the correct authority to the exit program, contact the OEM vendor of the exit program, or remove the exit program from the exit point. If removing the exit program resolves the problem and the exit program must be used, contact the OEM software vendor for the exit program. 2. When connecting using PC5250 emulation, underneath the covers it is using AppAdmin http://www.ibm.com/support/docview.wss?uid=nas8N1019482 to query the OS/400 for the user settings of the user profile you use to connect to IBM i OS. AppAdmin uses the remote command to query IBM i OS. Make sure the AS-RMTCMD daemon job is up and in a listen state by doing a NETSTAT *CNN command. You should see AS-RMTCMD in listen state on port(s) 8475 and 9475 depending if you are using SSL. For a complete list of Client Access TCP/IP ports see document N1019667, TCP/IP Ports Required for Access for Windows and Related Functions. If the PC is remote to the IBM i OS System and is going through a firewall and/or routers, you should ensure that the 8475 and/or the 9475 port is open. Cross reference information Segment Product Component Platform Version Edition Operating System IBM i 6.1 Operating System IBM i 7.1 Historical Number 22773543 Document information More support for: IBM i Access for Windows Software version: 5.4.0, 6.1, 6.1.0, 7.1, 7.1.0 Operating system(s): IBM i Reference #: N1019482 Modified date: 2013-04-09 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
page explains why the access request failed. WebSEAL provides a number of https://publib.boulder.ibm.com/tividd/td/ITAME/SC32-1359-00/en_US/HTML/am51_webseal_guide37.htm default message pages. You can modify the contents of these pages. https://publib.boulder.ibm.com/iseries/v5r1/ic2924/info/rzaii/rzaiiodbc23.HTM You can also create you own error message pages, based on error codes returned by WebSEAL. This section contains the following topics: Default error message pages Modifying existing HTTP error pages Creating new HTTP error pages Enabling the time of day error page Specifying error error message page location Backwards compatibility Default error message pages The error messages pages are installed when the WebSEAL server instance is configured. Each error message page is a separate HTML file. The names of the files are the hexadecimal values of the returned error codes. Do not modify these file names. The location of the error files access ibm error is configurable. See Specifying error page location. The names of the error message files are listed in the following table. Filename Title Description HTTP Error Code 132120c8.html Authentication Failed Credentials could not be retrieved for the client certificate used. Possible reasons include: the user supplied an incorrect certificate the certificate has been revoked the user's credentials are missing from the authentication database 38ad52fa.html Non-Empty Directory The requested operation requires the removal of a non-empty directory. This is an illegal operation. 38cf013d.html Request Caching Failed The request-max-cache or request-body-max-read values have been exceeded. 38cf0259.html Could Not Sign User On The resource requested requires the WebSEAL server to sign user on to another Web server. However, a problem occurred while WebSEAL was attempting to retrieve the information. 38cf025a.html User Has No Single Sign-on Information WebSEAL could not locate the GSO user for the requested resource. 38cf025b.html No Single Sign-on Target for User WebSEAL could not locate the GSO target for the requested resource. 38cf025c.html Multiple Sign-on Targets
from errors that are returned by the DBMS. For errors that occur in the data source, the Client Access ODBC Driver maps the returned native error to the appropriate SQLSTATE. When both the Client Access ODBC Driver and the Microsoft Driver Manager detect an error, they generate the appropriate SQLSTATE. The Client Access Express ODBC Driver returns an error message based on the message returned by the DBMS. For errors that occur in the Client Access Express ODBC Driver or the Microsoft Driver Manager, the Client Access ODBC Driver returns an error message based on the text associated with the SQLSTATE. Error message format Error messages have the following format: [vendor][ODBC-component][data-source] error-message The prefixes in brackets ([]) identify the source of the error. The following table shows the values of these prefixes returned by the Client Access ODBC Driver. When the error occurs in the data source, the [vendor] and [ODBC-component] prefixes identify the vendor and name of the ODBC component that received the error from the data source. Error Source Value Driver Manager [Microsoft] [ODBC Driver Manager] [N/A] Client Access Express ODBC Driver (32-bit) [IBM] [Client Access Express ODBC Driver (32-bit)] N/A NLS messages [IBM] [Client Access Express ODBC Driver (32-bit)] Column #: NLS error message number NLS error message text Communication [IBM] [Client Access Express ODBC Driver (32-bit)] Communications link failure. Comm RC=xxxx - (message text) where xxxx is the error number in decimal, not hexadecimal, format. Message text describing the nature of your error appears with the error number. iSeries DBMS [IBM] [Client Access Express ODBC Driver (32-bit)] [DB2 UDB for iSeries] Host message Viewing OS/400 DBMS error message text: For errors that begin with: Use this OS/400 command SQL DSPMSGD RANGE(SQLxxxx) MSGF(QSQLMSG) IWS or PWS DSPMSGD RANGE(ZZZxxxx) MSGF(QIWS/QIWSMSG) where ZZZ is IWS or PWS You can search and view NLS or communication error messages in the express Online Users' Guide, in the Service, Error and Trace message help topic. Refer to Common ODBC errors for help with other ODBC error messages.