Fix: “Tally is not running. Error no: 10061” While Exporting Data from TICK Production ERP to Tally Prime – Bison Knowledgebase

Fix: “Tally is not running. Error no: 10061” While Exporting Data from TICK Production ERP to Tally Prime

📅 03 Jan 2026 📂 General 👁 24 views

When exporting accounting or inventory data from TICK Production ERP to Tally Prime, users may encounter the error:

“Tally is not running. Error no: 10061”

This error typically appears even when ODBC is enabled and data communication seems operational in Tally. It indicates a connection refusal at the network/service level, not an accounting or data-mapping issue.

This Knowledge Base article explains the root cause, technical background, and step-by-step resolution to reliably restore ERP-to-Tally data export.

Technical Explanation

What Does Error 10061 Mean?

Error 10061 is a standard TCP/IP connection refused error.
In the context of Tally integration, it means:

The ERP attempted to connect to Tally’s listening port
The port was not reachable, blocked, or Tally was not accepting connections
The connection was refused by the OS or firewall

Even if ODBC is enabled, Tally must be actively running and listening on the configured port.

Typical Data Flow (ERP → Tally)


TICK ERP
   |
   |  TCP/IP / ODBC / XML
   v
Tally Prime (Port 9000 or custom)
   |
   v
Company Loaded & Active

If any layer fails, Error 10061 occurs.

Common Use Cases Affected

Exporting:
- Purchase Vouchers
- Material Receipt Notes (MRN)
- Sales / Production Entries
Real-time sync from ERP to Tally
Batch voucher export
Multi-user Tally environments
Tally running on a different PC / Server

Step-by-Step Solution / Implementation

Step 1: Ensure Tally Prime Is ACTUALLY Running

✔ Tally Prime must be:

Open
Not minimized to tray
On the Gateway of Tally screen
A company must be loaded

❌ Opening Tally after clicking “Export” will fail
❌ Opening Tally without loading a company will fail

Step 2: Verify Tally Is Listening on the Correct Port

Default Tally port: 9000

In Tally Prime:

Gateway of Tally
F1 → Settings
Connectivity
Confirm:
- Enable ODBC Server → Yes
- Enable HTTP Server → Yes
- Port → 9000 (or ERP-configured port)

Step 3: Confirm Port Is Listening (Windows Check)

Run Command Prompt as Administrator:


netstat -ano | findstr 9000

Expected output:


TCP    0.0.0.0:9000     LISTENING

❌ If no output → Tally is not listening
✔ Restart Tally as Administrator

Step 4: Match ERP Connection Settings Exactly

In TICK Production ERP, verify:

Tally IP Address:
- Same PC → 127.0.0.1 or localhost
- Network PC → Actual LAN IP (e.g. 192.168.1.10)
Port → Same as Tally (9000)
Connection Type → TCP / ODBC / XML (as supported)
Company Name → Exact match (case-sensitive)

Step 5: Disable Firewall Blocking (Critical)

Temporary Test (Recommended):


netsh advfirewall set allprofiles state off

Retry export.

If it works → firewall rule required.

Permanent Firewall Rule (Recommended):

Allow inbound on Tally port:


netsh advfirewall firewall add rule name="Allow Tally 9000" dir=in action=allow protocol=TCP localport=9000

Step 6: Run Both Applications with Same Privilege Level

Mismatch causes silent blocking.

✔ Either:

Run both Tally & ERP as Administrator
OR run both as standard user

❌ Admin ↔ Non-admin mix can trigger Error 10061

Step 7: Check Multi-User / License Mode

If Tally is:

In Educational Mode
License expired
In Single-user mode while ERP expects server

ERP connection will fail.

✔ Ensure correct license and mode.

Common Issues & Fixes

Issue	Cause	Fix
Error 10061 despite ODBC enabled	Tally not listening	Restart Tally
Works sometimes	Firewall / Antivirus	Add permanent rule
Works locally but not over LAN	Wrong IP / Port	Use LAN IP
Export stops midway	Company not loaded	Load company
ERP shows “connected” but export fails	Port mismatch	Match port exactly

Security Considerations

Avoid exposing Tally port (9000) to public networks
Allow port access only on LAN
Restrict firewall rule to specific IPs if possible
Do not keep firewall disabled permanently
Do not enable Tally connectivity on internet-facing servers

Best Practices

Always open Tally before ERP export
Use static IP for Tally server
Document ERP ↔ Tally port mapping
Keep Tally updated to latest Prime release
Restart Tally once daily in high-volume environments
Avoid running Tally via Remote Desktop session disconnections

Conclusion

Error 10061 during TICK Production ERP → Tally Prime export is not a data issue.
It is a network/service-level connection refusal, most commonly caused by:

Tally not running or not listening
Firewall blocking the port
Port or IP mismatch
Privilege-level conflicts

Once Tally is actively listening on the correct port and accessible, ERP exports work reliably.

#TallyPrime #ERPIntegration #TallyError10061 #TallyODBC #TallyConnectivity #AccountingERP #ProductionERP #TallySupport #TallyTroubleshooting #ERPtoTally #TallyExport #TallyImport #TallyNetworking #TallyFirewall #TallyPort9000 #TallyPrimeIssue #TallyDataSync #TallyITSupport #TallyKB #TallyPrimeERP #TallyServer #TallyTCP #TallyXML #TallyHTTP #TallyLAN #TallyIntegration #TallyPrimeError #TallyAdmin #TallyPrimeTech #TallyPrimeHelp #TallyERPError #TallyPrimeFix #TallyPrimeNetwork #TallyPrimeODBC #TallyPrimeExportError #TallyPrimeProduction #TallyPrimeAccounting #TallyPrimeIntegration #TallyPrimeKB #TallyPrimeSupport #TallyPrimeIssues #TallyPrimeGuide #TallyPrimeSetup #TallyPrimeServer #TallyPrimeIT #TallyPrimeTroubleshoot

Tally error 10061 Tally is not running error TICK ERP Tally integration Tally Prime ERP export error Tally connection refused Tally ODBC error ERP to Tally export issue Tally port 9000 error Tally TCP connection error Tally Prime connectivity iss

← Back to Home