top of page

Error messages


Run Time Error 70 permission denied

Run Time Error 76 Invalid path

Run Time Error 3343

Run Time Error 3463 Data Type Mismatch

Run Time Error 390 missing component

Run Time Error 380 Invalid Property

Run Time Error 3163 Field too Small

Backups will not view / restore






Run time error 70


Run Time Error 70 is a sharing violation error. With Archive this indicates that the activity you are trying to perform should only be done if no one else is using the system, but at this time there are other users.



To overcome problem


All other users exit program

Make sure all other users of the program have closed down out of the Private Funds Manager. Then try archiving again.


Stand-alone installations

If you are the only user of the Private Funds Manager, then the error usually indicates that the program was previously closed down incorrectly or experienced a problem during close down. This leaves a locking file called PFM5.LDB on the system, which then causes the RTE 70.  


Close down Private Funds Manager. Using Windows Explorer or My Computer, navigate to the Private Funds Manager folder and delete the file called PFM5.LDB – Microsoft Access Record-Locking Information File (be very careful not to delete PFM5.MDB as this is your database!)


If you are unable to delete this file, then you will need to close down the whole PC and restart. The locking file will then automatically be deleted.






Run time error 76


This error indicates that PFM is searching for something in the wrong folder/directory.  This could be when taking or restoring a backup for example.  If you are taking a backup (ie in Period End - Archives)  click on the button at the bottom right - Restore Default - and it will locate the correct path for this operation.





Run time error 3343


Run Time Error 3343 may appear when you try to go into PFM.  Unfortunately, this indicates a major database corruption that has left your data unreadable. It generally occurs if there is major network work being done resulting in spikes being sent down the network that corrupts the PFM data.  It is unlikely you will be able to recover the data from the datafile, so will need to return to a backup.


There are various choices with this -


1. Try to 'Compact and Repair' the database.

You will need to open the file called PFM5.mdb using Microsoft Access, and run the process called Compact and Repair.   Please call Istek Support if you are not sure about this.



2. Use the PFM Safety Nets -


PFM creates its own backups of the last 4 times you have used the system. These are called Safety Net 1, 2 3 and 4 although Safety Net 1 will not be the oldest - you will need to check the dates to find the newest one. Bear in mind that the latest Safety Net may include the corruption, so you will need to check the Safety Nets - newest first, until you find an operational set of data using My Computer or Windows Explorer.  Once located, COPY the relevant safety net and PASTE it.  Find the existing file called PFM5.MDB and rename to OLDPFM5.MDB.  Then rename the copy of the Safety Net to PFM5.MDB.   Run your program and it should now load.  GO straight to the Audit Trail on Screen Enquiries to see exactly what has been lost.


3. Use your Network Managers Backup -


If you network manager has a more recent backup of uncorrupted data, you may wish to have this data (called PFM5.MDB) restored instead.




Run time error 3464


Run Time Error 3464 may appear when you try to run various reports in Private Funds Manager.   Error 3464 is a data type mismatch which means that there is some necessary piece of information missing from a transaction.  This piece of information is sometimes the date, sometimes the shortcode.  It is very unusual for the system to proceed without these items of information, but occasionally a transaction is saved like this.  First of all, make sure you are on the latest version of PFM - version 7 - as this can often 'self heal' a RTE 3464. 


If the error persists, you will need to send your data to Istek for correction.  The best solution is to go into PFM and up to FILE -  REPORT A PROBLEM - SEND - SEND.  If you do not use Outlook, or an error comes up indicating your program has not been properly installed, use the following alternative solution.  Go into PFM and up to FILE - MAKE PFM5.FFT.  Then go to FILE - WHERE AM I? and note the folder.  Now close PFM, go into your email system and write an email to  Use the option to attach a file, browse to the folder noted in WHERE AM I? and locate the file called PFM5.FFT.  Attach this file and send it support, with a note explaining your problem.




Run time error 390



Run Time Error 300 missing component indicates that the workstation you are running PFM from has not had a Client Install performed. 


Please go back to your original CD and use the 'Additional Installs' option from the main menu.


If you do not have a CD, please go to TRAINING and UPGRADES tab above, and choose Workstation Install.





Run time error 380


There are vaious causes of the RTE 380.  If you are in RECEIPTS, Run Time Error 380 Invalid Property can occur when you are trying to print receipts to a receipt printer, but have not ticked the POS option.


Go to Transaction Entry - Receipts - tick POS at bottom left of screen.


When downloading Internet Payments, it can indicate that the folder holding the Internet payments has other files in it, which is confusing PFM.   Open the Unprocessed Internet Payments folder (using My Computer) and delete all other files from the folder.  Then try the import again.




Run time error 3163


This error indicates that you have exceeded the field size for either a data entry field or a reporting field,  You could try reducing you account names, but often it is the combination of say a long pupil name + a long short code + a long account name that is causing this.   The quickest and easiest option, is to call Istek Support who can talk you through extending the field size.




Backups will not view or restore



This usually indicates the installation has been moved, To correct -



  • Go into PFM and Period End - Archives - Backup - click on Restore Default then create a backup called NEWLOCATION


  • Go up to File - Where Am I? and note the folder.  Now CLOSE PFM.


  • Using My Computer, navigate to the folder noted above. Find the file called Archivelst.mdb and double click to open


  • Double click the table called Archives


  • Locate the backup called NEWLOCATION - in the second column is the path.  Highlight and copy (Right click - Copy)


  • Now go to the second column for every other backup and Paste down the path (Right click - Paste)


  • When complete use the X to close and the X to close completely.


  • Run PFM and you should now be able to view/restore.





bottom of page