Frequently Asked
Questions
Find Solutions to Common Issues Related to troubleshoot - demo mode
The client system going into Demo mode in BUSY. what should I do?
If you are experiencing issues with your client system going into demo mode while using an SQL database, you can follow these steps to resolve the issue:
Posibility1: If you are using an SQL database through VAN mode and the client system is going into demo mode, follow these steps:...
What steps should I take if my BUSY license is not being detected?
If your BUSY license not detected and running in demo mode, you can try these troubleshooting steps to fix it:
For Server system:
Step 1: Revalidate soflock license under the License Management.
Step 2: Reinsert dongle in other port and check.( In case of dongle).
Step 3: Ensure the you have selected correct model.
Step 4: Make sure correct version install according to the license.
For Client system:
Step 1: Make sure the data directory on the client system is the same as the data directory on the server system.
Step 2: Check connectivity between server and client either it is LAN or WIFI.
Step 3: Check the server IP pinging time on client system by mention
"ping (IP Address) -t" in run command, it should be 1 ms.
Step 4: Check can able to access data folder under the network tab.
Step 5: Check your antivirus or firewall settings and make sure they are not blocking BUSY Application from accessing the network or other resources.
Step 6: If the server and the client are on different locations, make sure the required port is open on the internet router.
Want to open specific data in client system
This issue comes when customers want to maintain GST or Without GST billing data in BUSY. However, we can maintain different data directories for different companies. This can be done through two options
Creating shortcut and specify data path in server and client system.
Through BUSY agent
To open specific data in client system follow the below steps:
1) Creating shortcuts and specifying data paths in server and client systems.
Step 1: Create a new shortcut of BUSY and after the .exe command, write PATH= D/BUSYwin/Data (or where your data is stored).
Step 2: Share the data folder to everyone.
Step 3 : Create a new shortcut of BUSY in the client system also.
Step 4 : Open BUSY at server system and then in Client
NOTE : This data directory will access until the shortcut is open on the server.
2) Through BUSY agent
Step 1: Install BUSY agent utility on server system.
Step 2 : Enter general configuration such as data directory.
Step 3 : Click on option additional data path and specify path of data folder.
Step 4: Share data folder for client system.
Step5 : Specify the data directory in the client system and reopen BUSY.
How can I restore access to my BUSY license? It is currently showing as not found.
If your BUSY is running in demo mode, you can try these troubleshooting steps to fix it:
For Server system:
Step 1: Revalidate soflock license under the License Management.
Step 2: Reinsert dongle in other port and check.( In case of dongle).
Step 3: Ensure the you have selected correct model.
Step 4: Make sure correct version install according to the license.
For Client system:
Step 1: Make sure the data directory on the client system is the same as the data directory on the server system.
Step 2: Check connectivity between server and client either it is LAN or WIFI.
Step 3: Check the server IP pinging time on client system by mention
"ping (IP Address) -t" in run command, it should be 1 ms.
Step 4: Check can able to access data folder under the network tab.
Step 5: Check your antivirus or firewall settings and make sure they are not blocking BUSY Application from accessing the network or other resources.
Step 6: If the server and the client are on different locations, make sure the required port is open on the internet router.
Resolve license not found issue in BUSY.
If your BUSY is running in demo mode, you can try these troubleshooting steps to fix it:
For Server system:
Step 1: Revalidate soflock license under the License Management.
Step 2: Reinsert dongle in other port and check.( In case of dongle).
Step 3: Ensure the you have selected correct model.
Step 4: Make sure correct version install according to the license.
For Client system:
Step 1: Make sure the data directory on the client system is the same as the data directory on the server system.
Step 2: Check connectivity between server and client either it is LAN or WIFI.
Step 3: Check the server IP pinging time on client system by mention
"ping (IP Address) -t" in run command, it should be 1 ms.
Step 4: Check can able to access data folder under the network tab.
Step 5: Check your antivirus or firewall settings and make sure they are not blocking BUSY Application from accessing the network or other resources.
Step 6: If the server and the client are on different locations, make sure the required port is open on the internet router.
I am unable to generate invoices in BUSY. It shows error message BUSY run in "Demo Mode". How can I resolve this?
The BUSY run in Demo Mode issue. Users encountering this problem can follow these steps to identify and address potential causes.
1. Check License File: Verify the presence of the license file in the BUSYWin folder.
2. BLS Expiry: If the BLS has expired and the audit trial feature is in use, generating vouchers in BUSY is restricted. Consider renewing the BLS.
3. Softlock License Validation: Confirm that the softlock license file has been validated. If not, this validation failure may lead to the software running in demo mode.
4. Check BUSY Model: Ensure that the selected BUSY model aligns with the purchased license. Choosing the correct model is crucial for proper functionality.
5. Dongle Connection: If a dongle is used, check whether it is properly connected. A disconnected or malfunctioning dongle can lead to demo mode issues.
6. Contact Customer Support: If the problem persists despite the above steps, reaching out to BUSY customer support is recommended. They can provide specialized assistance and address any specific issues with your license or software configuration.
The client system is not connecting to the server system. How can I troubleshoot this?
To fix the issue in connecting the client system to server system, please follow these steps:
Step 1: Make sure the data directory on the client system is the same as the data directory on the server system.
Step 2: Check connectivity between server and client either it is LAN or WIFI.
Step 3: Check the server IP pinging time on client system by mention
"ping (IP Address) -t" in run command, it should be 1 ms.
Step 4: Check can able to access data folder under the network tab.
Step 5: Check your antivirus or firewall settings and make sure they are not blocking BUSY Application from accessing the network or other resources.
Step 6: If the server and the client are on different locations, make sure the required port is open on the internet router.
If same issue persists you can reach out to us on our 24X7 helpline number: 8282828282 or 011 40964096. You can also email us your query at [support@busy.in].
How do I troubleshoot connectivity issues to connect a client system with the BUSY Server system.
To troubleshoot connectivity issues of the client system with the BUSY Server system, you can follow these steps:
1. Verify that you have entered the correct data path in your client system. Data path should be the same as the server system by networking.
2. BUSY should be open in the server system first then the client system. And reopen BUSY in your client system after entering the correct data path in the client.
3. Check BUSY model should be the same in server and client system.
4. Check Release is also same in both systems. If not, update the latest release in both systems after taking the latest backup.
5. Server and Client systems should be connected with the same LAN connectivity in case of access database.
6. Disable any firewall or antivirus software temporarily to see if they are blocking the connection.
7. Contact your network administrator or IT support to check if there are any network restrictions or issues.
8. If the problem persists, reach out to BUSY support for further assistance.
Unable to login client system's software showing SQL access denied
Check out the possibilities below:
1: Server Info is correct according to main server
2: Check after restart SQL services on main server and reopen BUSY on client system
3: Check that dongle server/ BUSY agent with dongle sercurity configuration running in main system startup if not then open dongle server from BUSYwin folder and enter the server info. then click on start and then click on add to startup and then check
4: Check TCP/IP is enable from Sql server manager then you have to enable & then start the services and check
5: Create inbound and outbound firewall rules from control panel
6: check ping process on client system search run on start search window and then type ping space then type main server IP4 address and then -t and then search. If ping process showing request timed out then you have to contact to your IT person and configure it
I am facing an error in logging in through the second system in double user setup. How can I resolve this?
If you are facing an error logging in through the second system in a double-user setup, you can follow these steps to resolve this issue:
Step 1: Try restarting your second software.
Step 2: Close BUSY on both systems. First, start the main server, and then start your second system.
Step 3: Ensure you have entered the correct path of the main server through networking in the data directory.
Step 4: Make sure you have a stable internet connection. Ensure you have the latest version of the software.
Step 5: Ensure your LAN cable is connected properly.
Step 6: Check your ping. It should be proper.
Step 7: Make sure antivirus and Windows Firewall are not restricting BUSY. If they are, allow BUSY in both programs.
Step 8: If the issue persists, contact customer support for further assistance.
Note: If your ping is not proper or there is a problem with the LAN cable and internet, contact your IT person.
