BERG Division of DEC ABID1 All-Bottle ID System (Liquid Dispensing Unit) User Manual Infititl4

BERG COMPANY Division of DEC International, Inc. All-Bottle ID System (Liquid Dispensing Unit) Infititl4

UserManual.wiki >

BERG Division of DEC >

ABID1 User Manual >

User Manual Part 6

23-2 Infinity Installation/Service and User ManualInfinity SpecificationsInfinity ECUDispenser type: All-Bottle or LaserDispensers per ECU: 1 or 2 Laser, 1 All-BottleECU dimensions : 6.75 in (172 mm) H10.5 in (267 mm) W4.5 in (115 mm) D [+ 3.25 in (82.6 mm) clearance]Mounting: Wall or under cabinet w/screwsEnclosure: Black anodized aluminumWeight: 5 lbsParallel information port: StandardRS-232 Serial Data Port: StandardRS-485 Communication Ports: 2 StandardMaximum distance to 485 Converter: 4000 ft (1219 m)Optional drip-proof enclosure: Stainless steel construction8.25 in (210 mm) H11.75 in (299 mm) W8.0 in (203 mm) DDrip-proof enclosure weight: 3 1/8 lbsECU electrical requirement: 120 VAC, 50-60Hz240 VAC, 50-60HzCertification: Conforms to ANSI/UL Std. 1950 (Third Edition)Certified to CAN/CSA Std. c22.2 No. 950-93All-Bottle DispenserDispenser type: Patented bottle inserts and activator ringNumber of brands: UnlimitedNumber of price codes: Up to 7Number of price levels: 3Number of portion sizes: 3 sizes/price code/price levelPortion sizes: 0 to 30 oz (0 to 887 ml)Security: Dispenser unit - key lock-outBottles - 2 levels (pourers/seals)I-Box dimensions: 2.5 in (64 mm) H5.0 in (127 mm) W [+ .75 in (19 mm) ring clearance]4.0 in (101.6 mm) D [+3.25 in (82.6 mm) clearance]Drip guard dimensions: .25 in (64 mm) H5.5 in (139.7 mm) W4.5 in (114.3 mm) DActivator ring holder mounting plate dimensions: 1.5 in (38.1 mm) W3.0 in 76.2 mm) DStandard cable length: 15 ft (4.6 m)I-Box mounting: Slide plate w/screwsI-Box enclosure: Stainless steelI-Box weight: 2 1/4 lbsDistance from ECU: 15 ft (4.6 m) standard cable25 ft (7.6 m) optional cable150 ft (45.7 m) maximum distanceFunction controls: Portions (S,R,L)Price levels (A,B,C)Function indicators: LEDs for portion size, price level(flashing for complimentary)With some exceptions. SeeConnect a Local Networkin the HardwareInstallation section.

23-4 Infinity Installation/Service and User ManualInfinity SpecificationsTAP 1 Tap ControllerNumber of portion sizes: 4 or 8 (3 or 7 with add-a-head)Maximum portion size: 99.99 oz (2.95 l)Flow rate: As defined by beer systemOther controls: Repeat function and cancelSecurity: Head key lock (to clean or convert to manual mode)Enclosure: Stainless steel & high-strength plasticDimensions: 3.4 in (87 mm) H x 2.0 in (50 mm) W x 2.9 in(75 m) DFaucet: Standard beer dispense styleOperation type: nOpen - pneumatically operated 55 psi (3.8 Bars)air or CO2nClose - spring loaded returnPower at head - Electrical: 15V supply (from remote console)Keypad: 6 button, backlit, moisture-resistantDistance from console: Up to 100 feet (30.5 m)Weight: 0.8 lbs (.37 Kg)Other: nAccommodates standard beer dispense handle(3/8” - 16)n10,000 actuations per pound (.45 Kg) of CO2TAP 1 ECUNumber of stations: Up to 8Number of draft brands: Up to 8Security: Key lock - ON/OFF -- calibration, reportingPassword security option availableEnclosure: Powder coated aluminumDimensions: 3.9 in (100 mm) H x 7.7 in (195 mm)W x 8.5 in (216 mm) DWeight: 2.7 lbs (1.23 Kg)Power at console - Electrical: 90 - 250 VAC, 50/60 Hz (external), 24 VDC (console)Display: LCD display of quantity dispensed and sales amountKeypad: 20 Key (programming price levels, etc.)Other: Memory - battery backupTAP 1 Flow MeterLocation: Installed in beer feed lineType: Turbine/magnet, pulses based on volumeDistance from console: Up to 500 feet (152.5 m)Sensor: Hall effectDimensions: 1.2 in (30 mm) H x 1.0 in (25 mm) W x 2.4 in(61 mm) LWeight: 0.13 lbs (.06 Kg)Other: n1 required per linenUses 29/32 in (23 mm) std. beer coupling nuts &tailpiecesnLong-life sapphire bearings

23-6 Infinity Installation/Service and User ManualInfinity SpecificationsComputer Requirements To use Infinity software, you need to meet the following minimum requirements:IBM compatible PC: PentiumOperating system: Windows 95, 98, 2000, ME or Windows NT 4.0.(Windows 95 should have Service Pack 1 or laterapplied. Windows NT 4.0 must have Service Pack 2 orlater applied.)RAM: 8 MBVideo monitor: Standard VGA resolution (640 x 480)Available hard disk space: 18 MBAvailable COM port: At least one (switchbox if using server ID)Berg strongly recommends the following computer requirements:IBM compatible PC: Pentium 66Operating system: Windows 95, 98, 2000, ME or Windows NT 4.0.RAM: 16 MBVideo monitor: Standard VGA resolution (640 x 480)Available hard disk space: 18 MBAvailable COM port: Two (if using server ID)Power supply: Uninterruptible Power Supply (UPS) unitSoftware FeaturesnOptional password protectionnFlexible, expandable system setupnControls and reports on every drink pourednAccounts for complimentary pouringnGenerates custom management reportsnInterfaces with ECR/POS systemsnExports data to other software applicationsnSchedules routine management and reporting tasksnAllows remote access to reports with a modemServer IDType: Programmable access keysNumber of servers: Unlimited (for the system or if sent to POS system)20 at one time per ECU10 at one time per TAP 1 partition if > 4 partitionsSecurity: Keys - 2 levels (system code, individual ID)Remote Server Access BoxDimensions: 2.5 in (64 mm) H5.0 in (127mm) W4.5 in (115 mm) D [+ 2.5 in (64 mm) cable clearance]Mounting: Under cabinet with screwsEnclosure: PlasticShipping weight (w/cable): 1 lb 14 ozDatakey Programming BoxDimensions: 1 in (25.4 mm) H2.38 in (60.5 mm) W3.88 in (98.5 mm) DMounting: DesktopEnclosure: PlasticShipping weight (w/cable): 15 oz

SECTION24 TroubleshootingThis section provides help with the following troubleshooting topics:Troubleshooting Tips .................................................................... 24-2Avoiding Problems ........................................................................24-4Local Network Communication Problems.................................... 24-5Remote Network Communication Problems ................................ 24-8Modem Dip Switch Settings .......................................................24-10Pouring Problems ........................................................................ 24-11Software Problems ......................................................................24-14Report and Export Problems ....................................................... 24-15Schedule Problems ...................................................................... 24-17Server ID Problems ..................................................................... 24-18

24-2 Infinity Installation/Service and User ManualTroubleshooting TipsThe following tips help you pinpoint the cause of a problem. This may help you solve theproblem on your own or at least help you explain the problem to Berg service personnel.Isolate the problem qHave you checked all of your cabling and connections?Some ECU problems can be solved by a simple reset of theECU. Just unplug the ECUs power cord, wait for five seconds,and then plug it back in and try again. This is a good place tostart for many electronics problems, even if you cant isolate anddefine the problem. This will not cause you to lose any sales orsetup data in the ECU.qAre all options in the software and at the dispenser(s) setcorrectly?qWhat is the exact nature of the problem? (e.g. Does the PC lockup or crash? Are your reports inaccurate? Are yourdispensers not pouring? Are scheduled events notrunning?)Try to narrow down the diagnosis by testing and excludingspecific possibilities, one at a time. Determine, if possible,whether the problem lies in the software, or in the computerhardware or in the station components.Determine the scopeof the problemqIs the problem continuous or intermittent? Is it predictable orrepeatable? If so, how?qAre all prices and portions affected, or only some of them?qIf it involves the software, what exactly does the screen say?Describe it and write it down.qWhat was the last thing you did before the problem appeared?qHave you previously done the same operation successfully, withthe same setup? Recently?qDoes the problem happen with cocktail pours?qDoes the problem happen with comp pours?qDoes the problem happen with manual pours?qDoes the problem happen with alternate sizes?qWhat have you done to try to fix or work around the problem?Did it work?

Troubleshooting 24-3qHow severe is it? Does it prevent you from operating?qDid this occur while you were operating live, or in Schedule?qIf it involved a schedule running, what do the schedule log andthe related .ERR file say?qIf it involves a TAP 1 ECU, are you operating in stand alonemode, or are you interfaced to the Infinity software? Howis the TAP 1 ECU partitioned? Which partitions areaffected?qIs there diagnostic information available?qDid you try any of the available diagnostic checks? (e.g. CheckECU Memory, the Diagnostics menu in Utilities, Scandiskor Chkdsk, virus checkers, etc.)Review your systemsetupIf you decide to call Berg personnel for assistance with aproblem, they are likely to ask you a variety of questions to helpdiagnose the problem. You can help by being prepared to answerquestions about your Infinity setup and the exact nature of theproblem.qAre you using Infinity, TAP 1 or 1544 Infinity ECUs? If theproblem happens on one type, does it happen on the other?qAre you using a local or modem network?qAre you using an ECR or POS interface and the Interfacesoftware?qHave you recently changed anything in your Infinity systemsetup and configuration?qHave you recently installed other new devices or software onyour computer?qWhat version of the Infinity software and ECU EPROMs doyou have?Version NumberslSoftware version number:Select About Infinity... fromthe Help menu of any Infinityprogram to determine theversion number.lEPROM version number: Run aConfiguration Report todetermine the EPROM versionnumber in your ECU(s).lFor TAP 1 and 1544 InfinityECUs, you can also cyclepower at the ECU and readthe version number displayedat power on.lAn All-Bottle ID dispenserdisplays ECU and dispenserEPROM at power on.

24-4 Infinity Installation/Service and User ManualAvoiding ProblemsYou can avoid some of the most commonly-reported problems by performing the followingprocedures.Calibration Taking the time to calibrate the system prevents future pouringproblems. If you dont calibrate the dispensers in your system,inconsistent portion sizes can result. You should calibrate alldispensers at the time of installation and any time you install anew dispenser or make changes to tubing runs. See theCalibration section.Back up configurationsettingsWith a backup copy of all your setup data, youre prepared in theevent of computer problems. You should back up configurationsettings at the time of installation and any time you makechanges to setup data. See Store Configuration Settings in theDatabase Management section.Maintain the system Perform cleaning and maintenance tasks at regularly scheduledintervals. This extends the useful life of your dispensers andprevents electrical and pouring problems. See the Maintenancesection of this manual and the Laser and TAP 1 Manuals.

