Frequently Asked
Questions
Find Solutions to Common Issues Related to errors-feedbacks-bugs - rte company database
Runtime Error ‘Could not update item balance ‘XYZ ITEM 3456’ junk character found at position ‘n’ in name’ while Changing financial year.
This problem arises when non-standard characters are identified within the text of an item master & account master at a specific location. To address this issue, follow the steps outlined below to remove the problematic characters.
If error message show Runtime Error ‘Could not update item balance ‘XYZ ITEM 3456’ junk character found at position ‘n’ in name’ while Changing financial year follow the below steps:
Step 1. : Perform a thorough inspection of the data by accessing the 'Check Junk Character' feature within BUSY Software, accessible
through Open Company → Housekeeping → Check Junk Character. Remove all detected junk characters to ensure a smooth
execution of the desired actions and to preemptively address any potential issues that may arise.
Step 2: After successfully removing the junk characters, attempt to update master balance the data. If the error persists, it is now
necessary to proceed with sending the data of backup to r & d on support@busy.in.
Runtime Error ‘1046’ Cannot read at the time changing financial year
Runtime Error 1046, "Cannot read," typically occurs when there is an issue with reading or accessing data from a variable, object, or data structure in a programming language. To resolve this error, you need to identify the root cause and fix the problem. Here are some steps to help you troubleshoot and resolve Runtime Error 1046
Step 1: Please check the hard disk drive for any bad sectors that may be causing issues while reading data files from those sectors. Bad sectors can lead to data corruption and may affect the performance and reliability of the drive.
Step 2: 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 3: If the issue continues to persist after Step 2, you are required to send the data to us at support@busy.in for further assistance.
Error in Importing table ‘Company Server block to statement with ‘Ad Hoc Distributed Queries’ while importing data from Access to MSSQL.
The error message "Server blocked access to AD HOC Distributed Queries" typically occurs in Microsoft SQL Server when you're trying to execute ad hoc distributed queries. These are queries that involve accessing data from a remote data source, such as another SQL Server instance or a linked server, directly in the query.
To resolve this error and enable the execution of ad hoc distributed queries, you need to configure SQL Server to allow such queries. Here's how you can do it:
Step 1. : Enable Ad Hoc Distributed Queries:
You can use the following SQL command to enable ad hoc distributed queries:
EXEC sp_configure 'show advanced options', 1;
RECONFIGURE with OVERRIDE
Go
to EXEC sp_configure 'Ad Hoc Distributed Queries', 1;
RECONFIGURE with OVERRIDE
GO
Step 2: Restart SQL Server: After making changes to the configuration, it's a good practice to restart the SQL Server service to ensure
that the changes take effect, now problem will get auto-resolved.
Runtime Error ‘9’ Script out of range while Creating company
An 'Script out of range' error is encountered when attempting to create a company in the Access database, often caused by discrepancies in Windows regional settings
If error message show Runtime Error ‘9’ Script out of range while Creating company follow the below steps:
Step 1 : Press the Windows key on your keyboard to open the Start Menu. Type "Control Panel" and press Enter to open the Control Panel.
Step 2: In the Control Panel, click on "Clock and Region" (or "Region" depending on your version of Windows). Click on the "Administrative" tab.
Step 3: Under the "Language for non-Unicode programs" section, click on the "Change system locale" button
Step 4 : Uncheck the "Beta: Use Unicode UTF-8 for worldwide language support" option if it's checked. Click the "OK" button and follow any additional prompts to apply the changes and You may need to restart your computer for the changes to take effect.
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.
