Exception 24 not trapped; Does not understand: isbvapppane

We have 2 users who are frequently getting the same error below.

Exception 24 not trapped;
an instance of the class bctabctrl (object reference: random numbers)
Does not understand: isbvapppane

They say it happens at random, 2-3 times a day and can never duplicate it. We're currently on version 2015 - 7.74, which is on a remote server that everyone logs into to run BusinessVision. It's always these 2 users, which doesnt make any sense considering they're all using the same system.

If anyone has any suggestion on getting rid of these error, I'm all ears. 

  • 0

    Hello EricW

    The following is a list of possibilites to resolve random exception 24s

    1. Have your network and computer hardware verified to ensure that it is working correctly. Ensure that your network adapters are configured to operate at the correct speed of your network. Contact your network administrator or Business Partner for assistance.

    2. Configure a Pervasive gateway for data and Workbook folders. See knowledgebase article: Understanding Gateways and the Pervasive Workgroup engine.

    3.  Delete files not required in data folder. See knowledgebase article: What files can be deleted from version 7 data folder?.

    4. Disable network and workstation power saving features.

    5. Ensure that the same version of BusinessVision is installed on each workstation.

    6. Upgrade to the current version of BusinessVision.

    Ensure that the same version of Pervasive is installed on each workstation and the server.

    7. Use the Pervasive System Analyzer to remove components old components of Pervasive.

    8. Confirm that Wbtrv32.dll and Wbtrcall.dll files are found only in the C:\Pvsw\Bin folder. Delete if found in other locations on the hard disk drive.

    9. Create new user ID.

    10. Replace the Users.btr and Userslv.btr files from a newco set of data.

    11. Reorganize files related to the module that receives the error. Click File, and then click Reorganize Files. Backup your data first.

    12. Reboot the workstation and the server to clear memory.

    Use Windows System Configuration Utility (Msconfig.exe) to disable non-required programs running in the background.

    13. Reduce the size of history files.  

    14. Use a virus checker with the latest definitions to confirm that the computer is not infected with the Crypt.FKM.Gen virus. If the virus is found, remove the virus using recommended procedures.

    14. Configure the virus checker to not scan *.btr and *.fil data files.

  • 0 in reply to Hueman

    Hi Hueman,

    Thanks for the quick response. I've gone through a few of these already but there's some questions I have for others.

    8. I can locate the Wbtrv32.dll file in the \bin folder,  but the wbtrcall.dll file is nowhere to be found

    13. Where/how would I reduce the history files?

  • 0 in reply to EricW

    Hello EricW

    For question 13 this resolution to the KB article ID:20536 will suffice:

    Use the Reorganize option in System Setup to purge sales and purchase history.

    Purge Sales History

    Click Utilities, System Manager, System Setup.

    Click Sales order.

    Click Sales order history.

    Example, if you want to retain a minimum of 24 months of history you would set the Months retained box to 24.

    Click Reorganize.

    Once the reorganize is finished, set the Months retained box to 36.

    In one years time you will prompted with a history warning. The above procedure can be repeated to remove an additional year of sales history.

    Purge Purchase History

    Click Utilities, System Manager, System Setup.

    Click Purchase order.

    Click Purchase order history.

    Example, if you want to retain a minimum of 24 months of history you would set the Months retained box to 24.

    Click Reorganize.

    Once the reorganize is finished, set the Months retained box to 36.

    In one years time you will prompted with a history warning. The above procedure can be repeated to remove an additional year of purchase history.

    As for the question 8 if the file is not present then you can eliminate that step.

  • 0 in reply to Hueman

    I dont understand why it's only affecting one user. Everyone is remoting into the same server, so performance and resources shouldn't be an issue. If it's a history issue, wouldnt everyone be affected the same way?

    We've completely recreated her profile and she still suffers the exact same error.

  • 0 in reply to EricW

    Even recreated her user on the server and she almost instantly crashed... I hate BV.