psconfig Internal Error Messages
The messages detailed in this section are those that are displayed on the
terminal while psconfig is being accessed.
Table F-1. psconfig Internal Error Messages
------------------------------------------------------------------------------------
| | |
| Error | Message/Meaning/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| 100 | Error accessing the OPSDB |
| | |
| | * Meaning: This is the general error condition message that is |
| | displayed on the terminal when an error occurs while |
| | attempting to access the OPSDB. A more specific message is |
| | written to PSUILOGD. |
| | |
| | * Action: Contact the HP Response Center. This is an error |
| | condition that may involve IMAGE, and should be examined by a |
| | HP Response Center Engineer (RCE). The RCE may request access |
| | to PSUILOGD information for troubleshooting purposes. |
| | |
------------------------------------------------------------------------------------
| | |
| 200 | Error accessing the psconfig Message Catalog |
| | |
| | * Meaning: This message indicates that an error occurred while |
| | attempting to read the message catalog or perform some other |
| | activity involving the message catalog. A more specific |
| | message is also written to PSUILOGD. |
| | |
| | * Action: Contact the HP Response Center. This is an error |
| | condition that may involve IMAGE and the OPSDB. The RCE may |
| | request access to PSUILOGD information for troubleshooting |
| | purposes. |
| | |
| | NOTE: The following items apply to psconfig internal error messages. |
| | |
| | |
| | * An even-numbered message (for example: 100, 200) appears on |
| | the screen. |
| | |
| | * An odd-numbered message (for example: 101, 201) with details |
| | about the specific error condition appears in PSUILOGD, the |
| | psconfig error log. |
| | |
| | * The 600-series messages are printed only to the screen without |
| | a message number. |
| | |
------------------------------------------------------------------------------------
| | |
| 300 | Unable to make the CE comment file. |
| | |
| | * Meaning: This message indicates that an error occurred while |
| | opening, writing to, or closing PSCEFILE, the CE comment file. |
| | The comment was probably not saved. A more specific message |
| | is written to PSUILOGD. |
| | |
| | * Action: Go to the detailed error information in PSUILOGD, the |
| | psconfig run log. One of the following three error messages |
| | will appear with message 300. |
| | |
| | 301 Unable to open the CE comment file. |
| | 302 Unable to write to the CE comment file. |
| | 303 Unable to close the CE comment file. |
| | |
| | |
------------------------------------------------------------------------------------
Table F-1. psconfig Internal Error Messages (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Meaning/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| 300 Cont | |
| | Determine why there were problems making PSCEFILE.PRED.SYS. |
| | Some possibilities are: |
| | |
| | * The file was being accessed. In this case, try saving |
| | the file again. |
| | |
| | * The file is being used for something other than its |
| | intended use. For example, a file by the name of |
| | PSCEFILE has been created by some other source. In |
| | this case, purge the file and try the "Send Comment" |
| | function again. |
| | |
| | If problems persist, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| 400 | Internal psconfig error - unexpected condition |
| | |
| | * Meaning: This message indicates that there is a mismatch |
| | between a selected item and the psconfig software. There may |
| | be a problem with the psconfig software. A more specific |
| | message is written to PSUILOGD. |
| | |
| | * Action: Contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| 500 | Internal psconfig error - IPC error |
| | |
| | * Meaning: This message indicates that psconfig received an |
| | unexpected IPC error communicating with the Predictive monitor |
| | (PSMON) or setting up for communication with PSMON. A more |
| | specific message is written to PSUILOGD. |
| | |
| | * Action: Contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| 600 | Error ! opening the psconfig log. Source error # ! |
| | |
| | |
| | * Meaning: This usually indicates that psconfig was competing |
| | for files with a STORE. This message prints only to the |
| | screen. |
| | |
| | * Action: |
| | * Run psconfig at a later time when it does not have to |
| | compete with a STORE. |
| | * If problems persist, contact the HP Response Center. |
| | |
| | |
------------------------------------------------------------------------------------
| | |
| 602 | psconfig message catalog missing. File name is !. |
| | |
| | |
| | * Meaning: psconfig could not find the specified message |
| | catalog. This message prints only to the screen. |
| | |
| | * Action: |
| | * Locate the catalog on either the product installation |
| | tape or a backup tape. |
| | * Replace the specified file. |
| | * If messages persist, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| 603 | Error opening psconfig message catalog (<filename>). Error # = ! |
| | |
| | |
| | * Meaning: psconfig could not open the specified message |
| | catalog. The error number displayed is an FSERR. This message |
| | prints only to the screen. |
| | |
| | * Action: |
| | * Take the necessary steps to fix the FSERR. |
| | * Replace the file, if necessary. |
| | |
| | Contact the HP Response Center for additional assistance, if |
| | required. |
| | |
------------------------------------------------------------------------------------
Table F-1. psconfig Internal Error Messages (cont.)
------------------------------------------------------------------------------------
| | |
| Error | Message/Meaning/Action |
| Number | |
| | |
------------------------------------------------------------------------------------
| | |
| 604 | PSUI log open failed. Error # = ! Source error = ! |
| | |
| | |
| | * Meaning: psconfig was probably competing for files with a |
| | store. This message prints only to the screen. |
| | |
| | * Action: |
| | |
| | * Run psconfig at a later time when it does not have to |
| | compete with a STORE. |
| | |
| | If problems persist, contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| 700 | Error attempting to read Transfer disable options from OPSDB |
| | Press RETURN when ready to return to Main menu |
| | |
| | * Meaning: This message indicates that an error occurred while |
| | reading one of the values in the OPSDB that is used for the |
| | transfer disable options. A more specific message is written |
| | to PSUILOGD. |
| | |
| | * Action: Contact the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| 800 | Error obtaining sizes of Transfer files Press RETURN when ready to |
| | return to Main menu |
| | |
| | * Meaning: This message indicates that an error occurred while |
| | checking for something to upload under a "Transfer Normal" |
| | file transfer action. It will appear in PSUILOGD with the |
| | following error: |
| | |
| | (801) Sherlock error ! obtaining size of ! |
| | |
| | |
| | Possible values for the Sherlock error are: |
| | |
| | 201 Currently accessed. The file is already open (probably opened |
| | by a Predictive run). Try again later |
| | 203 Invalid file reference. This is an internal psconfig problem. |
| | 204 Invalid record size. (Should not occur.) |
| | 205 Nonexistent file. (Should be looked into.) |
| | 207 Security violation. The user is not logged onto PRED.SYS. (This |
| | should not matter since these files are only being read.) |
| | 214 Invalid access mode. This is an internal psconfig problem. |
| | 219 Invalid file type. This is an internal psconfig problem. |
| | |
| | |
| | * Action: Make sure you are logged into the SYS account. Try |
| | again later. If transfer normal still does not work, contact |
| | the HP Response Center. |
| | |
------------------------------------------------------------------------------------
| | |
| 900 | A Code Word Request file cannot be built at this time. |
| | |
| | |
| | * Meaning: This message indicates that a "Transfer Request" |
| | (file transfer that requests a code word from the HP Response |
| | Center) has failed because the request file cannot be |
| | generated. The following message appears with message 900 in |
| | PSUILOGD: |
| | |
| | (901) Error ! attempting to build the Code word Request file. |
| | |
| | |
| | (See message 800 for possible error numbers.) |
| | |
| | * Action: Make sure you are logged into the SYS account. Try |
| | again later. If transfer normal will not work, contact the HP |
| | Response Center. |
| | |
------------------------------------------------------------------------------------