Frequently Asked
Questions
Find Solutions to Common Issues Related to errors-feedbacks-bugs - rte company database
Runtime Error ‘48’, Problem in loading Dll while opening BUSY
Runtime Error 48, "Problem in loading DLL," usually occurs when there is an issue with a dynamic-link library (DLL) that the application is trying to load during its execution. To resolve this error, you can try the following steps
Step 1: Run as Administrator: Make sure the application requires administrative privileges to load the DLL, try running the application as an administrator.
Step 2: Update Windows and Drivers: Ensure that your Windows operating system and drivers are up-to-date. Outdated software may cause conflicts and lead to DLL-related errors.
Step 3: you need to attempt to resolve it by running the 'Rewrite Book'. After logging in to the company, navigate to 'Housekeeping' and select 'Rewrite Book.' This action may help solve the problem.
Step 4: If the issue continues to persist after Step 3, you are required to send the data to us at support@busy.in for further assistance.
Runtime Error ‘53’, File Not found
The Runtime Error '53', "File Not Found" typically occurs in Visual Basic when a specific file or reference that the code is trying to access is missing or cannot be found. This error can happen when the code attempts to open a file, load a dynamic link library (DLL), or reference an external file that is not present in the specified location If error message show Runtime Error ‘53’, File Not found follow the below steps:
Step 1: If the error mentions a specific file name, verify for missing or unregistered DLLs. In such instances, it may be necessary to re-register the DLLs or reinstall the BUSY Software again.
Step 2: If the problem still persists, then we need to upgrade the BUSY software with the latest version. The latest version may include bug fixes and enhancements that can address the issue you are facing.
Run Time Error ‘3079’ The search key was not found in any record.
Run-time error 3079 in Microsoft Access typically occurs when you're attempting to perform an operation that involves searching for a specific record based on a search key, but the key cannot be found in any of the records in the specified table. This error message is informing you that the search criteria you provided did not match any existing records in the table.
If error message show Run Time Error ‘3079’ The search key was not found in any record follow the below steps:
Step 1: This error arises when the report data is displayed on one system, and records are subsequently deleted from another
system. Upon attempting to refresh the data, the search key becomes unavailable for the search, resulting in this issue.
Step 2: if it comes oftenly then need to send the data to us at support@busy.in for further assistance.
Runtime Error ‘339’, Program has performed an illegal operation & will be shut down
Runtime Error '339' often occurs when a required component or file is missing, not registered, or outdated in a Windows application. This error message may also state that the program has performed an illegal operation and will be shut down. To resolve this issue, follow these steps:
If error message show Runtime Error ‘339’, Program has performed an illegal operation & will be shut down follow the below steps:
Step 1: System File Checker (SFC): Run the System File Checker tool to scan and repair corrupted system files. Open Command Prompt as an administrator and run: SFC /scan now
Step 2: Duplicate the data file to an alternative location and verify if the copying process is successful. If the duplication is successful, it suggests data is corrupted; however, if copying encounters issues, it may indicate potential bad sectors on the hard drive.
What should I do if I can't perform specific tasks in BUSY?
If you find that you are unable to perform specific tasks in BUSY, you can take a series of troubleshooting steps to identify and resolve the issue. Here's a step-by-step guide on what to do:
Step 1 : Verify that you have the necessary user permissions to perform the task in question.
Step 2 : Consult the user manual, help documentation, or user guides provided by BUSY
Step 3 :If you encounter error messages while attempting the task, take note of the error message and any error codes provided.
Step 4 : Ensure that your computer has a stable and active internet connection, especially if the task involves online features or cloud-based functionality.
Step 5 : If you have followed the above steps and still cannot perform the task, consider reaching out to BUSY's customer support for assistance.
Tracking invoices and expenses in BUSY steps to achieve this.
If you find that you are unable to perform specific tasks in BUSY, you can take a series of troubleshooting steps to identify and resolve the issue. Here's a step-by-step guide on what to do:
Step 1 : Verify that you have the necessary user permissions to perform the task in question.
Step 2 : Consult the user manual, help documentation, or user guides provided by BUSY
Step 3 :If you encounter error messages while attempting the task, take note of the error message and any error codes provided.
Step 4 : Ensure that your computer has a stable and active internet connection, especially if the task involves online features or cloud-based functionality.
Step 5 : If you have followed the above steps and still cannot perform the task, consider reaching out to BUSY's customer support for assistance.
How can I troubleshoot the RTE-430 error that occurs while opening BUSY?
To troubleshoot the RTE-430 error that occurs while opening BUSY, follow these steps:
1. VeriFinancial Year System Requirements:
2. Ensure that you are using the latest version of BUSY. Updates often include bug fixes and compatibility improvements.
3. Try running BUSY in compatibility mode. Right-click on the BUSY executable, go to Properties and navigate to the Compatibility tab.
4. Attempt running BUSY with administrator privileges. Right-click on the BUSY executable and select Run as administrator.
5. Uninstall BUSY, then reinstall the latest version.
6. Check system logs or event viewer for any specific error messages related to the RTE-430 issue.
7. If the issue persists, contact BUSY support.
8. VeriFinancial Year that no third-party software interfering with BUSY.
9. Temporarily disable antivirus or security software to see if it has any impact.
10. Test on Another System:
I'm getting an error message RTE OR I don't understand. What should I do?
If you are getting an Error like RTE 5 OR 3343 So you need to follow some steps and those are -
Step 1: Take Backup of Your Data From Company menu
Step 2: After Take Backup of Your Data Go to Company menu and click on Reindex Data and reindex all FY One by one and Most Probabily It will be Resolve.
Note: If You face error during Reindex Processing Then You need to send Data Backup at our end to show the Research and Devlopment Deparment on mail id Support@busy.in With all Your details like Your Name ,contact no., license no. company user name and password, organisation name mail id and Screen shot of the error.We will revert you Within 24-48 Hours in working days
BUSY crashed unexpectedly while I was working on a report. What could have caused this crash and how can I recover my work?
To troubleshoot and fix BUSY crashed unexpectedly while I was working on a report. The cause of BUSY crashing unexpectedly can be due to various reasons such as hardware issues, software conflicts, or corrupt data.
Step 1: Take Backup.
Step 2: Open BUSY Go to Company Menu option
Step 3: Click on Reindex Databases and select company which you are facing issue of crashing.
Step 4: Continue to run reindex.
Step 5: Check & verify same report after re-indexing. Check the specific report you were working on to see if the crash is resolved.
Step 6: Check BUSY latest version and Release.
Step 7: If the problem persists even after re-indexing and updating, contact BUSY support by sending the data backup to support@busy.in for further analysis and repair.
I am getting error while uploading files from BUSY to GST portal. How to resolve?
There are the solutions of E-return file are not getting uploaded from BUSY to GST portal :
1. Sales Voucher Number cannot be start with zero
2. Sales Voucher Number cannot be more than 16 characters
3. HSN code should be Numeric and as per Aggregate Anual Turnover.
4. If the HSN code belongs to service then in item master you need to select tag category as service gst rate.
5. GST number should be Active and correct
6. mention correct state in account masters.
7. Check bill sundries accounts taggings.
If still having same issue then you can contact us on our centerlized 24*7helpline
number i.e. 8282828282 or 011-40964096.
You can also share your query on support@busy.in