Troubleshooting 24-5Local Network Communication ProblemsCommunication errors can occur for a number of reasons, and can be difficult to isolate. Oncediagnosed however, the problem is usually a faulty cable connection. The two most effectivetools for solving communication problems are the loopback tester (Berg PN 8009196), and theRS485 network tester (Berg PN 8005830). Both come with detailed instructions.Local network connections The first step in finding a communications problem is to checkall connections as described below. You want to determinewhether the communications fail for only a single ECU, or forall ECUs within a network. Check the following connections:q1. Is the RS-232 to RS-485 converter plugged into thecomputers serial communications port?q2. Is the power transformer for the converter plugged into a'live' outlet and into the converter?q3. Is the network cable plugged into the converter?q4. Are the ECUs power cords plugged into a 'live' outlet?q5. Is the network cable connected to the computer? (If a TAP1 ECU is included in this network, there is an additionaladapter cable assembly that connects between the networkcable and the first TAP 1 ECU.)q6. Are the ECU addresses correct? Be sure each has a uniquenumber.q7. Is the communications baud rate for the network set to thesame baud rate as the ECUs?q8. Is the correct communication port (entered during Networksetup) being used?q9. Are the settings for the COM port itself correct?If youre having trouble communicating after updatingfrom a DOS version of Infinity, the problem may be due tochanges made to the COM ports IRQ or address with theold version of Infinity. Those settings are no longer madein Infinity; theyre defined by Windows. Find a copy ofthe settings from your old version and enter them usingWindows.Loopback tests If you cant determine the problem by checking cableconnections, perform loopback tests until the problem isdiagnosed. See Loopback Test in the ECU Diagnostics sectionfor help with performing the tests. Perform the tests in thefollowing order:

24-6 Infinity Installation/Service and User ManualCOM port Loopback Test1. Unplug the converter from the computers COM port.(continued on next page)2. Run the Loopback Test.If there are errors with the loopback tester disconnected andno errors when you connect the loopback tester, the COMport is OK. Perform the converter loopback test.If there are errors, either the COM port is incorrectlyspecified or the port is defective. If youre unsure this is theport youre looking for, try plugging the loopback tester intoanother 9 or 25 male pin port and see if the screen keepscounting errors. If any port you try doesnt quit countingerrors, you may have a defective serial port or you may needto change the systems settings for your COM port.Converter loopback Test1. Unplug the loopback tester from the computers COM portand plug the converter back into the COM port.2. Disconnect the network cable from the converter.3. Connect the test cable supplied with the loopback tester tothe converter (interconnecting the loopback tester andconverter).4. Run the Loopback Test.If there are no errors, disconnect the loopback tester and seeif errors occur. If they dont, youve specified the wrongport. If they do, the converter and its transformer are OK.Perform the network cable loopback test.If there are errors, the converter and/or its transformer arenot working. Substitute a different converter or transformerand run the test again.Network Cable Loopback Test1. Unplug the loopback tester from the converter and reconnectthe network cable.2. Disconnect the other end of the network cable from eitherthe network junction box or an ECU, and plug that end ofthe network cable into the loopback tester.4. Run the Loopback Test.If there are no errors, the network cable is OK.If there are errors, replace the network cable ends. If the teststill fails, the cable is probably defective somewhere in themiddle of the cable, and should be replaced.Communication WizardlYou.can also use theCommunication Wizard, whichwill guide you through a seriesof communication andloopback tests. SeeCommunicatio Wizard in theECU Diagnostics section.

Troubleshooting 24-7If the loopback tests verify proper operation of components butcommunications still fail for only a single ECU, or for only afew ECUs (but not all), perform the ECU Communication Teststo test the individual ECU cable(s).If communications fail for all ECUs within a network, theproblem is either in the software configuration (e.g., the baudrate is set incorrectly), or in some hardware component orconnection between the computer and the network.ECU communication tests Use these tests if only some of the ECUs in the network are notcommunicating with the computer. See Communication Test inthe ECU Diagnostics section for help with performing the tests.1. Disconnect all cables from one of the non-communicatingECUs.2. Connect the ECU directly to the computer using a knowngood converter and cable. The only cables required forcommunication are the power cord and the communicationcable.3. Run the Communication Test.If there are no errors, the ECU is probably OK. Using BergsRS485 Network Tester (PN 8005830) will give you a morecertain result.If there are errors, check the baud rate and ECU number setin the software and in the ECU (unplug it first). If thesettings are correct, try replacing the CPU board in the ECU.(If you switch boards, set the ECU number and baud rate inthe ECU before re-trying the Communication Test.) If thereare still errors, replace the ECU.Daisy chain cables If the ECU(s) test out OK, test the cable connecting the ECUs inthe network. If you have a problem communicating with the lastECU(s) in a daisy chain, the problem is usually a cable problem.1. Disconnect the last ECU in the chain and take it to the ECUit was connected to.2. Connect a short jumper cable between the 2 ECUs.3. Run a Communication Test.If there are no errors, the problem is in the cable previouslyconnecting the ECUs.

24-8 Infinity Installation/Service and User ManualRemote Network Communication ProblemsRemote network communication errors usually include modem errors and/or cabling connections.Check modemrequirementsIf you suspect a malfunctioning modem, first check to make surethat the modems type, configuration and operational settings areconsistent with the requirements of the Infinity system.qAll modems must be Hayes compatiblethat is, they mustrespond to the AT command set and must have Hayes-compatible S registers.qA separate phone line must be provided for each modem.qIf the phone lines at the installation are controlled by a PBXsystem, call the PBX dealer to see if that particular PBXsystem is compatible with modems.qBergs RS-485 to RS-232 converter must be inserted betweenthe network modem and the first component of thenetwork.qThe baud rate setting for all ECUs served by the same modemshould be set to the same value, not to exceed thetransmission capacity of the modem itself.Check modem lights If you have an external modem with status lights, observe thereactions of the lights to attempted communications. (A specialcommunications utility such as Telix, ProComm, Q-Modem, etc.may be helpful for these sorts of diagnostic tests.) Withconfigured modems properly connected, check to see that theAA (Auto Answer), TR (Transmit), and MR (Modem Ready/Power) lights are on. The HS (High Speed) light may also be on.As the modems communicate, the data or send-and-receive lightsshould blink.If the lights on the modems are labeled differently, use the abovenames/labels as a guide. Also, some modems have only twolights, for power and data. Verify as much as you can from theavailable lights on the modems.Check modem speakers Most modems have a speaker. As you test the modem, youshould be able to hear it take the phone line off-hook and dial.At the network modem, you should hear the phone ring, and themodem answer, and then the carrier tone.Non-Berg ModemslBerg does not supportmodems not purchased andset up from Berg.

Troubleshooting 24-9Check networksoftware setup Verify that the network setup information is entered correctly.Communication test If the software is configured correctly, test modemcommunications by running an ECU Communication Test. SeeCommunication Test in the ECU Diagnostics section for helpwith performing the test.1. Run the Communication Test.2. As the test is running, monitor the indicator lights on bothmodems. (You will need an assistant at the remote location.)Verify the following status-light activity:The data or send-and-receive light should flash on thecomputer modem. The Off Hook light should turn on,indicating that the modem is dialing, and the Auto Answerlight also should turn on.On the network modem, the Off Hook light should turn on,indicating the network is trying to answer, and you shouldthen hear a loud screeching, static-like sound. When themodem has successfully answered, the Carrier Detect lightshould turn on at both modems.During communication, the data or send-and-receive lightsshould blink at both modems.3. Stop the test.Both modems Off Hook lights should turn off, indicatingthe modems have disconnected from the phone line. Thelights on the modems should return to their original 'ready'states.If the modem lights do not respond as described above, testwhichever modem seems to be at fault (or both modems)with some other communications application (for example,by dialing an online service or Internet provider).If either of the modems fails in a test with anotherapplication, replace that modem and repeat the test.If the modem lights do respond as described above, butcommunications still fail, the problem may be within theInfinity components. Perform the loopback tests listed underLocal Network Communication Problems in this section. Usea gender changer and treat the network modems 25-pin Dconnector like the computers serial port to perform the test.Then remove the gender changer and plug the modemconverter in and proceed to test it and then thecommunication cable.

24-10 Infinity Installation/Service and User ManualModem Dip Switch SettingsIf you use a modem supplied by Berg, you dont have to worry about these settings. If you use anon-Berg modem, Berg does not support it.Computer Modem Station ModemDTR Normal DTR ForcedAuto Answer Off Auto Answer OnCarrier Detect Normal Carrier Detect ForcedLoad Factory Defaults Load Factory DefaultsSmart Mode Dumb Mode

Troubleshooting 24-11Pouring ProblemsCheck these tips and procedures for troubleshooting pouring problems. They may help solve theproblem or help you isolate and define the problem for Berg service personnel.Price level failsto switch (All-Bottleand Laser)If dispenser price levels do not switch, but other operationsappear normal, verify that price-level changes are enabled in theECU definition. If the feature is enabled and the problempersists, isolate it as follows:1. Replace the ECU with a substitute 'test' ECU, and try again.Make sure the baud rate and ECU number of the test ECUmatch those of the suspect ECU.If price levels switch with the new ECU, the problem was inthe dispenser controller board or the CPU board of theoriginal ECU.2. If price levels still do not switch, unplug the cablesconnecting the dispenser to the replacement ECU, andinspect the connections for problems such as moisture, bentpins, corrosion, etc.3. Whether or not you find an obvious connection problem,plug the cables into the original ECU (not the ECU you usedfor the test in step 1 above), and try again, and/or replace thecables and try again.4. If still unsuccessful, remove the All-Bottle or Laserdispenser from its mounting plate and remove the cover.5. Place the probes of an ohmmeter on the common andnormally open leads of the switch.The meter should read > 1000 ohms when the switch isopen, and < 2 ohms when the switch is closed.If the readings are incorrect, the switch is defective orincorrectly assembled, and should be replaced.ECU stops pouring 1. Verify that the ECU is properly connected to all dispensers.2. Verify (in software) that the portion and price level of thebrand in question is not set to zero, and that the ECU itself isnot disabled at the computer.3. Verify (if server ID is enabled at the ECU) that you have avalid server key in the remote server access box.(continued on next page)

