Frequently Asked
Questions
Find Solutions to Common Issues Related to errors-feedbacks-bugs - rte company database
What steps can I take to get voucher generation working when it fails with errors in BUSY?
If you are facing any problem while creating a voucher then please follow given steps :
Step 1: Open BUSY Software
Step 2: Go to Comapny Menu
Step 3: Click on Backup data
Step 4: Select the company and then mention username and password
Step 5: Specify path for taking backup then select Single or All Financial year then click on Ok button, it will take few seconds to take backup
Step 6: After successful backup, Click on Open company
Step 7: Select the comapny and mention login username and password
Step 8: Go to Housekeeping Menu
Step 9: Click on Reinedex database
Step 10: You Can select the 2 option i.e You can proceed as i have latest backup then click on Ok Button
Step 11: you will get a popup window I.e Proceeding to reindex Database for the Company then Click on Ok Button
Step 12: you will get a confirmation message of Successful Reindex Database
RTE 3001 at company opening or at voucher saving.
If you are facing RTE 3001 at company opening then follow these steps:
Step 1: Take the latest backup of your data.
Step 2: Open BUSY then click on company menu
Step 3: Click on reindex data base and complete the process.
Step 4: If you found the same issue after run reindex database then send you data on support@busy.in mail with necessary details like BUSY serial number, contact name, contact number, query and company login credentials.
If you are facing RTE 3001 at voucher saving then follow these steps:
Step 1: Take the backup of your data base.
Step 2: Step 2: Open the company then go to housekeeping section.
Step 3: Choose the rewrite books option then select the option you can proceed as i have the latest backup and click on Ok.
Step 4: If you found the same issue after run rewrite books then send you data on support@busy.in mail with necessary details like BUSY serial number, contact name, contact number, query and company login credentials.
The company data is not opening and shows an error. Is there a problem with the database due to junk characters?
Yes, Junk characters can cause database errors while opening company data.
If your company is not opening and showing error, you can follow these steps to resolve the issue:
Step 1: First take tha latest backup of your company.
Step 2: Go to Housekeeping menu and select the Reindex Databases option.
Step 3: Run the process and check the issue is resovle or not. If issue is not resolve, Remove the junk characters and Incomplete vouchers and try again.
Step 4: Run BUSY in administrator mode. Set compatibility, down UAC, change region setting UK and US, and give everyone rights to BUSY.
Step 5: Ensure you are using latest BUSY update. If not, Update your BUSY in latest version.
Step 6: If the issue persists, contact customer support for further assistance.
Note : Ensure you have latest backup before performing any housekeeping option in BUSY. and you have upgrade your BUSY in latest version. You should also take a daily backup to prevent any data loss.
What are the basic steps to be followed if something is not working in BUSY
If you are facing a problem in working in BUSY then please follow the given steps:
Step 1: Open the BUSY Software
Step 2: Go to Company Menu
Step 3: Click on Backup data
Step 4: Select the Company in which you are facing problem
Step 5: Specify the location for taking backup
Step 6: After successful backup, Close the BUSY
Step 7: Again open BUSY Software, Go to Company Menu
Step 8: Click on Reindex Database Option
Step 9: Select the Company in which you are facing problem
Step 10: you will get 2 option
Step 11: You Can select the 2 opton i.e You can proceed as i have latest backup then click on Ok Button
Step 11: you will get a popup window I.e Proceeding to reindex Database for the Company then Click on Ok Button
Step 12: you will get a confirmation message of Successful Reindex Database
How to solve the RTE 339 program has performed an illegal operation & will be shut down at the time of taking backup.
To resolve the RTE 339 program has performed an illegal operation & will be shut down at the time of taking backup follow below steps:
Step 1: Take a latest backup of the data.
Step 2: Then open company and go to housekeeping menu option.
Step 3: Then select reindex database option and after completion of the process again check by taking backup.
Step 4: Close all BUSY tabs and right click on BUSY icon then select properties option.
Step 5: Then mark tick on run this program in compatability mode and do the same configuration for user also.
Step 6: Then click on apply and ok button.
Step 7: Then navigate to the window tab and type UAC or user account control and drag down it.
Step 8: After that Go to control panel option and make sure to select time zone as IST indian standard time zone
Step 9: Then select region and locale as english united kingdom .
Step 10: Then restart the system again.
Runtime Error ‘3051’ The Microsoft jet database can’t open the file NEPALIDATE.BDS, it is exclusively opened by another user, or you need permission to view its data
Check File Permissions Ensure that the folder where the Access database file .bdsis located has appropriate read/write permissions for all users who need access to the database. If the file is on a network drive, make sure that all users have appropriate network access rights.
If error message show Runtime Error ‘3051’ The Microsoft jet database can’t open the file NEPALIDATE.BDS, it is exclusively opened by another user, or you need permission to view its data follow the below steps:
Step 1: Check if the Database is Opened by Another User: Ensure that no other user or application has the Access database file open exclusively. If another user is accessing the database, ask them to close it or use a shared access mode.
Step 2: Check File Permissions: Verify that the current user has the necessary permissions to access and modify the database file. Make sure that the user has read and write permissions to the folder containing the database.
I tried to reindex and backup my BUSY data but I am still having issues showing runtime RTE What else can I try?
If you have tried to reindex but your BUSY data is showing RTE 3343, you can follow these steps to resolve the issue:
Step 1: Go to Housekeeping menu and Remove the junk characters and Incomplete vouchers.
Step 2: Run the process and check the issue is resovle or not.
Step 3: Ensure no any lockes file is created in COMP000x folder. If they are, delete all lockes files and check issue resolve or not.
Step 4: Run BUSY in administrator mode. Set compatibility, down UAC, change region setting UK and US, and give everyone rights to BUSY.
Step 5: Ensure you are using latest BUSY update. If not, Update your BUSY in latest version.
Step 6: If the issue persists, contact customer support for further assistance.
Note : Ensure you have latest backup before performing any housekeeping option in BUSY. and you have upgrade your BUSY in latest version. You sould also take daily basis backup for any data loss.
Runtime Error ‘6’ while printing of document
Runtime Error 6, also known as "Overflow" error, typically occurs in programming languages VB. This error indicates that a numeric variable or expression exceeds its allowable range. In the context of printing a document, this error might be caused by an issue with data types or calculations related to printing.
Step 1: The Oloron font has become corrupted and requires replacement with a new, error-free version. performance and Uninstall the Corrupted Font: Before installing the new font, it's a good practice to uninstall the corrupted font to avoid potential conflicts. You can do this through your operating system's font management tools. Install the New Font: For Windows Right-click on the font file (typically with a .ttf or .otf extension) and select "Install" from the context menu. This will add the font to your system's font library.
Step 2: In the printer configuration, you have the option to choose a different font for the printing style, apart from Oloron.
Runtime Error ‘70’, Permission denied while restoring backup
Runtime Error 70, "Permission Denied," during a backup restoration process typically indicates that the application or process attempting to restore the backup doesn't have the necessary permissions to access or modify certain files or directories. To resolve this issue, follow these steps:
If error message show Runtime Error ‘70’, Permission denied while restoring backup follow the below steps
Step 1: Check File and Folder Permissions: Ensure that the target directory where the backup is being restored and any associated files have the appropriate permissions for the user or application. Make sure the user has both read and write permissions to the directory.
Step 2: Temporarily disable or configure any antivirus or security software that might be interfering with the backup restoration process. Some security software can block file access and modification.
Step 3 : User Account Control (UAC): If you're using Windows, User Account Control (UAC) might be causing permission issues.Temporarily disabling UAC or adjusting its settings could help.
Runtime Error ‘440’, Automation error
VB Runtime Error '440', also known as "Automation error," is a generic error that occurs when there is an issue with accessing Automation objects in Visual Basic (VB) code. Automation objects are components or applications that can be controlled programmatically, such as COM objects or ActiveX controls. To resolve this error, you can take the following steps:
Step 1: Update or Reinstall the Component: If the error is related to a specific third-party component or ActiveX control, consider updating or reinstalling the component to ensure that you have installed BUSY with the latest version and in a different folder and that it is properly registered.
Step 2: Check for Version Compatibility: If the Automation object is created with a different version of the component than the one used in your VB project, ensure that they are compatible. If there is a version-related issue causing Automation errors, consider updating the relevant Windows components to resolve the compatibility problem.
