Tally Prime Multi-User Data Crash – Simple Troubleshooting Guide
In a multi-user (client-server) setup, multiple computers work on the same Tally data through a LAN network.If the network becomes unstable, users may experi...
In a multi-user (client-server) setup, multiple computers work on the same Tally data through a LAN network.
If the network becomes unstable, users may experience:
Tally freezing or closing suddenly
Errors while saving vouchers
Company not opening
Data corruption warnings
This guide explains why this happens and how to fix & prevent it.
What Is a Multi-User Data Crash?
Simple meaning:
✔ Tally stops working properly in multi-user mode
✔ Data may not sync correctly
✔ Users may get unexpected errors
It usually affects all users, not just one system.
Why Does This Problem Occur?
Think of LAN like a road connecting computers.
If the road is unstable → data traffic gets disturbed.
Common causes:
Loose / faulty network cables
Weak or fluctuating Wi-Fi
Server computer restarting
Network switch/router issues
Power fluctuations
Heavy network usage
Antivirus/firewall blocking communication
? Common Symptoms Users Notice
✔ Tally hangs during voucher saving
✔ Sudden “Not Responding”
✔ Company closes unexpectedly
✔ Different data shown on different systems
✔ Data corruption errors
✅ Step-by-Step Solutions
Follow these checks carefully.
1️⃣ Check Server Computer (Most Important)
✔ Is the server PC ON?
✔ Is Tally running on server?
✔ Did server restart unexpectedly?
? Server issues affect all clients
2️⃣ Check Network Stability
✔ Ensure LAN cables are firmly connected
✔ Avoid damaged cables
✔ Prefer wired LAN over Wi-Fi
? Wi-Fi fluctuations = Common crash reason
3️⃣ Restart Network Devices
✔ Switch OFF router/switch
✔ Wait 10–15 seconds
✔ Turn ON again
✔ Restart server & client systems
4️⃣ Avoid Heavy Work During Instability
If network feels slow/unreliable:
✔ Avoid saving critical vouchers
✔ Pause report generation
? Prevents data mismatch
5️⃣ Check Power Supply
✔ Use UPS for server & switch
✔ Prevent sudden shutdowns
6️⃣ Look for Error Patterns
| Situation | Likely Cause |
|---|---|
| Crash for all users | Network/server issue |
| Crash for one user | Local PC issue |
| Crash during saving | Network fluctuation |
| Data mismatch | Sync interruption |
7️⃣ Temporarily Disable Antivirus / Firewall
✔ Security software may block Tally traffic
✔ Disable briefly for testing
⚠ Re-enable after check
8️⃣ If Data Corruption Appears
? STOP WORKING IMMEDIATELY
✔ Restore latest backup
✔ Use Repair option (with expert help)
⚠ Important Precautions
✔ Never ignore frequent crashes
✔ Never continue working on unstable network
✔ Always take regular backups
✔ Avoid force-closing Tally repeatedly
✅ Best Practices to Prevent Multi-User Crashes
✔ Use Wired LAN (Highly Recommended)
✔ More stable than Wi-Fi
✔ Fewer interruptions
✔ Protect Server With UPS
✔ Prevent sudden shutdown
✔ Protect active data
✔ Maintain Good Network Hardware
✔ Quality cables
✔ Reliable switches
✔ Avoid cheap connectors
✔ Take Daily Backups (Critical Habit)
✔ Lifesaver during crashes
✔ Store in separate drive/cloud
✔ Avoid Overloading Network
✔ Large file transfers → slow Tally
✔ Heavy downloads → lag/crash
✔ Monitor Early Warning Signs
✔ Slow response
✔ Frequent hanging
✔ Random disconnects
? Fix early → Prevent corruption
Short Conclusion
Multi-user crashes are usually network-related, not Tally defects.
✔ Stable LAN + Healthy Server = Smooth Tally
✔ Backups = Ultimate Safety Net
If crashes continue → Consult IT/network professional.
Was this guide useful?
Your answer helps us keep BISONKB accurate and practical.