Error Messages

TLV Error when viewing reports
Module Start up Active X can not create component
Run Time Error 429 ActiveX component can't create object
Run Time Error 3343 Unrecognised Database format

TLV Error when viewing reports
This error message indicates that on a new installation some components have not installed correctly, or in an existing installation some other software has been removed and in the process, critical files have been deleted that are shared with PABXSoft. In both situations the solution is to re-install Reports and the latest upgrades.

Module Start up Active X can not create component

This error usually relates to the PBEMAIL component not having been installed correctly. Go to C:\Program Files\PABXSoft and double-click PBEMAIL to install the component.

Archiving Error Message - RTE 429 Active X Component can not create object. This is sometimes seen on Windows 95/98 and means that you should install MDAC

Run Time Error 429 ActiveX component can't create object

This error normally presents on a new installation on a Windows 95/98 PC. Typically it is because either Internet Explorer 5 (or higher) or MDAC 2.5 are not installed on the computer, or other applications were running on the computer at time of installation that share essential components used by PABXSoft.
In some cases, MDAC may have installed during PABXSoft installation but after the PABXSoft installation it may need to be installed again (Utilities folder of the PABXSoft CD contains MDAC) or paste this link to your browser
http://www.microsoft.com/data/download_250rtm.htm.
Internet Explorer 5 is also in the Utilities folder of the CD (SetupIE5)
Failing this, re-install PABXSoft with ALL other programs shut down

Run Time Error 3343 Unrecognised Database format

This indicates that one of the PABXSoft databases has suffered a corruption and can no longer be read. However, in most cases you can quickly and easily repair it using our DBView maintenance utility.

Step 1. Look at the error message and determine which database is the problem
"Pabxcalls" means the main database on the PC running PABXSoft Call Collector
"Reports" means the Reporting database on an individual PC.
You must carry out the Repair ONLY on the PC where the corrupted database is located.

Step 2. Make sure ALL PABXSoft programs are shut down on EVERY PC on your network.
(If you are repairing the "Pabxcalls" database. It does not matter about other PC's if you are repairing a local "Reports" database)
You will not be able to run the Repair utility if it detects any PC's at all are still looking at the database.

Step3. Using Windows Explorer, locate and take a copy of the database and paste it somewhere else. (This is just a safety precaution in case your repair does not work).

Step 4. Run DBView (Start/Run/PABXSoft/DBView).

Step 5. When DBView has opened, select "Database", then "Repair" and browse to the database location. (PABXSoft will automatically go to the default location). Doubles click the database (pabxcalls.mdb) and wait patiently. If the database has grown very large then the Repair can take up to 30 minutes. If the database has grown this large then the reason why it corrupted is that it is too big! Don't forget to regularly ARCHIVE your database (Reports/Maintenance/Database/Archive).