Troubleshooting 24-15Report and Export ProblemsReport problems are usually related either to printer errors or database errors.Reports do not print If Infinity reports do not print at all, investigate the problem bythis step sequence:1. Verify that the printer is turned on, on-line, and properlyloaded with paper.2. Verify that the printer cable is securely fastened at eachendto the printer, and to the proper computer port.3. Verify that the printer is set up as the default printer inWindows. (Infinity prints all reports using the defaultprinter.)4. Execute the printer self-test. (If necessary, refer to the printermanual for directions to execute a printer self-test.) If theprinter self-test does not print, then the problem is in theprinter. Repair or replace the printer. If the printer self-testprints as it should, then the problem is probably in thecomputer.5. If the printer is ready, but Infinity reports still dont print,try printing something from another software application.If other applications can print, restart the computer to try toreestablish the printer connection.Incomplete reports qCheck the paper supply.qCheck the printers print head.Brush out any dust or paper impeding the print head.Reports do not run due to database errorsqDid the computer suffer a loss of power while a report wasrunning?Even a momentary flicker in the power supply, as sometimesoccurs during storms, can cause database errors if a reportis in progress.qPerform the Infinity database diagnostic procedures included inthe Utilities program. (See Check the Database for Errors,Rebuild the Database Index Files and Repair the Databasein the Database Management section.)qReload the backup copy of system-configuration data youstored after installation, or reload from a recent backup.(continued on next page)

24-16 Infinity Installation/Service and User ManualqInvestigate possible hard disk problems.If the disk is full (or close to full), delete any outdated orunnecessary files.To reduce the space used by Infinity sales records, ClearSales from your database at the computer. This erases allInfinity archive sales records. (See Clear Sales from theDatabase in the Database Management section.)Remove saved Infinity report files you no longer need.(See Managing Report Files in the Reports section.)Set the Archive Record Storage Length to a lower limit toconserve hard disk space. (See Data Storage and DisplayOptions in the Configuration Options section.)Several commercially available diagnostic utilities (PCTools Deluxe or Norton Utilities, among others) canautomatically inspect the surface of a hard disk and reporton any irregularities, and can even recover mostor allof the data in the event of an otherwise catastrophic diskcrash.

Troubleshooting 24-17Schedule ProblemsSchedule stopsprematurelyqVerify that an Exit Schedule action is not defined for theschedule.qCheck the schedule log and error log.The schedule log indicates when the schedule was startedand stopped. If password protection is enabled, the name ofthe user who stopped the schedule is recorded in the log.If there is no Ending Schedule X.SCH entry in the log, apower failure probably caused the computer to restart.Consider adding the schedule to your Windows StartUpgroup or folder. See Run a Schedule in the Schedulessection.

24-18 Infinity Installation/Service and User ManualServer ID ProblemsServer key does not pour qTest the key with the Datakey programming box. On the CheckServer Key screen, use Check Key or Check ECU. Thesewill verify that the key is enabled, has the current keycode, and that the expiration date has not expired.qVerify that youre pouring at an allowed station and an alloweddispenser.qWith a terminal emulator read the diagnostic port. If you read1020 instead of 744, the distance is too great. You may beable to overcome this with a remote server access boxupgrade.

Error Messages 25-1Software MessagesSECTION25This section provides explanations for the Error, Question and Warning messagesassociated with Infinity software.About Software Messages............................................................. 25-2Communication (CM) Error Messages .........................................25-4Database (DB) Error Messages.....................................................25-7Interface (ECR) Error Messages .................................................25-10General (GE) Error Messages .....................................................25-13Infinity (INF) Error Messages.....................................................25-15Manager (M) Error Messages .....................................................25-19Report (R) Error Messages .........................................................25-23Setup (S) Error Messages ........................................................... 25-25Schedule (SCH) Error Messages ................................................25-29Utilities (U) Error Messages ....................................................... 25-30Communication (CM) Questions ................................................ 25-32Interface (ECR) Questions .......................................................... 25-33Infinity (INF) Questions.............................................................. 25-34Manager (M) Questions ..............................................................25-35Report (R) Questions .................................................................. 25-38Setup (S) Questions..................................................................... 25-39Schedule (SCH) Questions ......................................................... 25-40Utilities (U) Questions ................................................................25-41Communication (CM) Warnings .................................................25-43Interface (ECR) Warnings ........................................................... 25-44General (GE) Warnings............................................................... 25-45Infinity (INF) Warnings .............................................................. 25-46Manager (M) Warnings ...............................................................25-48Report (R) Warnings ...................................................................25-50Setup (S) Warnings ..................................................................... 25-51Utilities (U) Warnings ................................................................. 25-53

25-2 Infinity Installation/Service and User ManualAbout Software MessagesMessage Identification The title bar of a message box displays the type of message(Error, Warning or Question) and an ID string. The ID stringincludes an alpha code and a number (e.g., CM03).The alpha codes are as follows:CM = CommunicationsDB = DatabaseECR= InterfaceGE = GeneralINF = General InfinityM = ManagerR = ReportS = SetupSCH = ScheduleU = UtilitiesError numbers are usually 1-99 (for Manager, the error rangegoes up to 199)Warning numbers are 100-199Question numbers are 200-299How to find an explanationMessages types are arranged alphabetically in this section(Errors, Questions, Warnings). Alpha codes are then listedalphabetically for each message type with a numerical listing foreach alpha code.For each message listed in this section, youll find furtherexplanation of the problem, a remedy and/or workaround andpossibly a diagnosis method. In many cases, the diagnosis mayinvolve sending information to Berg. See the ECU Diagnosticssection.Diagnose and Document To help with any problem, get the following information:qThe exact set of messages. Note that all messages now havean ID so you do not need to copy the entire message.qA detailed description of the steps needed to duplicate theproblem. It is often useful to try to duplicate the problemyourself to make sure you understand the steps to repeat it.qThe version number of the software (Use Help | About).qThe version number of the EPROM(s). See TroubleshootingTips in the Troubleshooting section.qThe Windows operating system of the client PC.qIt is often helpful to send a full backup (from Utilities) toBerg. Berg can then try to reproduce the problem.

Error Messages 25-3Diagnostic mode For a communication log, put the program into diagnostic mode(Ctl-ALT-D from main menu) and run the operation. Close theprogram and send the debug.inf file to Berg.Also, in diagnostic mode, many error messages will allow you toclick on a diagnostic button and get additional information aboutthe code that was executing at the time of the error. Write downthe information from this diagnostics window.Troubleshooting tips Run check database and repair database to make sure that there isnot corruption in the database.Sometimes errors will occur when there are problems with thePC. One or more of the following may also help. Run a checkdisk program and/or other PC diagnostic tools to make sure thatyour hard disk and PC are operating correctly.Shut down other programs. Sometimes other programs willinterfere with the running of Infinity programs. Or trying to runtoo many programs at the same time will overtax the computersresources.Reboot. It is not unusual for a PC to get into a state where someor all programs will not run correctly.

