Resolving Tally Export Error 10061 in Tick Software (Crystal Reports + SQL Server via ODBC)
Many legacy business applications—especially those built on VB6, Crystal Reports, and SQL Server—integrate with Tally Prime for accounting automation. A comm...
Many legacy business applications—especially those built on VB6, Crystal Reports, and SQL Server—integrate with Tally Prime for accounting automation. A common issue faced during this integration is:
“Tally is not running. Error no: 10061”
Even when Tally is open and functioning correctly, exports fail. This article provides a deep technical explanation of the issue, its root causes, and practical solutions.
Understanding Error 10061
Error 10061 = Connection Refused
This is a network-level socket error, meaning:
- The client (Tick software) attempted to connect
- But the server (Tally) refused the connection
Why This Happens
- Tally is not listening on the expected port
- Port mismatch between Tick and Tally
- Firewall blocking communication
- Hardcoded port in legacy application
Architecture Overview
Understanding the integration flow is critical:
Tick Software → Crystal Reports → SQL Server (ODBC)
↓
Tally (HTTP/XML API)Key Point
- ODBC is used only for SQL Server
- Tally uses HTTP/XML over a specific port (default: 9000)
? These are two completely separate communication layers
How Tally Integration Works
Tally exposes an API via:
- HTTP Server
- XML Requests
Default Configuration in Tally
| Setting | Value |
|---|---|
| Port | 9000 |
| HTTP Server | Enabled |
| ODBC Server | Enabled |
Root Cause in Real Scenarios
In most cases:
- Tally port changed from 9000 → 9049
Tick software still tries:
http://localhost:9000Result:
Error 10061 (Connection Refused)
Step-by-Step Troubleshooting
1. Verify Tally Configuration
In Tally:
- Press
F1 → Settings → Advanced Configuration - Ensure:
- Enable HTTP Server = Yes
- Enable ODBC Server = Yes
- Port = 9000 (recommended)
Restart Tally after changes.
2. Test Tally Port Availability
Open browser:
http://localhost:9000Expected Result:
- Blank page or XML response → ✅ Working
If Failed:
- Tally not listening on port
- Wrong configuration
3. Check Tick Software Configuration
Look for:
- Settings panel
.inior.configfiles- Registry entries
Update:
localhost:9000 → localhost:90494. Legacy Application Limitation
Many older systems (VB6-based) have:
Hardcoded:
http://localhost:9000
? No option to change port
Solutions
✅ Solution 1: Use Default Port (Recommended)
Set Tally back to:
Port = 9000✔ No code changes
✔ Works instantly
✔ Most stable
✅ Solution 2: Modify Application Configuration
If supported:
- Update port in config files
- Restart application
✅ Solution 3: Windows Port Forwarding (Advanced)
If Tick cannot be modified:
Run Command Prompt as Administrator:
netsh interface portproxy add v4tov4 listenport=9000 listenaddress=127.0.0.1 connectport=9049 connectaddress=127.0.0.1How It Works
| Request | Action |
| Tick → 9000 | Redirected |
| Windows → 9049 | Sent to Tally |
✅ Solution 4: Firewall Configuration
Allow port in Windows Firewall:
- Open Windows Defender Firewall
- Add Inbound Rule
- Allow port:
9000or9049
Common Mistakes
❌ Trying to set Tally port in SQL Server
❌ Modifying ODBC DSN for Tally connection
❌ Assuming Tally uses database connection
❌ Ignoring HTTP server settings
Best Practices
✔ Always use default port 9000 unless required
✔ Document integration architecture
✔ Avoid changing ports in production
✔ Use consistent environment across servers
✔ Monitor firewall and antivirus rules
Real-World Case Insight
In most deployments:
- Tick (VB6 + Crystal Reports) uses fixed port 9000
- Changing Tally port breaks integration
- Reverting port resolves issue instantly
Conclusion
The Error 10061 in Tally export scenarios is primarily a port mismatch issue, not a failure of Tally itself.
Final Recommendation:
? Always align Tick and Tally ports
? Prefer keeping Tally on port 9000
This ensures seamless communication and avoids unnecessary complexity in legacy systems.
#tally #tallyprime #tallyerp #odbc #sqlserver #crystalreports #vb6 #accountingsoftware #erp #softwareintegration #api #xml #http #networkerror #windowsserver #firewall #portforwarding #netsh #database #export #import #troubleshooting #itservices #techsupport #enterprise #automation #businesssoftware #integration #server #networking #connectionerror #socketerror #port9000 #tallyerror #dataintegration #legacysoftware #vb6apps #crystalreporting #sqlintegration #tallyapi #xmlapi #softwareerror #debugging #itadmin #sysadmin #windows #serverissue #technicalguide #howto #solution
Was this guide useful?
Your answer helps us keep BISONKB accurate and practical.