Home › BUSY Guides › BUSY 'Unable to Connect to Server' and SQL Login Failed: Fixes
BUSY 'Unable to Connect to Server' and SQL Login Failed: Fixes
BUSY: सर्वर से कनेक्ट नहीं हो रहा / SQL लॉगिन फेल
BUSY client cannot connect to the SQL server or shows login failed? BUSY's checklist: server name, BUSY Agent, port 1433, firewall, UAC and SA password.
Checklist
- Server name / IP on the client is correct
- BUSY Agent is running on the server and starts with Windows
- Dongle server configuration is enabled
- Server and client are on the same network
- SQL TCP port 1433 enabled and allowed in the firewall
- UAC lowered as BUSY's help suggests
Login failed
Check the server name, user and password saved in BUSY's server settings; if the SA password is wrong or locked, reset it in SQL Server Management Studio and restart the SQL service.
Setting up a new network? Read BUSY multi-user LAN setup.
Menu names as given in BUSY's own help on busy.in; they can differ slightly by BUSY version, plan and configuration. Take a backup before changing settings.
Need it done for you?
Our team sets this up remotely over UltraViewer, usually the same day. Call or message us, or see BUSY services.
Updated 2026-10-27 · Bharat Busy Care, Authorised BUSY Platinum Partner, Sri Ganganagar
FAQ
Why can't my BUSY client connect to the server?
Usually BUSY Agent is not running, port 1433 is blocked, or the server name on the client is wrong.
Can you fix it remotely?
Yes, over UltraViewer.
Talk to a BUSY expert
Call or message us; we answer in Hindi or English.