25-4 Infinity Installation/Service and User ManualCommunication (CM) Error MessagesNote that all communications with an ECU are tried three times. An error must be persistent inorder to produce an error message. For a communication log, put the program into diagnosticmode (Ctl-ALT-D from main menu) and run the operation. Close the program and send thedebug.inf file to Berg.ERROR CM00: Incorrect error messageExplanation This message should never appear. Either the error number was not set or the error displayroutine was called in error.Remedy Try rebooting the computer.Diagnosis Debug.infERROR CM01: Cant open comm port.Explanation This message should be preceded by CM20, CM21 or CM22. See those messages.ERROR CM02: Cant transmit data. Check comm port.Explanation Communication data being sent through the comm port never got transmitted. (The maximumtime the software waits for a transmission is 0.4 seconds (80 x 50 ms) This is probably aproblem with your comm port.Remedy Try using a different comm port or installing a new port. Rebooting or shutting down otherprograms may work if multiple programs are contending for the port.ERROR CM03: No response from unit. Fix Communication problem.Explanation The message to the ECU was successfully sent but no response was received from the ECU.This is the most common communication error. After waiting 0.4 seconds (80 x 50ms) foreach communication try, no legal response was received (both an STX and an ETX must bereceived). Usually, if you see this message, nothing was received from the ECU. There aremany reasons for this error including the ECU has no power, the ECU is not connected in theInfinity network, a converter is not present or has no power, the wrong port has been selectedor there is a loose network connection. For some older units, this error can mean a mismatchin the security code (see CM19).Remedy Try the operation again. Check all connections to the ECU and power to the ECU.Diagnosis Use the Communication Wizard to diagnose the problem.ERROR CM04: No answer from modem. Check modems or fix communication problem.Explanation This occurs on a modem network when the phone connection could not be made. Bothmodems need to be operational. Check modem settings and the modem init string and phonenumber. Both modems must not be in use by another program and must be powered on.Sometimes modems just dont connect.Remedy Try the operation again.Diagnosis Any of the conditions listed under CM03 can apply. Note that the Communication Wizardcannot be used on a modem network.ERROR CM05: Noisy communications line. Fix Communication problem.Explanation A complete message was sent to the ECU but the content was corrupted. This is often theresult of a noisy communication line.Remedy Try again. Replace the communication line. Make sure you have not exceeded therecommended line length for communication line.Diagnosis Debug.infERROR CM06: Incorrect response.Explanation The wrong ECU has responded to a communication message. One possible reason this canhappen is when an ECU has the wrong security code.Remedy Retry. If problem persists, identify the offending ECU. Cycle power on that ECU and Clearand Restore its memory.Diagnosis Use Debug.inf to identify the ECU that is inappropriately responding. You can also runcommunication tests with show error check on each ECU to see if one has the wrong securitycode (CM19).

Error Messages 25-5ERROR CM07: Unit received an invalid command.Explanation The ECU received a message that it does not know how to handle. In many cases, this isbecause the PC has misidentified the type or version of the ECU.Remedy Run Check Version or Clear and Restore Memory for the ECU.Diagnosis Run Compare ECU to see if the ECU type and model are correct. Debug.inf.ERROR CM08: Unit received an invalid price level.Explanation The ECU received a change price level command but the intended price level is out of range.This is an unlikely error.Remedy Retry.Diagnosis Debug.infERROR CM09: Noisy communications line. Fix Communication problem.Explanation See CM05. The detection of this error occurred at a different place but the error and remedyare the same.ERROR CM10: Unit received an invalid file number.Explanation ECU cannot return the type of information that the PC has requested. Usually, this means thatthe ECU type or version doesnt match the definition in the database. You can also get thiserror if more than one ECU has the same ECU number.Remedy See CM12.ERROR CM11: Unit received an invalid record number.Explanation ECU cannot return the amount of information that the PC has requested. Usually, this meansthat the ECU type or version doesnt match the definition in the database. It could also meanthe dispenser types do not match.Remedy See CM12.ERROR CM12: Record overflow.Explanation ECU has reported that the amount of data requested exceeds the amount that can be returned.Usually, this means that the ECU type or version does not match the one listed in the database.Remedy Try Compare ECU in Utilities. This will show if the ECU definition differs from the database.If differences are noted, run Restore Station Memory to reset the ECU to the proper type andversion. This can also result from a corrupted database. Run Check Database and RepairDatabase.Diagnosis Put program into diagnostics mode. Run the operation again. At the error message, click ondiagnostics button and record the information. Forward this info to Berg along with standardinformation.ERROR CM13: PC received an invalid comm error.Explanation An unknown communication error has occurred.Remedy Retry. Reboot and then retry.Diagnosis Forward a debug.inf file to berg.ERROR CM14: Network record not found.Explanation Network being used by this operation could not be found in the database. This could be acorrupted database or it could mean corrupted memory.Remedy Reboot. Retry. Possibly repair database.Diagnosis Run Check Database and Repair DatabaseERROR CM15: Station record not found.Explanation Station being used by this operation was not found in the database. Possible databasecorruption. See CM14.ERROR CM17: The ECU EPROM has been changed. Use ECU Setup to adjust ECU type or options.Explanation The ECU type or version recorded in the database does not match the actual type and versionof the ECU. This may happen when upgrading from Infinity to Infinity with All-Bottle ID. Itmay also occur if you change ECU numbers or move a database from one system to another.Remedy Set the correct ECU number on the ECU. Use Setup ECU to correct the ECU type in thedatabase. (You may need to first delete the current ECU.)Diagnosis Check ECU number. Run Compare ECU.ERROR CM18: Unit busy. Please retry later.Explanation The ECU cannot perform the operation you requested since it is performing some other task atthe moment.Remedy Retry when the other operation is completed.

25-6 Infinity Installation/Service and User ManualERROR CM19: Invalid security code.Explanation The security code in the ECU does not match the security code in the database. When thishappens, no communication is possible between the ECU and PC.Remedy Cycle power on the ECU to clear its security code. Then Clear and Restore Memory to sendthe security code to the ECU.ERROR CM20: Port %d is currently in use.Explanation Port is being used by another program or device. The device may be a modem or a mouse.Note that some programs will not release the port until they are exited. If a program crashedwhile using the port, the port may still think it is in use. When running a program in a DOSwindow, the DOS window will hold on to the port (even after the program completes) until theDOS window is closed. See also CM22.Remedy Close other programs using the port. Close DOS windows. If this doesnt work, reboot to clearthe port.Diagnosis Check that you are using the correct port  the Communication Wizard can be used for this.ERROR CM21: Port %d does not have appropriate hardware.Explanation 8250 UART or better is required to use the comm port. Most equipment (com boards, PCs,modems) will easily fulfil this requirement.Remedy Upgrade your port or PC  it is very old.ERROR CM22: Port open error %d on port %d. Port may be in use or may not exist.Explanation Port could not be opened  usually for one of the following reasons. Port is being used byanother program or device. The device may be a modem or a mouse. Note that some programswill not release the port until they are exited. If a program crashed while using the port, theport may still think it is being used. When running a program in a DOS window, the DOSwindow will hold on to the port (even after the program completes) until the DOS window isclosed.This can also mean the port does not physically exist on the computer or is not defined to Windows.Remedy Close other programs that are using the port. Close DOS windows. If these do not work,reboot to clear the port.Diagnosis Check that you are using the correct port  the Com wizard can be used for this.ERROR CM23: Invalid Parameter comport %d, tone/pulse %dExplanation The tone/pulse selection on modem network setup does not match your modem settings.Remedy Change network setup or the settings on the modem.ERROR CM24: Not supported on demoExplanation Demo attempts to mimic the operation of the live operation without actually attempting anycommunication. The operation attempted does not have a demo equivalent. It cannot bedemonstrated.ERROR CM26: You must upgrade your EPROM to use this version of Infinity.Explanation The type of operation cannot be performed by this version of EPROM. Some features cannotbe performed by all EPROMs.Remedy Contact BERG for the latest version of EPROM for your ECU type.ERROR CM27: EPROM version is unknown. Run Get Version under Manager before continuing.Explanation The ECU version type has not been recorded properly in the databaseRemedy Run Get Version or Clear and Restore Memory.ERROR CM28: MEMORY CORRUPTION DETECTED! Operation will continue.Explanation The ECU has examined its memory and found corruption. The current operation will continuebut you may not be able to trust the state of the ECU.Remedy Clear and restore memory. You may need to cycle power on the unit.Diagnosis Debug.infERROR CM29: Unexpected sequence number. Retry operation.Explanation The EPROM and PC have gotten out of sequence. The current operation is stopped. Often thisis a timing problem. This can also mean that the ECU does not support sequence numbers.Remedy Retry operation. It will most likely succeed. Clear and restore memory.Diagnosis If the error is reproducible, put the program into diagnostic mode and rerun the operation andsend the debug.inf file to Berg personnel. Run get version number. If you get a CM17, useRemedy for that error.

Error Messages 25-9ERROR DB25: Unable to perform database operation.Explanation Possible database corruption.Remedy See DB14.ERROR DB26: Unable to perform database operation. Attempting to continue.Explanation Possible database corruption. The operation is one where it makes the most sense to try tocontinue.Remedy See DB14.ERROR DB27: Too many dispensers on this ECUExplanation An operation which loops through the dispensers found more than allowed on this ECU. Orthe number of the dispenser may be more than allowed. The database may have errors. Theoperation may try to continue.Remedy Reboot and retry. Run ECU Setup and check dispensers, make corrections if needed and savethe information (Note if you change dispensers, you should also check your brandassignments.) Run Utilities to fix the database. If necessary, Restore a Full Database backupor Reload Configuration.Diagnosis Run Utilities | Check Database and Repair Database. Check for disk corruption.ERROR DB50: Fatal Error  Preparing for Infinity Database.Explanation before the database could be opened, there was some error. This is likely a system error.Remedy Reboot and retry. Run Diagnostics on your PC. Shut down other programs.ERROR DB51: Cant open Infinity Database.Explanation The database could not be opened. Sometimes follows DB52 (if so, see DB52). Databasecould be corrupted or missing.Remedy Reboot and retry. Try database repair functions from Utilities if Diagnostics indicate it.Diagnosis Run diagnostics on database. Make a full backup of your database and send to Berg.ERROR DB52: Database is locked. You may need to reboot your systemExplanation One or more database files is locked. This will happen when the database base is not properlyclosed, possibly from a program crash.Remedy Reboot and retry.ERROR DB53: Cant open Logging Database.Explanation The logging portion of the database cannot be opened.Remedy See DB51.ERROR DB54: The current database is empty.Explanation The database is present but does not contain any information. (Even a new install containssome information in the database.) This is most likely an install that was not completed.Remedy Reinstall or restore the last good backup.ERROR DB55: Some database files are missing.Explanation Infinity has identified that some of the database files are missing. This may happen if Infinityfile were deleted, you tried to copy database files or tried to use a store disk as the targetdatabase (store disks contain only configuration information, not a complete database.)Remedy Reinstall or use a full backup to restore the database. In case of deletion, try using recycle binor deleted file recovery utility present on some PCs to recover the missing files.Diagnosis Send a directory listing of the files in the Infinity directory to Berg.ERROR DB56: Logging Database cannot be accessed. Logging will be suspended.Explanation An error has been discovered in the logging portion of the database (probably duringschedule.). Logging cannot continue because of this error. The schedule will continue andother actions may be successfully completed. Logs will continue to be placed in the error fileand will also automatically be added to the debug.inf diagnostics file.Remedy Check and correct database errors. Reboot and retry.

25-10 Infinity Installation/Service and User ManualInterface (ECR) Error MessagesERROR ECR05: Interface has not been properly installed. Install Interface from setup disk.Explanation Interface should be installed from setup disks. It used to be possible to move files by hand tomimic the installation, but its no longer possible to do this. Interface setup is part of Infinitysetup and the software is installed at the same time.Remedy Reinstall using the Setup disk.ERROR ECR06 Unsupported driver. Interface options are disabled. Please reinstall Interface.Explanation The NCR 2160 is no longer supported. This message may also occur if the driver cannot bedetermined.Remedy Reinstall Interface from disk.ERROR ECR07 Unsupported driver version. Interface options are disabled. Please reinstall Interface.Explanation The driver version is old and no longer supported or the version number cannot bedetermined.Remedy Get an upgrade if appropriate and reinstall Interface from disk.ERROR ECR12: Can not open the driver file.Explanation In the process of loading a driver, the driver file itself could not be opened. The file could bemissing, the disk drive could have an error or there may be PC system errors.Remedy Reboot and retry. Fix any disk errors. Reinstall Interface.Diagnosis Check if the driver file exists. It has the drv extension. Check your hard disk for errors.ERROR ECR13: Can not open the log file.Explanation When the verbose flag is on in the ECR Configuration file, a log file gives details about theloading process. This flag should be turned on only by direction of Berg personnel. This logfile is created as a new file and overwrites any old file any time a driver is loaded. Failure tocreate this file is a disk or system error.Remedy Reboot and retry. Fix any disk errors.Diagnosis Check disk.ERROR ECR14: Illegal record type in driver.Explanation The driver file could not be interpreted. Verbose can be set on to get additional informationabout this error but the most likely cause is that the driver file is corrupted or the disk has anerror.Remedy Fix any disk errors or reinstall Interface.Diagnosis Check disk.ERROR ECR15: Undefined segment.Explanation See ECR14.ERROR ECR16: Segment is not relocatable.Explanation See ECR14.ERROR ECR17: Fatal loader error, bad TIR record.Explanation See ECR14.ERROR ECR18: Illegal TIR command.Explanation See ECR14.ERROR ECR20: Command stack overflow.Explanation See ECR14.ERROR ECR21: Command stack underflow.Explanation See ECR14.ERROR ECR22: Underflow symbol.Explanation See ECR14.

Error Messages 25-11ERROR ECR23: Loader ERROR signed byte out of range.Explanation See ECR14.ERROR ECR24: Loader ERROR signed word out of range.Explanation See ECR14.ERROR ECR25: Loader ERROR unsigned word out of range.Explanation See ECR14.ERROR ECR26: Loader ERROR unsigned byte out of range.Explanation See ECR14.ERROR ECR27: Loader ERROR mixed byte out of range.Explanation See ECR14.ERROR ECR28: Loader ERROR mixed word out of range.Explanation See ECR14.ERROR ECR29: Command 64 arithmetic rotate not implemented.Explanation See ECR14.ERROR ECR30: Command 82 invoke macro is not implemented.Explanation See ECR14.ERROR ECR31: Fatal loader error has occurred.Explanation See ECR14.ERROR ECR32: Conditional loader error has occurred.Explanation See ECR14.ERROR ECR33: Loader warning has occurred.Explanation See ECR14.ERROR ECR34: Conditional loader warning has occurred.Explanation See ECR14.ERROR ECR50: PLU cannot be removed.Explanation In the modifier order list, the PLU marker must be present. It cannot be moved off of the listsince the PLU must always be part of the packet sent to the sales terminal.Remedy This action will be prevented.ERROR ECR51: Cannot open ecr.cfg file.Explanation The interface configuration file cannot be opened. It may be missing or the disk may becorrupt or there may be a system error.Remedy Reboot and retry. If the file is missing, reinstall Interface. If there is a disk error, fix the diskproblem.Diagnosis Check disk.ERROR ECR52: Syntax error in ecr.cfg file.Explanation The contents of the configuration file have been corrupted.Remedy Reinstall Interface and use a store disk or backup disk to restore the ecr.cfg file.Diagnosis The ecr.cfg can be sent to Berg for analysis.ERROR ECR53: Internal error trying to read ecr.cfg file.Explanation The config file may be corrupted or the disk may be corrupt or there may be a system error.Remedy See ECR51ERROR ECR54: Unknown keyword in ecr.cfg file.Explanation See ECR52ERROR ECR55: Wrong number of parameters.Explanation See ECR52

25-12 Infinity Installation/Service and User ManualERROR ECR56: An old style ecr.cfg file was processed. All modifier information will be lostExplanation An older style ecr.cfg file was found and used. Since this style cannot be interpreted entirely,the modifier information if present will be lost and will not be sent to the ECUs. If you do notuse any modifiers, this will not present any problems.Remedy Under driver settings, click on save as defaults after making any changes needed. This willwrite the config file in the correct format.ERROR ECR57: At least one ECU had a communication error.Explanation When reading or writing driver or modifier settings, one of the ECUs had a communicationerror. Therefore, the information being viewed does not necessarily reflect the settings of all ofthe ECUs or the changes were not written to all ECUs. You should have seen one or more CMerrors which identify the ECUs with the errors.Remedy See CM error displayed and correct that. Retry the operation.ERROR ECR59: The ECUs did not have identical options and modifiers.Explanation When reading settings from more than one ECU, the options and modifiers were not the samefor every ECU. For most installations, this indicates an error. This may be preceded byECR57. In that case, fix ECR57.Remedy Make changes to the settings as need and send the changes to all ECUs.ERROR ECR60: At least one ECU has an older version that cannot supply modifiers.Explanation Older EPROM versions had a different style of storing modifiers. Changes made to themodifiers can be sent to the ECUs but they cannot be read and correctly interpreted by thesoftware.Remedy Upgrade your EPROM version.

Error Messages 25-13General (GE) Error MessagesERROR GE00: Insufficient memory. Please exit.Explanation There is not enough available memory to continue running. The current operation may nothave completed successfully. You should exit the program. It is unlikely any other operationwill work.Remedy Shut down all other programs and retry. In some cases, memory may have been permanentlytied up and you will need to reboot the PC. Check that you have the required memory forInfinity and if not, add memory to your PC.ERROR GE19: Cant delete database Z records.Explanation Whenever a clear and archive is done, the old last archive (Z) records must first be cleared.For some reason, this could not be done and therefore the new records cannot be written. Thisis often a result of corruption in the database.Remedy Repair database if possible using Utilities. Fix any indicated disk problems. Clear sales willclear out all archive records even when this error occurs.Diagnosis Check Disk. Run Utilities | Check Database and Repair Database to see if there are anydatabase errors.ERROR GE21: Cant delete out of date archives.Explanation Whenever a clear and archive is done, the program looks for archive records which are pastthe storage length of the archive records. These records are deleted. The deletion did not workfor some reason.Remedy See GE19. You may also be able to get around the problem by changing the storage length inSetup Configuration.ERROR GE34: Unable to open a file.Explanation A file could not be opened. It may be missing, corrupt or locked by the system.Remedy IF the file is missing, you need to contact Berg to see how to recreate it. This may involvereinstalling. Fix any disk problems. If a file is locked, you should reboot and retry.Diagnosis Turn Diagnostics mode on. Click on the diagnostic button will give the name of the file.Check the disk.ERROR GE42: Cant write to the file.Explanation The named file could not be written. This could be a disk problem or you could be out of diskspace on the disk. It could indicate a memory or system problem.Remedy fix any disk problems. Reboot and retry.Diagnosis Check the disk and make sure there is enough disk space. If problem persists, take a fullbackup and send to Berg.ERROR GE43: Unauthorized copy - Serial number mismatch.Explanation The serial number is stamped twice into the database. These two numbers are not the same.This could be the results of a bad install or an improper restoration of a database backup.Remedy Reinstall. Find a good backup and restore it. Make sure the store/reload disk has the correctserial number.ERROR GE50: Invalid User Name - Password combination.Explanation The user password combination is not valid.Remedy Check your spelling and retry. If you cannot get in at all, use the setup disk to change thepassword or to turn passwords off entirely.Diagnosis Setup can be used to confirm the names of the users but not the passwords.ERROR GE51: Couldnt find Infinity data files. Please make sure you are in the right directory or that your BERG.INI file iscorrect.Explanation The Infinity database is sought in the directory the program runs out of and in the BERG.INIfile. Usually all programs and database files are in the same directory.Remedy Reinstall.Diagnosis Check that the programs and database files are in the same directory. In particular, look for thefile infdb.dbd. Open BERG.INI (found in the Windows directory) with a text editor and lookfor the line starting with DBPATH. This should also point to the same directory.

25-14 Infinity Installation/Service and User ManualERROR GE52: Unable to recover. You will probably need to reboot your computer.Explanation Parts of the database are locked. This may have happened during a previous error.Remedy Reboot and retry.ERROR GE53: Cant change driveExplanation In trying the locate the database files, the software attempted to switch to a different diskdrive. This attempt failed. Check that the database is in the correct location.Remedy Reinstall.Diagnosis See GE51.ERROR GE54: Cant open logfile %sExplanation This error appears in the schedule log when the error file could not be opened. Note that allerrors will still be located in the schedule log.Remedy See GE34.

Error Messages 25-15Infinity (INF) Error MessagesERROR INF01: This program was not meant to be run on this version of Windows. Check that you have installed the correctversion.Explanation Because of differences in different versions of Windows, different version of Infinity havebeen produced to run on each one. The current Infinity/Windows combination will not allowInfinity to be run correctly.Remedy Get the proper version of Infinity to run on your windows or install Infinity on a compatibleversions of Windows.Diagnosis Check the release notes, manual or setup disks for the Windows Operating System versionsthat your Infinity software runs on.ERROR INF02: This ECU does not support Server ID.Explanation Older versions of ECU EPROMS do not support the current Server ID implementation. Thismessage may also indicate that Server ID has been turned off for this ECU.Remedy Enable Server ID on this ECU. If the software does not allow you to do so, then you mustupgrade your ECU(s) in order to use Server ID.Diagnosis Put Manager into Diagnostics mode and run Check ECU version.ERROR INF03: No key present. You must enter a key.Explanation You have started a function that needs a key present in the Datakey programming box. There isnot a key present.Remedy Insert the desired key and click retry,ERROR INF04: The ECU is not a member of a station listed on the key.Explanation: Server keys can list up to three stations at which they can pour. The ECU that you are checkingagainst is not one of those three stations.Remedy If you want to pour at this ECU with this key, put this ECUs station name on the key. This canbe done under Setup Server Key. You can also change the key to pour at all stations.ERROR INF05: Invalid Date FormatExplanation The date typed in could not be interpreted as a date. Check for mistyping and whether you areusing the date format you have defined under Windows Control panel.Remedy Retype a valid dateERROR INF06: Invalid Time FormatExplanation The time typed in could not be interpreted as a time. Check for mistyping and whether you areusing the time format you have defined under Windows Control panel.Remedy Retype a valid timeERROR INF07: Serial Number does not match database.Explanation The serial number of the programs is not the same as the serial number in the database. Thecould be a bad install or an improper restoration of a backup.Remedy Reinstall. Find a good backup and restore it. Make sure the store/reload disk has the correctserial number.ERROR INF08: Form # is still Loaded.Explanation This error will only be shown when in Diagnostics mode. A form used by Infinity was notproperly closed down when the program was closed. Normally, this will not cause any furtherproblems.Diagnosis Send information about this error and the circumstance which preceded it to Berg.ERROR INF09: From Date must precede To DateExplanation When a date range is given the from or start date must always precede the to or end date.Remedy Check the dates and enter a proper range.ERROR INF10: Value must be in rangeExplanation A numeric value entered was too small or too large. Usually, this message will give theacceptable range of numbers. The displayed value will be reset to a value that is legal.Remedy Enter a number within the range shown.

25-16 Infinity Installation/Service and User ManualERROR INF11: Please select an ECUExplanation The operation requested requires that an ECU number be entered or selected.Remedy Enter the ECU number.ERROR INF12: Unable to continue testExplanation A loopback or comm test cannot be completed. This will usually be preceded by some systemerror message.Remedy Provide Remedy for the initial error message.Diagnosis If there is no other error message. turn on Diagnostics and run test again.ERROR INF13: Wrong version of VSVBX.VBXExplanation The wrong version of the version checking code was found.Remedy Reinstall or get a newer version of Infinity to install.ERROR INF14: # already existsExplanation The name or number of the new item that you attempted to create already exists. For example,every station and group must have a unique name. (The duplicate name replaces the # in themessage.)Remedy Select another name or number.Diagnosis Check your existing list of items and their definitions to see if you have them defined the wayyou want.ERROR INF15: # does not existExplanation A file or item does not exist. This may be a name that you typed in or a file that normallyshould exist. If the file is missing, this may be the result of a improper installation.Remedy See GE34.ERROR INF16: The ECU does not contain a dispenser type at which this key can pour.Explanation: A server key can list which dispenser types at which it can pour. The ECU that you arechecking against does not have any of those dispensers. Therefore, this server key will notallow pouring at the ECU selected.Remedy In Server Key Setup, enable additional dispenser types.ERROR INF17: Berg Infinity Manager is currently running. You must exit or pause it before running another Infinity program.Explanation You can only run one Infinity program at a time. The Manager program is already running.Remedy Either exit the Manager program or pause it. You can pause it by closing all forms andpressing F5.ERROR INF18: Berg Infinity Report is currently running. You must exit or pause it before running another Infinity program.Explanation See INF17ERROR INF19: Berg Infinity Schedule is currently running. You must exit or pause it before running another Infinity program.Explanation See INF17ERROR INF20: Berg Infinity Utilities is currently running. You must exit or pause it before running another Infinity program.Explanation See INF17ERROR INF21: At least one item must be selected.Explanation This operation cannot proceed unless at least one item in the list is selected. There are twoselection methods. The simple method, clicking on each item, selects or deselects it. In theextended method, clicking on an item selects it and deselects all other items. To select another,hold down Ctrl key when you click. To select a range select one and then hold down shift asyou click. That will select all items between the first and second item clicked upon.Remedy Select at least one item.ERROR INF22: Server # is not on the server list.Explanation The server name on the key (given by #) does not appear in the list of servers in the database.This is an illegal key and either came from a different system or was not rewritten after youmade changes to the server list.Remedy Rewrite the key so that it contains valid server information. If the display has been changed toreflect valid information (after responding to this message), you need only click on the OKbutton on the server key form.ERROR INF23: ID Number # does not matched expected ID for this server. Changing displayed ID to expected ID.Explanation Server keys contain a name and an ID number. The number and name do not match thecombination given in the database.Remedy See INF22

Error Messages 25-17ERROR INF25: Code on the key (#) is not the system key code.Explanation The code on the server key does not match this systems code. This key came from anothersystem or was not rewritten after the code was changed.Remedy See INF22ERROR INF26: Station Name # is undefined. Resetting displayed station name to <None>.Explanation Each key can be restricted to up to three stations. The station named by # is not a valid stationname and is being removed from the list of usable stations for this key. (If all allowed stationsare set to None, then this key will work on any station provided the other restrictions are met.)This key was not rewritten after changes were made to the station list.Remedy Determine if this key should be restricted and list the allowed stations and write the key.Otherwise, write the key with the revised information. If no stations restrictions are necessary,then check the all stations box.ERROR INF27: Server name is requiredExplanation All keys must list a server name. You must select one of the server names before writing thekey.Remedy Select a server name and write the key.ERROR INF29: At least one dispenser type must be selectedExplanation Each key can be restricted to certain types of dispensers. However, at least one dispenser typemust be selected or this key will not work anywhere.Remedy Click on at least one dispenser type and then rewrite the key.ERROR INF30: At least one station must be selected (or all stations must be checked)Explanation If all stations is not checked, then at least one station must appear on the allowed stations listor this key will not work anywhere. If the key is not to be restricted to particular stations, thenall stations should be checked.Remedy Determine where this key should be used and select those stations or allow the key to be usedat any station. Write the key.ERROR INF32: The # font is missing and has been replaced by *. For best results, install the missing font.Explanation The font named by # is normally used by Infinity in its displays. It will be replaced by the fontnamed by *. This message should only appear as a program is first loaded. All functionsshould work.Remedy To avoid this message, locate and install the missing font.ERROR INF33: Maximum count was reached. All counts reset to zero.Explanation A count such as used in the communication and loopback test has reached the maximum thatcan be handled or displayed. The count will be reset to zero and the counting will continue.ERROR INF34: Cant exit program. Critical activity in progress.Explanation An Infinity function is performing a task that normally should not be interrupted. Thismessage should appear when you are trying to stop a program by abnormal means, such asshutting down Windows.Remedy Wait for Infinity to complete the ongoing task and then close the program.ERROR INF35: Required fields have not been filled in.Explanation At least one field on this form has not been filled in that must be entered in order to completethe operation. In many cases, the focus will be returned to the missing field.Remedy Identify one or more blank fields and fill them in.ERROR INF36: No current serversExplanation Many server ID functions cannot be performed until you have defined at least one server onthe system.Remedy Under manager go to Server ID | Server Setup | New to create one or more servers.ERROR INF37: The key has expired.Explanation The current PC date is past the expiration date listed on the server key. Therefore the key hasexpired and will enable any ECU for pouring.Remedy Remove or change the expiration date in Server Key Setup.ERROR INF38: The key is disabled.Explanation The server key has been disabled and will not enable any ECU for pouring.Remedy Enable the key by checking the Enable check box in Server Key Setup.

25-18 Infinity Installation/Service and User ManualERROR INF39: Internal Error  Ordinal is not in the list of legal valuesExplanation Certain items kept track of by the Infinity program have ordinal values assigned to them, thatis they have a fixed set or list of values that can be used. A reference to an item was made thatdoes not have one of the allowed values. This will usually be a program error, not a user error,hence the Internal error designation.Remedy Closing the program or rebooting and retrying may allow you to continue. Check the lastoperation you did to see if it was retained.Diagnosis Send the database backup and information about what you were doing to Berg.ERROR INF40: You must create a new Group which includes all ECUs in order to proceed with this operation.Explanation This operation can only be run on the Master Group. The software has detected that you donot have the Master Group defined.Remedy Create such a group. This is done not by adding the list of all groups to a new group but ratherby checking the box which says includes all ECUs. (This way any ECUs added willautomatically be included without having to modify this group.)ERROR INF41: You must select the Group which includes all ECUs (#) in order to proceed with this operation.Explanation This operation can only be run on the Master Group. You have such a group but it is notcurrently selected.Remedy Select the Master Group and continue with the operation.ERROR INF42: Cant open #Explanation The file named by # could not be opened. The file may be missing or there may be a system ordisk error.Remedy Fix any disk errors. Reboot and retry may clear some system errors.Diagnosis Check if the file exists and the disk for errors. Make sure the file is in the correct directory.ERROR INF43: Error in file # - Not enough fields in line !Explanation The line ! in the file named by # is expected to be a text line containing a certain number offields. Fields are pieces of text separated by one or more delimiter characters such as spaces orcommas.Remedy Change the delimiter if the file type allows you to do so (such as the sales terminal data file).Otherwise, recreate or get a replacement file from the producer.Diagnosis Print the file to confirm the number of fields. Check for the correct delimiter.ERROR INF44: Error in file # - Numeric field expected in line ! field %Explanation The file is named by # and the line number is !. The field numbered % should contain anumeric value but it does not.Remedy See INF43.ERROR INF45: # requires a numeric portion.Explanation An entered value must have a number as part of the string, such as ABC123. The values nameis given by #. An example is an order number used in Inventory.Remedy Enter a text string with a numeric portion.ERROR INF46: The maximum for the numeric portion of # is !Explanation The number that is part of the string entered has exceeded the maximum.Remedy Choose a string with a lower numeric portion.ERROR INF51: Cannot read from key unit. You must have a valid key unit on the indicated port.Explanation The Datakey programming box must be connected to the port indicated.Remedy Attach a Datakey box or correct the problem.Diagnosis Check the port you entered. You can also run a loopback test with a loopback tester to makesure you have identified the number of the PC comm port correctly. Check connections. If youare using a switchbox or AB switcher, make sure you have switched to the correct path.ERROR INF52: Error reading key. Key may be corrupt. Reinsert key and retry.Explanation There is possible corruption on the key that you are trying to read.Remedy Pull out the key, reinsert and try reading again. If this error persists, then you will need toreprogram the key by going to Server Key Setup, entering all of the desired information for thekey and clicking OK to write it.ERROR INF53: Cannot create a Dealer keyExplanation Infinity software cannot be used to make a dealer key.

Error Messages 25-21ERROR M60: Name is already being used for a Station NameExplanation You have tried to create a group using a name that is already being used for a station. Sincestations and groups are used in the same way, a group name must not conflict with any stationname.Remedy Change the station or group name. Make sure that the existing name is being used.ERROR M61: Name is already being used for a Group NameExplanation You have tried to create a station using a name that is already being used for a group. Sincestations and groups are used in the same way, a station name must not conflict with any groupname.Remedy Change the station or group name. Make sure that the existing name is being used.ERROR M74: Product already assigned. It cannot be deleted.Explanation A prices and portion table cannot be deleted if it is assigned to a dispenser.Remedy Remove assignment and then delete the table.Diagnosis Check the Show Product assignments box to see where this price and portion table is assigned.ERROR M80: Partition # is not being usedExplanation At least one dispenser must be assigned to each partition. There is at least one partition whichdoes not have any dispenser assigned. You may have forgotten to indicate to which partitioneach dispenser belongs.Remedy Reduce the number of partitions (use Change button) or assign at least one dispenser to eachpartition (on dispenser tab).ERROR M82: Not supported for this ECU typeExplanation This function cannot be performed for any ECU of the type (Infinity, Tap 1) selected. Youmay have selected an ECU other than the one intended.Diagnosis Check the type of the ECU selected.ERROR M93: Actual ECU type is different than the type selected. Check ECU type before proceeding.Explanation The ECU type is different than the type defined in the database. Exit out of this function.Remedy Use F8 to check the ECU type listed for the ECU. Make sure that more than one ECU doesnot have the same ECU number.ERROR M94: This operation is not allowed while one or more units are in calibration mode.Explanation Certain operations are not allowed when at least one ECU is in calibration mode.Remedy Take all units out of calibration mode and retry the operation.ERROR M96: Large portion must be at least three times small portion.Explanation When doing calibration for a unit that uses portions, the large portion should be at least 3times the small. This gives the best results in calibration.Remedy Choose new large or small values to meet this requirement.ERROR M97: This operation is not legal with the Portion Lockout Jumper presentExplanation When the portion lockout version of the software has been purchased, changes to portions canonly be made when the jumper inside the ECU is moved to its inactive position or is removed.This keeps unaccounted portion changes from being made.Remedy The ECU must be opened and the jumper removed before any changes can be made.ERROR M98: Dispenser does not existExplanation The dispenser selected does not exist and the intended operation cannot be performed.Remedy Go to ECU Setup and add the missing dispenser.Diagnosis Check that you have selected the correct dispenser for this ECU.ERROR M100: A modem network requires a phone numberExplanation When the modem checkbox is checked, this means the Infinity network is using a modem line.A phone number is required to dial up the remote modem at the ECU site.Remedy Enter the phone number or uncheck the modem box if this network is not using a modem.ERROR M101: # value is not supported by this ECU. Resetting to legal value.Explanation A feature or value is not supported by this ECU. (# gives the name of the feature.) This may bebecause of the type of ECU or the version number. Many features are available only in morerecent EPROMs. For example, add a head limit can only be set for Tap1 EPROM of version3.00 or higher.Remedy If you wish to have this feature, you will need to upgrade your EPROM.Diagnosis If you think this feature should be available, check the ECU number.

25-24 Infinity Installation/Service and User ManualERROR R59: Both beginning and ending hour must be enteredExplanation A time range must have both a beginning and ending hour.Remedy Enter both hours.ERROR R60: Shift # is using an hour already included in shift @Explanation Shifts cannot overlap. The shifts numbered # and @ have at least one hour in common.Remedy Check the shifts in question and correct by removing the overlapERROR R61: Export to file # failedExplanation The export which was to be written to the file named by # has failed.Remedy If another error appeared before this one, fix that error first.Diagnosis Check for available disk space and run a disk diagnostics tool such as ScanDisk.ERROR R63: Minimum Zoom factor reachedExplanation You cannot zoom out any further.ERROR R64: Maximum Zoom factor reachedExplanation You cannot zoom in any further.ERROR R65: No default printer assignedExplanation Reports cannot be printed or viewed without a default printer assigned. Viewed reports areshown as they would appear on the printer: without a printer, there is no printer look toemulate.Remedy Even if you do not have a printer on your system, define a printer in control panel for viewingemulation.ERROR R67: Print Spooler is not loaded. Printing is disabled.Explanation The Windows print spooler mechanism cannot be located. No printing will work.Remedy Reboot and retry. You may need to reload parts of your Windows Operating System.ERROR R68: End of Day must not be after noonExplanation When selecting End of day, the hour must be between midnight and 11 AM inclusive.Remedy Pick a time in the AM range of hours. If you shut down before midnight, enter midnight foryour end of day.ERROR R69: No last report is present - function cannot be completed.Explanation The last report cannot be found. One reason is that you have not run any reports in thislocation. The last report is stored as a file so the other reasons have to do with not being ableto read the file. It may have been deleted or you may be experiencing disk problems.Remedy Rebooting may clear temporary problems. If disk problems are indicated, try to fix them.Diagnosis Use a disk diagnostics tools such as ScanDisk. The name of the of last report file is lastrpt.rptERROR R71: Custom Export files can only be saved to the current directory.Explanation Because it is not known when a custom export may be run, the file names are limited to thosein the current directory.Remedy Choose a local file name.ERROR R73: You must select a consecutive range of items in #Explanation All items in the list between the first and last one selected must also be selected.Remedy Check the list and select all items required.

Error Messages 25-25Setup (S) Error MessagesERROR S01: This install is for Windows 95/98, Windows ME, Windows NT and Windows 2000 only.Explanation Infinity will no longer run on Windows 3.1.Remedy Install on a PC with a more recent operating system.ERROR S02: You must have full administrator permission to install this software on Windows NT or 2000, You are not logged inas an administrator.Explanation For a Windows 2000 or NT family machine, Infinity software is set up to be installed underthe administrator. This allows all users to have access to the Infinity software.Remedy Log on as an administrator and reinstall.ERROR S03: Unable to create the directory %sExplanation The destination directory indicated could not be created. There may be disk or file systemerrors.Remedy Choose a different directory and retry. Reboot. Fix any problems indicated by disk diagnostics.Create the desired directory yourself and reinstall.Diagnosis Run a diagnostic tool like ScanDisk. See if you can create a new directory by other means.ERROR S04: Conversion failedExplanation The final steps to converting the database failed. Usually there will be a previous errormessage displayed before this one.Remedy Fix the earlier message. Then restore the previous database and reinstall.ERROR S05: Error Copying file:Explanation The file named could not be copied. This could be for several reasons. If the file is beingcopied from the setup disk, there may be an error on the disk. You may not have enough spaceon hard disk. You may be overwriting a file which is in use. You may have disk corruption.Remedy Fix any disk problems. Shut down all other programs. Try rebooting. Delete unneeded filesfrom your hard drive if you are low on space.Diagnosis Run disk diagnostics tools such a ScanDisk. Check your disk space.ERROR S06: Unable to run database conversion program. Error = %dExplanation The database conversion program could not be run. It may not be present on the setup disks,the work directory or there may be file system problems on your PC. The specific errornumber is given by %d.Remedy See S05Diagnosis Call Berg with the error number.ERROR S07: Database conversion program completed with errors.Explanation The part of the setup which will upgrade your database detected an error.Remedy Restore your previous database, reboot and retry. Run Repair Database or other databasefixing utilities on your old database to fix any indicated errors.Diagnosis After restoring your previous database, run Utilities to see if there are errors in the database. Itmay not be possible to upgrade all databases with errors in them.ERROR S08: Error deleting database work files.Explanation After converting your database, Setup will remove the work directory. These files were notable to be deleted. The setup will continue.Remedy After setup, delete the _infwork directory under your Infinity directory.ERROR S09: Internal dialog box error.Explanation Something has gone wrong trying to get install information from the user.Remedy Reboot and retry.ERROR S10: Unable to get serial number for source diskExplanation All setup disks are given a unique serial number for each customer. The serial cannot be foundor read from this set of disks. The media may be bad or there may be some system error.Remedy Reboot and retry.Diagnosis See if the disks load on another machine. Display the contents of the setup media.

25-26 Infinity Installation/Service and User ManualERROR S11: DLL Error %d - Unable to load %sExplanation One of the components needed by Setup could not be loaded. It is named by %s. It may bemissing or one of the components required by it may be missing.Remedy See S05Diagnosis Call Berg with the Error number %d.ERROR S12: An error occurred during the data move process: %dExplanation The data move is the main process of moving files from the setup media to your hard disk. Anerror has occurred on file indicated. See S05.ERROR S13: Disk set is not serialized.Explanation The serial number location was found but without a valid serial number. See S10.Remedy Ask Berg Company for a properly serialized disk if S10 remedies do not workERROR S14: Please shut down all other programs before running Setup.Explanation Installing a program always works best if no other programs are running during theinstallation. Setup has detected a program that might interfere with installation.Remedy Shut down all other programs before proceeding with setup.ERROR S15: Failure to overwrite existing database. Check returned %ldExplanation User indicated that they wanted to overwrite the existing database but setup was unable to dothis.Remedy Clear the Infinity directory yourself and retry. Also see S05.ERROR S16: This system has a 286 or 386 processor. A minimum of a 486 is required. Please contact your local computerdealer regarding possible upgrades.Explanation Infinity will not run on systems less than a 486. Berg recommends that you use a Pentium forbetter performance.Remedy Install on a more powerful PC.ERROR S17: Infinity requires at least the following Service Pack on the target machine:Explanation Microsoft often releases service packs for their Windows Operating Systems. The requiredservice pack level is not present on your PC.Remedy Download the latest service pack from Microsoft web site and install on your PC before tryingto install Infinity.ERROR S19: Error Code %d. Unable to stamp serial number to file %sExplanation The serial number on your setup disk must be stamped inside of each of the Infinity programsto ensure that there is not a mismatch between the database and the software. This stampprocess failed. The target programs may be missing or there may be hard disk or setup diskerrors.Remedy See S05.ERROR S20: %ld - Error defining dialog.Explanation A dialog to get information from the user cannot be created. The error number is given by%ld.Remedy Try rebooting.Diagnosis Call Berg with the error number if rebooting does not work.ERROR S21: The destination directory is too long. Please choose a shorter name.Explanation The destination directory is limited to 35 characters.Remedy Choose and type in a shorter destination directory.ERROR S22: This program requires VGA or better resolution.Explanation The video resolution is set lower than VGA (640 x 480). The setup cannot continue with theresolution set this low.Remedy Use control panel | Display | Settings to select a higher video resolution.ERROR S35: Cant open databasesExplanation The old or new database could not be opened. Database could be corrupted or missing. Setupmedia could be incorrect.Remedy Reboot and retry. Try database repair functions from old version Utilities if diagnosticsindicate it. If the old database is in bad enough shape, you may need to install a new system.Diagnosis Run diagnostics on old database.

Error Messages 25-27ERROR S40: Cant convert this database versionExplanation You are trying to upgrade a database which is not supported by this setup.Remedy In some cases, a two step install may be possible to upgrade. Run setup from setup2x directoryon your setup CD to upgrade from 2.x databases. For other cases, you will have to install anew system.ERROR S41: No Infinity Configuration Information. Empty database.Explanation Database configuration record is not found. This usually means that you are trying to upgradefrom an empty database that was not properly installed.Remedy Reboot and retry. Restore backup of the old database. Or you may need to install a newsystem.ERROR S42: Fatal Error  Preparing for Infinity Database.Explanation Before the database could be opened, there was some error. This is likely a system error.Remedy Reboot and retry. Run diagnostics on your PC. Shut down other programs.ERROR S46: Cant switch to %sExplanation Setup tries to change is directory to the indicated install directory. For some reason, this didnot work.Remedy Choose a different directory name. Reboot and retry. Fix any disk errors.Diagnosis Check disk for errors. Verify that the indicated directory exists.ERROR S47: Cant switch back to %sExplanation After the install, setup tries to switch back to the original directory. This failed. In some cases,this will not affect the success of the install.Remedy See S46.ERROR S57: Error creating category nameExplanation New installs will attempt to create the required category name Standard in the database. Thisfailed and a valid new database cannot be created.Remedy Check that you are not out of disk space and free some up. Check that the disk drive is notcorrupt. Reboot and retry.ERROR S58: Error creating Master GroupExplanation New installs will attempt to create the required group Master Group (which includes all ECUs)in the database. This failed and a valid new database cannot be created.Remedy See S57.ERROR S59: Error creating inventory configuration recordExplanation For new installs or installing from 3.x databases, an inventory configuration record must becreated. This failed and the install cannot continue.Remedy See S57.ERROR S60: Error creating Product TypeExplanation For new installs or installing from 3.x databases, the product types are defined in the databaseand must be created. This failed and the install cannot continue.Remedy See S57.ERROR S61: Error creating ContainerExplanation For new installs or installing from 3.x databases, the default containers must be created. Thisfailed and the install cannot continue.Remedy See S57.ERROR S62: Error creating security levelExplanation For new installs or installing from 3.x databases, the default containers must be created. Thisfailed and the install cannot continue.Remedy See S57.ERROR S70: Unable to find your Infinity directory - %s which is specified in your BERG.INI file.Explanation In order to start the configuration portion of the setup, the setup program attempts to positionat the drive and path of the Infinity directory. This attempt failed.Remedy Reboot and retry.Diagnosis Check that the directory name exists with a valid Infinity installation.ERROR S71: Unable to change to drive %s.Explanation See S70.

25-28 Infinity Installation/Service and User ManualERROR S72: Unable to start database operations.Explanation The database could not be opened to start changes that may be required for configurationsetup. This will usually be proceeded by a previous message.Remedy See the Remedy listed for first message displayed.ERROR S73: No Infinity configuration information found.Explanation See S41.ERROR S74: No users in database. Nothing to modify or remove.Explanation You cannot modify or unregister users when none have been defined. If you are trying tocreate a new user, choose register users.ERROR S75: You have passwords enabled but you do not have any users defined. You must either disable passwords or addusers.Explanation When you turn on passwords, you must define one or more users or the software can not berun. Passwords are used to start every Infinity program and determine which functions areallowed tot he user.Remedy To disable security, uncheck the password checkbox. Or, define users by using register users.ERROR S76: Unable to create dialog box.Explanation See S20ERROR S77: Unable to start help.Explanation The help file cannot be located or run on this system. This could be a error on the setup mediaor an error on your hard disk or operating system.Remedy Call Berg with your question. Reboot and retry.Diagnosis Run disk diagnostics and fix any problems found.ERROR S78: A name is required. Please enter a name.Explanation Every user defined must have a name. This name is used as part of the logon.Remedy Add a name.ERROR S79: Missing password for %s. Please enter a password.Explanation Every user defined must have a password defined. This password is used as part of the logon.Remedy Enter a password for this user.ERROR S80: Duplicate name - A user with name %s has already been registered. Please enter a different name.Explanation There can only be one user with each name.Remedy Enter a different name. If you wanted to change this users password, use modify user insteador register user.ERROR S81: Unable to Unregister user - No registration data exists for user %s.Explanation The user selected to be unregistered does not exist in the database. This is possible databasecorruption.Remedy Fix database errors. Reboot and retry. Restore good backup of the database.Diagnosis Use database utilities to diagnose any database corruption.ERROR S82: Unable to add %s (%ld) to listExplanation A text string could not be added to a list to be displayed to the user. The setup media may be inerror or there may be a system problem.Remedy Reboot and retry.Diagnosis Check setup media and hard disk for errors.ERROR S83: Load Program failed on %s - error code = %dExplanation The program named by %s could not be run. It is required for some portion of setup.Remedy See S06.ERROR S84: You must have at least four security levels.Explanation Although you can add and delete security levels, you must always define at least 4 securitylevels. (Note that you do not need to assign any users to each security level.)ERROR S85: All security levels must be consecutive. No gaps are allowed in the list.Explanation You can have from 4 to 8 security levels but they must be numbered starting at one. There canbe no gaps in the list. (Note that you do not need to assign any users to each security level.)ERROR S86: Security level %s is already being used.Explanation Each security level must have a unique name. At least two security levels have the same name.Remedy Change one of the names.

Error Messages 25-29Schedule (SCH) Error MessagesERROR SCH02: File # does not existExplanation You have a tried to select a file that does not exist and must exist for this operation.Remedy Select an existing file.ERROR SCH05: Unknown option #Explanation An option listed after an action in a schedule file is not recognized.Remedy Edit the action to make it legal.ERROR SCH06: This schedule file is not the most recent version. Some data may be lost.Explanation This is an earlier version of a schedule file. Some information may be lost.Remedy Modify the schedule file and save it. All schedule files saved from the Schedule program willhave the correct version inserted.ERROR SCH09: Current action # is not supported for this database.Explanation The action selected is not supported by this database. Therefore, a different default action willbe displayed in the Define Action form. The schedule being modified may be from a differentinstallation or the installation has been modified in some way since this schedule file wascreated. Examples: A schedule with a custom report is modified after all custom reports aredeleted. A schedule which is used to enable and disable Interface is modified after Interfacehas been removed.Remedy Delete this action, replace it with another or restore the state that was present when theschedule was created.ERROR SCH10: Custom export # does not existExplanation The custom export named in the schedule does not exist. The schedule being modified may befrom a different installation or the export has been deleted or renamed since the schedule wascreated.Remedy Delete this action, replace it with another or change the name o the export file. You may alsorestore the database that was present when the schedule as created.ERROR SCH11: Custom report # does not existExplanation See SCH10ERROR SCH14: Auto-Run or Recovery of Schedule failedExplanation You have set up an auto run schedule or a schedule has tried to recover. The schedule couldnot be run. This may be because of a mismatch in user name/passwords if you have passwordsenabled.Remedy Check that you have not deleted the user who set up the auto run schedule. If so, you mustsave this schedule under a different user. If auto run failed otherwise, try saving the scheduleagain. To just run the schedule, use Schedule | Run.

25-30 Infinity Installation/Service and User ManualUtilities (U) Error MessagesERROR U01: Current serial number was not found. Serial number was not updated.Explanation On a store where the serial number was being changed, the current serial was not found andtherefore cannot be changed.Remedy Use Help | about box to see the current serial number and try again.ERROR U03: Error loading DLL or database. Some functions will not be available.Explanation The database could not be opened or some supporting code file could not be loaded. Utilitieswill still run but a number of functions may not be available to run. Basically, any functionthat requires access to the database contents will not run. If one of those functions isattempted, an error message will be displayed.Remedy Reboot and retry. Try restoring a good copy of the database, reinstalling or emergencyrecovery.ERROR U04: Store settings was NOT completed. This disk should NOT be used for reload settings!Explanation One or more database files could not be copied. There may be missing or corrupt files in thedatabase.Remedy Check the hard disk and the destination disk for errors and correct any of them. Reboot andretry.ERROR U05: Reload settings was NOT completed. The database may have been left in an undefined state!Explanation One or more database files could not be copied into the Infinity directory. Since some of thefiles could have been, the database may have been left in an inconsistent state.Remedy Reboot and retry. Use a different store disk or backup disk. You may need to reinstall andrebuild the database from scratch.ERROR U06: Please put a floppy in the disk and close the doorExplanation You have tried to access a floppy drive but there is not floppy in the drive or the door to thedrive has not been closed.ERROR U08: Internal Disk ErrorExplanation Disk error has been detected, probably on a floppy.Remedy Check disk and repair or try with another floppy.ERROR U09: Disk is full. Please enter next disk.Explanation The destination disk is full. If it is a floppy, you may be able to continue by using acontinuation disk.ERROR U10: Disk is full.Explanation The destination disk is full.Remedy Remove unused files from your disk.ERROR U15: File # not foundExplanation File needed for the copy was not found. There is likely some file missing from your database.Remedy Reboot and retry. Look for a good restore or backup disk and restore the database. Or you mayneed to reinstall from scratch.ERROR U16: File # not found. Please enter next disk.Explanation File need for copy was not found. If there is another floppy disk, enter it now. If not, then thismay not be a good store disk.ERROR U17: This disk is not a store disk or contains a database with the wrong version. It cannot be reloaded on top of yourcurrent database.Explanation A store disk contains a file which identifies it as a store disk and gives the version of thedatabase. The file is either missing or the database has been identified as one which is notcompatible with the software. You should normally create a new store disk every time youupgrade the software and every time you make changes to the configuration.Remedy If you have the wrong disk, enter the correct in the drive.ERROR U18: This disk is not a backup disk or contains a database with the wrong version. It cannot be restored on top of yourcurrent database.Explanation See U17

Error Messages 25-31ERROR U19: Cant launch # - Error = !.Explanation The program named in the error could not be started.Remedy If the file is missing, reinstall the software. Reboot and retry. Fix any disk errors.Diagnosis See if this program exists in the Infinity directory.ERROR U20: This disk is not a store disk or contains a database that cannot be upgraded.Explanation Only certain database versions can be used in a previous reload database. This is not adatabase that can be used in this fashion or is not a store disk at all. See U17.ERROR U21: This disk is not a backup disk or contains a database that cannot be upgraded.Explanation See U20ERROR U22: You cannot choose #. It contains the current Infinity database.Explanation A Store or reload was attempted using the current Infinity database. Usually, a store is done toa floppy drive. It can also be placed in a subdirectory of the Infinity directory but cannotreside in the same location as the Infinity database.Remedy Choose a different directory or drive.ERROR U50: No automatic correction is possible.Explanation The Repair Database utility has found an error for which this is not an obvious fix. Nocorrection will be made by the utility. The nature of error will precede this error message.Remedy You may be able to remove the inconsistency by making changes in Manager. The nature ofthe changes may be suggested by the specific error. In some cases, this error may not causeany side effects and does not need to be corrected.ERROR U53: Missing system recordExplanation A system record was not found in the database. Most likely this is a result of a installation thatwas not completed.Remedy Reinstall the software.ERROR U54: Create check failed on %s.Explanation Repair utility was unable to create a new record during testing phase. The database is likelycorrupted.Remedy You may need to rebuild the index files or run the emergency rebuild utility.Diagnosis Run Check Database for Errors utility.ERROR U55: Unable to delete new %s.Explanation After creating a new record, the repair utility was unable to delete it. The database is likelycorrupted. See U54.ERROR U56: Error reading %s record.Explanation Repair utility was unable to read some database record. The database is likely corrupted. SeeU54.ERROR U57: Error traversing %s record.Explanation Repair utility was unable to traverse through all of the records. The database is likelycorrupted. See U54.ERROR U58: Error traversing %s record by key.Explanation Repair utility was unable to traverse through all of the record keys. The database is likelycorrupted. See U54.ERROR U59: Error traversing %s record by set.Explanation Repair utility was unable to access all of the records by traversing the set. The database islikely corrupted. See U54.ERROR U60: Error getting set for %s record.Explanation Repair utility was unable to read some database set for the record. The database is likelycorrupted. See U54.ERROR U61: Error setting owner of set for %s record.Explanation Repair utility was unable to find the owner for some database record. The database is likelycorrupted. See U54.

25-32 Infinity Installation/Service and User ManualCommunication (CM) QuestionsQuestion CM200: The ECU currently has different alignment values than that stored in the PC. Do you wish to reload thealignment values data from the PC into the ECU?Explanation Activator ring alignment values have been stored in both the database and the ECU but thestored values are not the same. Normally, after you Align Activator Rings, the values arestored using Store Alignment Values. If this is not done, Manager will remind you when youexit Manger. The fact that the two sets of values do not match probably means you didnt wantto store the alignment values (because they may have been done improperly).Remedy Answer Y if the last alignment done at the ECU was suspect and you want to return to the lastgood values stored in the database at the computer. Answer N if you expect the alignmentvalues are good in the ECU. In this case, you should use Store Alignment Values in Managerafter this operation is complete.

Error Messages 25-33Interface (ECR) QuestionsQuestion ECR200: Interface has just been installed. Do you want the driver to be loaded into every ECU? If you decline, youmust use Load Drivers menu choice to load the drivers into each ECU.Explanation As soon as Manager is loaded after installing Interface, it will inquire whether the drivershould be loaded into every defined ECU. If you answer Yes, the driver will be loaded in asingle step. Choose Yes unless there are some ECUs which are not interfaced. By answeringNo, the drivers must be loaded into each appropriate ECU by using Interface | Load Driver.

$Error Messages 25-39Setup (S) QuestionsQuestion S200: Do you wish to place Infinity program icons on your desktop?Explanation If you answer Yes, an icon for Manager, Report, Schedule and Utilities will be placed on yourWindows desktop in addition to appearing in the Infinity folder. If you answer No, you willneed to use the Infinity folder under Programs to start any Infinity programs.Question S201: All archive data sales will be erased. Are you sure this is what you want?Explanation Clear Sales erases all archived sales data in your database. This means you wont be able torun any date range or most recent archive reports until you next Archive and Clear Sales at theECU(s). Answer No if you want to retain your archived sales data. (Remember you can alsochoose to automatically delete sales data older than a certain date by using SetupsConfiguration | Data | Storage Length.) Answer Yes if you want to delete all archived salesfrom your database.Question S202: Do you want to load the sample database?Explanation A sample database in included with new DEMO and DISPLAY installations. The sampledatabase is populated with ECUs and assignments and lets you quickly illustrate some ofInfinitys features. Answer Yes if your would like to install this database. Answer No to buildyour own database.Question S203: You have selected to overwrite your existing installation in the directory: %s. Are you sure you want to do this?Explanation If you overwrite the database, you will lose all setup information you have already enteredsuch as ECUs, brands and sales. Overwriting results in an empty database. If you intended toupgrade this database, answer No. If you really are willing to junk your previous database,answer Yes.Question S204: Do you want a backup made of your current installation?Explanation The current database can be backed up by Setup if you like. This creates a full copy of theInfinity directory in a subdirectory named Backup. If you need to restore this version of thedatabase later, simply copy the entire contents of the Backup subdirectory into the Infinitydirectory. If you want to have this safety net, answer Yes. If you have already done a fullbackup of the database yourself, answer No.Question S205: The database in \%s\ already has an Interface installed. Do you want to overwrite the default Options andModifiers?Explanation When you install Interface, a set of default options and modifiers is also installed. If you havechanged these defaults in Manager (using Interface | Settings | Save As Defaults) and you wantto retain your defaults, you should answer No. If you want to reinstall the Berg defaults,answer Yes. If you answer Yes, you will still need to load the Berg defaults into each ECUwhich still has your defaults.Question S272: Deleting any existing security level(s) will change users and functions with that security level to the lowestavailable level. Do you want to continue?Explanation When you remove a security level, it is possible you have functions or users who have beenassigned that security level. Any function or user with the deleted security level will bechanged to the security level with the lowest priority still available (the highest numbered).Remedy Answer Yes to continue. Answer No if you want to check which user and functions may havebeen assigned to that security level.Question S273: You are about to unregister user %s. Are you sure?Explanation When you unregister a user, that user is no longer available as a name which can log on toInfinity programs. Be careful not to delete the last user without also turning off the PasswordsEnabled flag.Remedy Answer Yes if you are sure that this user is no longer needed.$