Frequently Asked Questions

please follow these steps if you forgot your SQL server name and password in BUSY: 
Step 1: First of all check in which drive is your BUSY is installed
Step 2: Suppose if BUSY is installed in C drive and in BUSYwin folder 
Step 3: Then open the BUSYwin folder 
Step 4: Click on system folder
Step 5: Then click on server 
Step 6: This file is in text format and you can check your sql server name and password from it

If any error coming during synchronization data between HO and BO, please follow the given steps
 Step 1 Go on administration in BO
 Step 2 Click on configuration
 Step 3 Click on feature options 
 Step 4 Enterprise features
 Step 5 Enable HO BO data sync. options
 Step 6 Select here branch and click on configuration
 Step 7 Click on check connection, it should be successful
 Step 8 Further if any issue coming then contact to our customer support team

If count show in demo mode check these steps:
1. Reopen BUSY on both system first on server then on count(client)
2. Check set server information on count system 
3. Check dongle server information in dongle server app or in BUSY agent app 
4. Create Inbound and outbound rule and restart sql services then check 
5. Check BUSY model mention correct or not for sql must use SC or EC
6. Check Tcp ip configuration in ipv 4 and in ipv all

To restart service in SQL follow the steps below:
Step 1: Go to search bar option in system then search SQL configuration manager 
Step 2: Now select SQL server services 
Step 3: Go to SQL server with server name then right click on it 
Step 4: Click on restart option 
Note: Make sure BUSY is closed before restart service of SQL
Step 5: Now go to client system
Step 6: Select server information option and check server name password is correct 

If the server name is not showing up on the drop-down list when trying to connect through SSMS in BUSY below are the steps to follow:-
Step 1: You can try entering the server name manually in the server name field. 
Step 2: You can also click on server name option then click on browse for more option then click on Database option if your server name is showing there so select it then click on ok button.

If the client PC is in Demo Mode in SQL, follow these steps
Open SQL Configuration Manager and restart SQL services.
Go to Control Panel, click on User Account, change account type to Never ModiFinancial Year Mode.
Temporarily disable antivirus and firewall, and add SQL Port 1433 in the firewall.
Open SQL Configuration and check TCP 4 port.
Go to Networking Sharing and fix the LAN IP.
Following these steps should help resolve the Demo Mode issue in SQL on the client PC.

SQL installation depends on compatabilty with window in system If your using Window 10 then 2019 version of SQL will not support you can install SQL 2016 or 2017.Even it depends on an user from which you have logged in your system you can install it with current user or your admin user and also can add user administration during installation .Even make sure that if SQL is already installed in system then instance should be different.

If SQL services are not starting, follow these steps:
Step1 Check Error Logs:
Step2 VeriFinancial Year Service Account Permissions
Step3 VeriFinancial Year that there is sufficient disk space available on the server
Step4 Try restarting the server where SQL Server is installed.
Step5 Confirm that the SQL Server port is not being used by another application.
Step6 Ensure that dependent services, such as the SQL Server Agent, are also running.
Step7 If all else fails, consider reinstalling or repairing the SQL Server installation

To resolve the problem during SQL installation indicating a requirement for Microsoft .NET Framework 3.5 Service Pack 1 has failed, follow these steps:
1.Open Control Panel on your Windows system.
2.Navigate to All Control Panel Items and select Programs and Features.
3.Choose Turn Windows features on or off.
4.Look for .NET Framework 3.5 in the list and enable the service, then press OK.
5.Restart your computer.
6.Proceed with the SQL installation; it should now be successful.

You cannot find the server folder; you can find the server file, not the folder. To find the folder, you can follow the below steps:
Step 1: Open the file, explore, Go to the drive on which you installed the BUSY. On the drive, you will find the BUSY.win folder.
Step 2: In the BUSYwin folder, select the system folder. In the system folder, you will find the server text file.