Frequently Asked Questions

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.

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.

If your BUSY is giving runtime 5 while opening the report suddenly, 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.

Runtime Error '3197' occurs in Microsoft Jet Database Engine when two or more users are trying to modify the same data in a database simultaneously. This error is often encountered in multi-user environments where multiple users have access to the same database.The error message "Microsoft Jet Database engine stopped the process because you & another user is changing the data at the same time" indicates that the database engine has detected a data concurrency issue, and to prevent data corruption or conflicts, it stops the process to ensure data integrity. If error message show Runtime Error ‘3197’ Microsoft jet Database engine stopped the process because u & another user is changing the data at the same time follow the below steps: 
Step 1: In the first step, you need to delete the 'lock.sysfile and restart the system.
Step 2: If the problem still persists, then we need to delete the 'compinfo.bds' file from the BUSYwinfolder.

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," 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.

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.

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," 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.

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.