| Support Home | Sales Website | Technology | Contact Us |
|
| RDP Support |
|
|||
| RDPWin KB | Booking Engine - IRM.Net | RDPWin4 & PCI Compliance | Search | |
PBAdmin Errors
Added 09/05/02
Article ID#: KIN0032
ProtoBase Response Messages
Protobase issues the following messages when processing a credit card through RDP:
| Error# | Description | Error | Description |
|---|---|---|---|
| 0000 | COMPLETE | This transaction is successful. | None necessary. |
| 0001 | BAD DEVICE | ProtoBase has been configured to use a malfunctioning or nonexistent device. | Make sure a valid device is configured (modem or line). Make sure the configured device works. |
| 0002 |
COMM DIRECTOR NOT RUNNING | Pbdirect, the communications director process, is not running | Ensure the Pbdirect is running and the pbd.LCK is present when Pbdirect is running. |
| 0003 | COMMUNICATIONS ERROR | ProtoBase was unable to complete the transaction due to an interruption in communications. | Retry the transaction. If continued failure, check phone and modem connections. Run the transaction again and watch the modem for proper operation. Check baud rate. Most third-party transaction processors communicate at 1200 baud. |
| 0004 | COMMUNICATIONS FAILURE | A fatal communications error has occurred. Similar to error #0003, but usually indicates a failure in the modem. | Retry the transaction. If continued failure, check phone and modem connections. Test modem with another communication software package. If these are OK, report problem to help desk. |
|
0005 | ERROR INITIALIZING PORT | Could not initialize port. | Check and repair malfunctioning communications port. Make sure configured port actually exists. Make sure that the device name matches that specified in the pbconfig.cfg file. |
|
0006 | MODEM DIAL ERROR | ProtoBase is unable to dial the modem. | Repair malfunctioning modem. Make sure a phone or data line is connected. Make sure correct Dial String, such as ATDT, is in the Device Configuration entry in the Configuration file, pbconfig.cfg. |
|
0007 | MODEM RESPONSE ERROR | Modem is not responding correctly. | Check and repair broken modem. Be sure modem is turned on and attached to correct port. Ensure that the Init string is defined properly in the Configuration file. Make sure that the max baud rate is larger or equal to the modem speed in the configuration file. |
|
0008 | NO ANSWER FROM HOST | Host did not answer. | Check phone number in the Processor Configuration entry in the Configuration file, pbconfig.cfg. Try transaction again. |
|
0009 | NO DIAL TONE | No dial tone. | Check and, if necessary, connect phone line to modem. If necessary, have phone line repaired. Be sure line is not in use. |
| 0010 | NO ENQ FROM HOST | Host did not send ENQ. A transaction or deposit was attempted and ProtoBase was unable to receive the initial character sent from the host computer. | Verify the phone number and baud rate are valid. |
| 0011 | NO HOST CONNECTION | No response from host on initial connection attempt. | Try again. Network connection not established. Check phone number and baud rate. |
| 0012 | NO PHONE NUMBER | No phone number in the Processor Configuration entry in the Configuration file, pbconfig.cfg. | Check Processor Configuration, and enter a valid phone number. |
| 0013 | NO RESPONSE FROM HOST | Host did not respond to transaction. | Try transaction again. |
| 0014 | NO RESPONSE FROM MODEM | Modem is not responding. | Check and repair malfunctioning modem. Verify the modem is turned on and attached to the correct port. Verify the Init string is defined properly in PBCONFIG.CFG. Verify the Max Baud Rate is greater than or equal to the modem speed in PBCONFIG.CFG. |
| 0015 | RECEIVE TIME OUT | Host did not respond in time. | Try transaction again. |
| 0016 | TRANSMISSION ERROR | A transmission error occurred. | Try transaction again. |
| 0017 | UNEXPECTED DISCONNECT | The telephone line disconnected before the transaction completed. | Try transaction again. Make sure Call Waiting feature is disabled. |
| 0018 | UNKNOWN PROCESSOR | SofTrans module for selected processor not present. | Check Define Terminal Section of Config File to be sure that proper processor is defined. Contact Help Desk to purchase appropriate SofTrans module, or select another processor. |
| 0019 | UNKNOWN PROTOCOL | PBCOM.DAT is missing a communications protocol definition or the file is corrupt. | Contact help desk. |
| 0020 | UNKNOWN DEVICE | ProtoBase has been configured to use a malfunctioning or nonexistent device. | Make sure a valid device (modem or line) is configured. Make sure the configured device works. |
| 0022 | BATCH FILE IS EMPTY | The user attempted to run a report or deposit with no current credit card transactions in the current batch file. The batch file must contain transactions to run a report or settlement from it. | Continue processing as usual. |
| 0023 | CANNOT CREATE HISTORY FILE | Unable to create batch History file. | Ensure that disk is not full and that permissions are set correctly. |
| 0024 | DEVICE FILE ERROR | Error in the Device Configuration entry of the Configuration file, pbconfig.cfg. | Usually caused by a scrambled file. Edit and repair the file. Run pbconfig.exe. |
| 0025 | INVALID TRANSACTION FILE | Bad or nonexistent input file. | Repair file; ensure that it is in the current working directory. Be sure path of input file points to the ProtoBase directory. |
| 0026 | PROCESSOR FILE ERROR | The Processor Configuration entry of the Configuration file, pbconfig.cfg, is missing, corrupt or contains an error. | Recreate the Processor Configuration entry in the Configuration file, pbconfig.cfg and run pbconfig.exe. If error persists, call Help Desk. |
| 0027 | PROTOCOL FILE ERROR | Pbcom.dat, the protocol file, is missing, corrupt, or contains and error. | Call Help Desk. |
| 0028 | UNABLE TO ACCESS BATCH FILE | Either no pbbatch.dat file exists, or the path to the file is incorrect. May be caused intermittently by transactions being recorded at the same time. | Check permissions. Supply correct path. Verify upload criteria. Delete any pbbatch.LCK files. |
| 0029 | UNABLE TO CREATE FILE | Cannot create any file. | Check permissions; make room on disk. |
| 0031 | UNABLE TO OPEN MERCHANT FILE | Cannot open pbmerc.dat, the merchant data file. | Make sure the live merchant file has been installed. Check permissions, supply correct path. |
| 0032 | UNABLE TO OPEN OUTPUT FILE | Cannot open output file, the data file to which the results of each transaction are written. | Check permissions, make room on disk. |
| 0035 | UNABLE TO OPEN TERMINAL FIELD #0109 | Could not open TTTTTTTT.trm, the Terminal file. | Enter a valid value for field #109, Terminal ID as defined in pbconfig. Supply a valid correct entry for field #105, Data Files Path. Create a valid TTTTTTTT.trm terminal file. Note: The pbconfig.exe file entries are case sensitive. |
| 0036 | UNABLE TO OPEN TRANS FILE | Bad or nonexistent input file. | Repair file; ensure that it is in the current working directory. |
| 0037 | UNABLE TO READ FROM FILE | Corrupted disk. | Repair disk or reinstall ProtoBase. |
| 0038 | UNABLE TO WRITE TO FILE | Corrupted disk or permissions not set correctly. | Verify permissions; repair disk or reinstall ProtoBase. |
| 0039 | UNABLE TO OPEN DEVICE FILE | Cannot open pbdev.dat, Device Configuration data file. | Be sure file is in ProtoBase files directory. Check permissions. Run pbconfig and retry trans. |
| 0040 | UNABLE TO OPEN REPORT FILE | Cannot open file supplied in field #107, Report File. | Supply correct path and file name. |
| 0041 | INVALID ACCOUNT NUMBER FIELD #0003 | Account number data is invalid. If the data was manually input, the account number may have been miskeyed. | Re-swipe or reenter the card data. If error occurs again, manually enter the account number and expiration date. If the error condition continues, ask the customer for another credit card or type of payment. |
| 0042 | INVALID ADJUSTMENT AMOUNT | The amount entered or passed from the POS product is invalid. | Re-enter the amount in the format 9999.99. |
| 0043 | INVALID AMOUNT | The transaction amount (field 2) entered or passed from the POS product is invalid. | Re-enter the amount in the format 9999.99. |
| 0045 | INVALID BATCH DEPOSIT LEVEL | Batch Deposit Level is not 1, 2, 3, or 4. | Check Configuration file for value of Batch Deposit Level field, Value must be 1 - all, 2 - deposit, for merchant number specified, 3 - deposit for cashier ID specified, or 4 - Deposit for terminal ID specified. |
| 0046 | INVALID CARD INFORMATION FIELD #0003 | Account number data is invalid. If the credit card was input via a card reader, the magnetic stripe on the credit card may be damaged or the credit card may be fraudulent. | Re-swipe or re-enter the credit card. If error occurs again, manually enter the account number and expiration date. If the error conditions continues, ask the customer for another credit card or type of payment. |
| 0047 | INVALID CARD TYPE | The credit card being used for payment is not listed in the Card Type section of PBCONFIG.CFG for this terminal, or the BIN does not match any defined ranges in the CardType section. If the credit card was manually entered, the account number may have been typed incorrectly. | Try the transaction again. If error condition recurs, ask customer for another credit card or form of payment. Call Help Desk for assistance in customizing the Card Type entry in the Configuration file to include this type of credit card. Check the Processor configuration entry and Terminal Configuration entry to add the card type information and save the file. Acceptance of this card type must be input into the merchant's file on the third-party transaction processor computer as well. |
| 0048 | INVALID DATE ENTERED | Date entered is invalid. | Enter a valid date in format MMDDYY. |
| 0049 | INVALID EXPIRATION DATE FIELD #0004 | Date entered is invalid. | Enter a valid date in format MMYY. Ensure that no spaces exist in card account number. |
| 0050 | PIPE OPEN FAILURE | Indicates a system level failure. The system could not open the Interprocess Communication (IPC) link between the various elements of the ProtoBase system. | Check system permissions and system resources. |
| 0051 | INVALID INDUSTRY CODE ENTERED | Critical system error. Industry code read is not valid. | Call Help Desk. |
| 0053 | INVALID MAG STRIPE FIELD #0003 | Invalid CRC (cyclical redundancy check) via a card reader. The magnetic stripe on the credit card may be damaged or the credit card may be fraudulent. | Re-swipe or re-enter the credit card. If error occurs again, manually enter the account number and expiration date. If the error condition continues, ask the customer for another credit card or type of payment. |
| 0054 | INVALID REFERENCE NUMBER | The reference number in Field 7 is either less that 1 or greater than 99999999. | Verify and re-enter a valid reference number, or call the Help Desk. |
| 0057 | INVALID TERM ID | Terminal ID in Field 109 is invalid. | Supply a valid terminal ID as defined in "Terminal Configuration Section," or define the terminal in the Terminal Configuration entry in the Configuration file, pbconfig.cfg file. |
| 0058 | INVALID TIME ENTERED | Time entered is invalid. | Enter a valid time in HHMMSS. Verify the system time is correct. Retry the transaction. |
| 0059 | INVALID TRANSACTION CODE | Critical system error. Transaction code in Field 1 is not valid. | Verify integration with POS System. Call Help Desk. |
| 0060 | UNDEFINED VALIDATION ERROR | The response from the host, as interpreted by ProtoBase, did not fit the pattern for an approved or accepted transaction. (this may be a DECLINE, HOLD CARD, CALL CENTER, etc.) | Retry transaction. If error condition recurs, request another form of payment. If this error occurs during testing, check the input data. |
| 0061 | CARD NOT MARKED FOR EDC IN BIN | A transaction type other that Authorization Only is being performed on a card type that has no Depositor set up for it in the Configuration file. | Ask to use another credit card or type of payment. Perform an Authorization Only transaction and then mail receipts to the bank via existing company procedures. Call Help Desk for assistance in customizing the Card Type section to include the desired credit card type. Check the Processor and Terminal sections in PBCONFIG.CFG to add the card type information. The merchant file, PBMERC.DAT, may also need to be edited for the desired card type to be accepted. |
| 0062 | MERCHANT NUMBER NOT IN PBMERC.DAT | PBMERC.DAT contains an invalid or test merchant number, or the Terminal section in PBCONFIG.CFG contains invalid merchant keys. | Edit the merchant keys in PBCONFIG.CFG. If the error continues, contact Help Desk for merchant update. |
| 0063 | PIPE READ FAILURE | Indicates a system level failure. The system could not read the Interprocess Communication (IPC) link previously opened between the various elements of the ProtoBase system. | Check system permissions and system resources. |
| 0064 | PIPE WRITE FAILURE | Indicates a system level failure. The system could not write to the Interprocess Communication (IPC) link previously opened between the various elements of the ProtoBase system | Check system permissions and system resources. |
| 0065 | TRANSACTION NOT FOUND | An invalid reference number in Field 7 was entered during a Void operation. | Edit Field 7 in the input file. Retry the transaction. |
| 0066 | NO DELIMITER IN INPUT LINE | The comma is missing from a line in the input file. Can also be caused by blank line in input file. | Correct the input file. |
| 0067 | MISSING OR INVALID FIELD # | Field #xxxx is missing or invalid in input file. This field is required for the transaction. | Add or supply a valid value for the field number specified. |
| 0068 | INPUT LINE GREATER THAN 256 CHARS | An input line is too long. | Correct the input. |
| 0069 | INCORRECT ACCT LENGTH | Credit card # is incorrect. | Check credit card #. Verify that Card Type entry is pbconfig file is correct. |
| 0071 | NO DEPOSITORS FOUND IN BIN | Could not find a depositor in TTTTTTTT.trm, the terminal file. | Make sure that the depositor is specified for each card type for each terminal in the Configuration file. |
| 0072 | ERROR IN BATCH UPLOAD | There was an error during the settlement process. | Contact your processor and retry the settlement. |
| 0073 | INVALID BATCH DEPOSIT LEVEL | Deposit level in input file is incorrect. |
Enter a valid value in field 111. Valid values are: 1 = All 2 = Deposit for merchant number specified 3 = Deposit for cashier ID specified 4 = Deposit for terminal ID specified. |
| 0074 | NO MATCHING RECORDS IN BATCH | Could not find record to void or modify. | Select a valid record. |
| 0077 | AWK FAILED | Awk failed to execute. Awk is a transaction and reporting system used with UNIX related systems. ProtoBase uses awk for file handling during batch deposits. | Check the path, and make sure the awk executable is not named differently. |
| 0078 | DEPOSIT IN PROGRESS, TRY LATER | Deposit for this merchant in progress. | Retry the transaction after the deposit is complete. |
| 0079 | UNABLE TO LOCK BATCH, TRY LATER | Could not lock Batch file to add transaction. | Try the transaction again later. |
| 0081 | UNABLE TO CHANGE DIRECTORY | Incorrect path given in field 105, 106, 107, or 108. | Supply valid paths for data files, batch file, report file, and history files. Make sure the trailing slash (\) character exists. |
| 0084 | NOT ENOUGH MEMORY | ProtoBase was unable to allocate enough memory to run the requested transaction. | Add memory to the system, or fire up existing memory. Be sure that the Softrans files or Merchant file were compiled on the proper system, intel vs non-intel. |
| 0085 | COMM PROCESS TERMINATED | Pbcom processing ended abnormally. | Run pbkill to shut down pbdirect. Check configuration; retry transaction. If problem persists, call Help Desk. If pbcom is not present, delete UNX* and *.LCK files, kill the pbdirect process and restart pbdirect. |
| 0086 | COMM NOT AVAILABLE | Pbdirect cannot locate pbcom. | Check Configuration file to make sure that the correct devices are configured and the number of requests for each device have not exceeded their limits. Also make sure a device Is available for the desired processor. Stop and restart pbdirect. Check permission of pbcom. |
| 0087 | UNABLE TO OPEN CUHIST.NDX | Could not open history index. | Supply valid path for field #108, History file path, or correct permissions. |
| 0088 | NO RESPONSE FROM COMM DIRECTOR | Pbdirect not running. Pbd.LCK exists and pbdirect appears to be running but is not. | Remove pbd.LCK and UNX*. Kill the pbcom process if necessary and restart pbdirect. |
| 0089 | CANNOT FIND FILE PATH | Batch file cannot be located. | Check file path for input file. Check history or bad files for batch file to be deposited. |
| 0090 | COULD NOT ACCESS FIELD CHK DATA | Wrong version of SofTrans module loaded for this processor. | Call Help Desk. |
| 0091 | NO DEVICES ARE AVAILABLE | Cannot access comport specified. | Check config file for device specified. Ensure that the Max Baud in the device is greater than or equal to the Baud Rate in the processor section. |
| 0092 | UNABLE TO RESTORE VOID TRANSACT | Unable to restore void. | Check reference # to match with voided transaction. |
| 0093 – 0100 | UNDEFINED MISC ERROR (S) | An error has occurred and ProtoBase was unable to define the cause | Try transaction again. If this persists, call Help Desk. |
|
Note: Responses to messages numbered from 101 to 117 are normally status responses for ongoing transactions. Numbers 101, 102, and 103 may be returned if the maximum number of tries have been exceeded in any one transaction. These status messages return during the course of each transaction and may be directed to the terminal device if desired. |
|||
| 0101 | MODEM ERROR | No fix necessary. See note above. | |
| 0102 | MODEM BUSY | No fix necessary. See note prior to message 0101. | |
| 0103 | MODEM NO ANSWER | No fix necessary. See note prior to message 0101. | |
| 0104 | MODEM RINGING | No fix necessary. See note prior to message 0101. | |
| 0105 | DIALING | No fix necessary. See note prior to message 0101. | |
| 0106 | WAITENQ | No fix necessary. See note prior to message 0101. | |
| 0107 | ONLINE | No fix necessary. See note prior to message 0101. | |
| 0108 | TRANSMIT | No fix necessary. See note prior to message 0101. | |
| 0109 | WAITING | No fix necessary. See note prior to message 0101. | |
| 0110 | RECEIVE | No fix necessary. See note prior to message 0101. | |
| 0111 | COMPLETE | No fix necessary. See note prior to message 0101. | |
| 0112 | RESPONSE | No fix necessary. See note prior to message 0101. | |
| 0113 | HEADER | No fix necessary. See note prior to message 0101. | |
| 0114 | PACKET | No fix necessary. See note prior to message 0101. | |
| 0115 | HANGUP | No fix necessary. See note prior to message 0101. | |
| 0116 | INACTIVE | No fix necessary. See note prior to message 0101. | |
| 0117 | ACK | No fix necessary. See note prior to message 0101. | |
|
0118 | NO DIRECT PROCESSOR | A direct processor has been indicated in the Processor Configuration entry in the Configuration file, when no direct line is present. | Add direct line or reconfigure for dial-up processor. |
PBAdmin Setup Errors
The following errors may occur when accessing PBAdmin during the initial installation:
| Error # | Error Message | Reason/Solutions |
|---|---|---|
| -1 | INTERNAL ERROR | For reasons unknown, an error occurred
while attempting to access any of the c-tree databases. Possible
reasons:
|
| -2 | INVALID DATABASE | An invalid database number was given while trying to process a command. Call help desk. |
| -3 | DATABASE ALREADY EXISTS | An attempt was made to create a database that already exists. Call help desk. If you have attempted to delete a database, make sure you remove both the .DAT and .IDX files. |
| -4 | DATABASE DOES NOT EXIST | An attempt was made to open a database that does not exist. Probable cause is that the paths on the Global/Local INI File screens were not set up. Log into PbAdmin, go into Administrator Setup->Global/Local INI File screens and save the information. Verify paths on the Global/Local INI File screens and the environment variables. |
| -5 | DUPLICATE ERROR | A transaction currently being processed or previously processed has been received a second time. If the duplicate is of a previous transaction, setting the "Duplicates Allowed" flag to "Yes" in the Location Information screen will allow this transaction into the database. |
| -6 | FIND FIRST OR LAST | An error occurred during a search procedure. Call help desk. |
| -7 | NO MATCHING RECORDS | No matching records were found when at least one was expected. Verify information. |
| -8 | RECORD NOT A SUBSET | Same as above |
| -9 | OUT OF MEMORY | The program has run out of memory during processing. Increase memory or reduce the number of transactions being processed. |
| -10 | RECORD LOCKED | An attempt was made to modify a record that was already locked by another process. Retry the transaction, and if that fails, try reindexing the file using the DataBase Management->Rebuild Database selection in the Administrator System. |
| -11 | DATABASE NOT INITIALIZED | A transaction could not be processed due to an internal logic error. Call help desk. |
| -12 | LOCATION NOT SET UP FOR MERCHANT | The terminal given in field 109 does not reference back to a valid card number/merchant key/location combination. Log into the Administrator Setup->ProtoBase Configuration area and verify that: The terminal belongs to the proper location (Terminals). The terminal and card type combination is setup with the proper merchant key (Card Tables->Edit). The settings were successfully configured with ProtoBase (Run Configuration). |
| -13 | UNABLE TO OPEN FILE | An attempt was made to open a file that does not exist. Probable cause is that the paths on the Global/Local INI File screens were not set up. Log into PbAdmin, go into Administrator Setup->Global/Local INI File screens and save the information. Verify paths on the Global/Local INI File screens and the environment variables. Make sure the file MKEYLIST.DAT exists in the DB directory. Verify that all of the files in the DB directory have read/write permissions set for all users. |
| -14 | PROTOBASE OUTPUT FILE NOT FOUND | ProtoBase did not respond with an output file. Verify paths are set properly on the Global/Local INI File screens and environment variables. Verify ProtoBase is currently running. |
| -15 | TRANSACTION NOT YET SUPPORTED | A transaction was received in the input file that is not currently supported by the Administrator System. Call help desk. |
| -16 | FINAL AMOUNT TOO LARGE | A prior authorization or close transaction was received whose final amount exceeds the previously authorized amount for the matching reference/card number. Solutions: Issue an authorization for the difference OR Setup the Administrator System to automatically do so by setting the "Auto Authorize Difference" flag to "Yes" in Location Information. |
| -17 | SETTLEMENT IN PROGRESS | Transactions cannot currently be run because a settlement is in progress for this location. Try again later. If the problem persists and is confirmed that no settlement is actually in progress, set the "Settlement in Progress" flag to "No" in Location Information. (<Shift> + <F3> is the "hot key" combination to go to this field.) Also, go to Database Management->Modify Transaction Status and move "In Progress" to "Selected". |
| -18 | INVALID DATA IN FIELD | The field number listed contains invalid data. Consult the "Input Fields with Descriptions" section for validation criteria. |
| -19 | INVALID LENGTH FOR FIELD | The field number listed is either missing or contains invalid data. Consult the "Input Fields with Descriptions" section for valid lengths. |
| -21 | CANNOT OPEN TABLE FILE | The reversal file "pbrevsup.txt" or history file "pbhstbl.tbl" could not be accessed. Verify paths on the Global/Local INI File screens and environment variables. Verify the files exist in the DB directory. Verify files have read/write permissions for all. |
| -22 | BATCH OUT OF BALANCE | For host capture systems only. The batch totals of the Administrator "shadow" file do not match what the host processor expects. Extra reconciliation with the processor should take place. |
| -23 | ERROR MOVING TO HISTORY-BATCH GOOD | An error occurred while moving an approved settlement to history. These records will usually show up with a status of "I" on the Select/View/Edit Transactions screen. Confirm with the processor that the settlement was accepted. If batch was accepted, use the Database Management->Modify Transaction Status utility to move the in-progress (I) transactions to history. If batch was not accepted, use the Database Management->Modify Transaction Status utility to change all of the in-progress (I) back to selected (X). |
| -24 | ERROR RESETTING WORKING FLAGS-BATCH BAD | An error occurred while moving an approved settlement to history. These records will usually show up with a status of "I" on the Select/View/Edit Transactions screen. See above for procedures. |
| -25 | ERROR RESETTING WORKING FLAGS-BATCH GOOD | An error occurred while moving an approved settlement to history. These records will usually show up with a status of "I" on the Select/View/Edit Transactions screen. See above for procedures. |
| -26 | FILE NOT FOUND | An attempt was made to open a file that does not exist. Verify paths on the Global/Local INI File screens and the environment variables. |
| -27 | RETURN CODE NOT FOUND | An error occurred when trying to access file. Call help desk. |
| -28 | SHELL PROGRAM NOT RUNNING | An error occurred while attempting to run the Administrator System on an OS/2 operating system and the shell program has not been started. Start shell program (PBSHELL.EXE). |
| -29 | UNABLE TO CREATE CHILD PROCESS | An error occurred while attempting to spawn a process. Call help desk. |
| -30 | FILE LOCKED | An attempt was made to access a file that is already locked by another process. Try again later, or look for *.LCK files in the subdirectory. If message continues, call help desk. |
| -31 | UNABLE TO OPEN VALID.DAT | The specified file could not be opened. Check permissions, see if the file still exists, or look for *.LCK files. |
| -32 | UNABLE TO OPEN REVSUP.TXT | The specified file could not be opened. Check permissions, see if the file still exists, or look for *.LCK files. |
| -33 | (Not used at this time) | (Reserved for future use.) |
| -34 | UNABLE TO OPEN PBERROR.TXT | The specified file could not be opened. Check permissions, see if the file still exists, or look for *.LCK files. |
| -35 | UNABLE TO OPEN PBADERRS.TXT | The specified file could not be opened. Check permissions, see if the file still exists, or look for *.LCK files. |
| -36 | UNABLE TO OPEN MKEYLIST.LCK | The specified file could not be opened. Check permissions, see if the file still exists, or look for *.LCK files. |
| -37 | UNABLE TO OPEN MKEYLIST.DAT | The specified file could not be opened. Check permissions, see if the file still exists, or look for *.LCK files. |
| -38 | UNABLE TO OPEN TERM.DAT | The specified file could not be opened. Check permissions, see if the file still exists, or look for *.LCK files. |
| -39 | MASTER INDUSTRY ERROR | A transaction cannot be run through a terminal set to a "Master Industry" location. |
| -40 | DEBIT CODE ERROR | A transaction illegal for Debit was attempted with the Debit qualifier set. This is an integration error. |
| -41 | UNABLE TO OPEN PROTOBASE BATCH FILE | A batch file was not successfully created for ProtoBase to settle, or PbAdmin could not open a batch file after settlement. Check the batch file or other files in the settlement directory for errors. Call help desk. |
| -42 | UNABLE TO OPEN PROTOBASE OUTPUT FILE | PbAdmin could not open the output file after a transaction was run through ProtoBase. This indicates ProtoBase abnormally terminated without returning an output file. Call help desk. |
| Any # not in this table | UNDEFINED ERROR | An unknown error was encountered. Call help desk and report the error number. |
PBAdmin Errors
The following errors may be displayed when accessing PBAdmin:
| Error | Description/Solution |
|---|---|
| Access Denied! | The logged in user does not have security permissions to perform this function. |
| American Express Pending | There is already an American Express settlement pending. This deposit must be cleared either manually or by calling the processor to check the status via the "View Deposit Log" option. If there is no actual batch pending, change the "American Express Pending" flag to "No" in Location Information. |
| At least two fields must be used | At least two fields must be entered to perform a proper search. |
| Cannot access settlement file | The settlement file could not be accessed. ProtoBase is currently settling another batch. Try again later. Make sure permissions for the ProtoBase directory are set for read/write. |
| Cannot lock file. Already in use | The record is already in use by another process. The changes could not be saved. Try again later. |
| Cannot remove current user. NOT DELETED! | An attempt has been made to remove the logged in user. This is not allowed. |
| Card type not valid for this location | This card type is not set up for the location in question. |
| Changes have been saved | The changes have been successfully saved |
| Comm Director not running | During settlement, PbAdmin determines that the ProtoBase communications director is not running. Ensure the director is running. |
| c-tree Error | C-tree encountered a memory error. Increase the largest executable size (available memory) |
| c-tree Internal Error |
For unknown reasons, an error occurred while attempting to access any of the c-tree databases. Possible reasons:
|
| Delete program not found | The program "admpurge" was not located in the base Administrator System directory. |
| Error configuring card types |
The file "master.crd" in the Administrator DB directory could not be accessed.
|
| Error configuring modems | The file "ucomm.dat" in the Administrator DB directory could not be accessed. Verify file paths on the Global/Local INI File screens and environment variables. Verify the directory and file permissions for the DB directory are set to read/write for all. After running "Run Configuration", confirm the "ucomm.dat" file exists. |
| Error configuring processors | The file "uproc.dat" in the Administrator DB directory could not be accessed. Verify file paths on the Global/Local INI File screens and environment variables. Verify the directory and file permissions for the DB directory are set to read/write for all. After running "Run Configuration", confirm the "uproc.dat" file exists. |
| Error configuring terminals | The file "uterm.dat" or "<terminal>.dat" files in the Administrator DB directory could not be accessed. Verify file paths on the Global/Local INI File screens and environment variables. Verify the directory and file permissions for the DB directory are set to read/write for all. After running "Run Configuration", confirm the files exists. |
| Error deleting record | The selected record could not be deleted: Record is already locked by another user. Try again later. c-tree encountered a memory error. The files in the Administrator System DB directory do not have read/write permission. |
| Error during status check | An error occurred during the American Express status check. Either no status was available, or some other error occurred. Try again later. |
| Error executing ProtoBase configuration program | The ProtoBase configuration program "pbconfig" could not be executed. Possible reasons are: "Pbconfig" is not located in the ProtoBase directory. You are running 32 bit ProtoBase with PBOS=DOS or PBOS=Client. The paths on the Global/Local INI File screens and in environment variables are invalid. "Pbconfig" does not have read/write/execute permissions set for all. |
| Error Loading File – Not enough Memory | The program is running out of memory. In a DOS system, increase available memory (largest executable program size). |
| Error purging file | An error occurred while attempting to purge records from a file. Make sure that the Administrator System DB directory and all of its files have read/write permissions set for all. |
| Error rebuilding index | An error occurred attempting to reindex a file. Make sure that the Administrator System DB directory and all of its files have read/write permissions set for all. |
| Error saving file NOT SAVED | An error occurred while attempting to save a file. Verify file permissions. |
| Error setting up choice list |
The choice list file could not be created and read into memory. Possible reasons:
|
| Error writing to printer | Check printer and printer settings. |
| File Saved Successfully | Your file was saved. (Not an error.) |
| File too Large for Default Viewer | Open the \rdp\pb\db\pbadmin.stl file using NOTEPAD (Start - Programs - Accessories - Notepad). Delete old deposit logs. Note: Keep deposit logs for dates of currently checked-in guests. |
| Insufficient Memory Available | Increase largest executable program size. |
| Invalid account number | The account number is invalid. The card type is not setup to be accepted by this terminal. The card did not pass a MOD 10 check. The card number contained invalid data. The length is incorrect. Re-enter, or check configuration. |
| Invalid amount entered | The dollar amount entered is invalid. Missing decimal point. Too many numbers to add decimal point. Amounts may not be negative. |
| Invalid expiration date | The card is expired or the date entered is not a proper date. |
| Invalid login. Access denied | The permissions set for this user do not allow access to this selection/function. |
| Invalid mag stripe info entered | The track information does not match between track 1 and 2. |
| Invalid Merchant Key |
One of two errors have occurred:
|
| Invalid password. Please reenter | The password corresponding to the previous login is incorrect. |
| Invalid printer parameters in file | The Administrator file "print.txt" contains invalid data, or is corrupted. Try selecting a different printer. |
| Invalid printer port | The port specified in the Location Information screen cannot be accessed |
| Invalid processor | The processor entered is not in the ProtoBase merchant file "pbmerc.dat". Please verify. Call help desk. |
| Invalid Range Entered for Card | A card BIN range must have a lower number on the left and a greater number on the right. |
| Invalid Record -- Duplicates Existing Entry | The entry you are saving already exists in the database. |
| Invalid selection | The value entered in this field is invalid. Press the [F2] key to view a list of valid values. |
| Invalid terminal/location combination entered | The terminal selected for this transaction does not belong to the currently logged in location. |
| No printer defined | No printer type has been defined in Location Information. |
| No records available for selection | PbAdmin cannot find any records of the requested type in the database. |
| No settlement pending | There is not settlement currently pending with American Express so the status check could not be performed. If this is incorrect, change the "American Express Pending" flag to "Yes" in Location Information and run again. |
| Printer is currently busy | Printer has sent back a busy signal, try again later. |
| Printer is out of paper | Printer is offline or out of paper |
| Printer is turned off or is offline | Printer is offline or not turned on. |
| Processor setup files not found | The ProtoBase setup files "pbset#.dat" and "pbmrc#.dat" are not currently located in the ProtoBase directory. Please verify. Call help desk. |
| ProtoBase Configuration program not found |
The program "pbconfig" was not found in the ProtoBase directory:
|
| ProtoBase is currently running a deposit | The reconfiguration could not be completed because ProtoBase is currently running a settlement. Try again later. |
| Record is No Longer Valid | A record on the screen has been deleted or changed. Exit and re-enter the Select/View/Edit Transactions screen to refresh the display. |
| Reference number not found | The reference number entered is not located in the current work file. |
| Report generator not found | The program "pbadrep" was not located in the base Administrator System directory. |
| Required Field not Entered – Not Saved | The cursor will be placed on the missing field when the message is cleared. Please enter a value for this field. |
| Restart ProtoBase to activate new settings | Upon successful completion of "Run Configuration" ProtoBase must be brought down and restarted for the updated values to be activated. |
| Sale not Valid—Use Prior Auth | Indicates that a Sale transaction has been entered for a non-host processor. Enter as a Prior Authorization transaction instead. |
| Selected file not found | The Administrator could not locate a required file. This can also happen if you perform a report that generates no data, or if your database contains no data. Call help desk. |
| Sorting program not found | PBSORT (for non-UNIX) or SORT (for UNIX) could not be executed. |
| Terminal Mkey does not match transaction Mkey | The terminal deposit Mkey currently defined does not match information in the transaction. You may attempt to fix this on the Database Management menu. |
| Terminal not valid for this location | The specified terminal is not set up for the current location. Select a valid terminal. |
| Transaction not found | No transaction was found that matched the entered criteria. Make sure the cursor is at the top of the database ([Shift]-[F7]) and try again. |
| Transaction status error - change not allowed |
The status flag indicator of this transaction is set to a value that does not allow editing. Status flags that cannot be edited are:
|
| Transaction type error - change not allowed |
The transaction type/code of this transaction is set to a value that does not allow editing.
Current transaction types that cannot be edited are:
|
| Unable to access choice list file |
The choice list file could not be created and read into memory. Possible
reasons:
|
| Unable to access help text file/td> |
The help text file could not be read into memory. Possible reasons:
|
| UUnable to access modem file | The file "ucomm.dat" in the Administrator System DB directory could not be accessed. Verify file paths on the Global/Local INI File screens and environment variables. Verify the directory and file permissions for the DB directory are set for read/write for all. If running "Run Configuration", confirm the "ucomm.dat" file exists. |
| Unable to access PBMERC.DAT |
The ProtoBase setup file "pbmerc.dat" cannot be accessed:
|
| Unable to access printer defs file |
The Administrator file "print.txt" was unable to be accessed.
|
| Unable to access processor file |
The file "uproc.dat" in the Administrator System DB directory could not be accessed.
|
| Unable to access report file | The report file could not be accessed. No records were found to generate the report. |
| Unable to access selection list | The processor, terminal, or device list could not be built. Verify the Administrator System DB directory has read/write permissions set. |
| Unable to access terminal file |
The file "uterm.dat" or "<terminal>.dat" files in the Administrator System DB directory could not be accessed.
|
| Unable to build selection list | The processor, terminal, or device list could not be built. Verify the Administrator System DB directory has read/write permissions set. |
| Unable to change directory |
An unsuccessful attempt was made to change to a specific directory.
|
| Unable to change industry because unsettled records exist | An attempt has been made to change the location industry code while unsettled transactions are still in the current working database. Settle or remove existing settleable transactions. |
| Unable to execute Editor command | Unable to execute the optional internal viewer program. Check path on the Global/Local INI File screens. |
| Unable to execute settlement program PBADSET |
The settlement program "pbadset" could not be executed. Possible reasons:
|
| Unable to execute System command | Unable to "shell" to a subprogram. Check for bad COMPSEL (DOS) or PBOS setting. |
| Unable to open file |
An error occurred while attempting to open a file.
|
| Unable to open PBCONFIG.CFG | The ProtoBase file "pbconfig.cfg" in the ProtoBase directory could not be accessed. Verify the directory and file permissions for this directory are set to read/write for all. |
| Unable to update selection list | The processor, terminal, or device list could not be built. Verify the Administrator System DB directory has read/write permissions set. |
| Unable to write to Administrator Log | The location’s Administrator Log could not be updated. Make sure all of the files in the Administrator System DB directory have read/write permissions set for all. |
| Unable to write to printer port | The port specified in Location Information cannot be accessed. Check permissions, verify path, and configure the device name. |
| Support Home | RDPWin4 & PCI Compliance | Enhancement Requests | Open A Web Support Ticket |
|---|---|---|---|
| Training | New Sales Website | Old Sales Website | Contact Us |
 |