I've looked at many KB articles, tried some of the suggested fixes and I've also tried getting help from Sage Support, but I still have problems. Any assistance would be greatly appreciated.
Scenario:
I recently upgraded from Sage 50 Accounting 2013 to Sage 50 Accounting 2016. Sage 2013 was on Windows Server 2003 and Sage 2016 was installed on a new server, Windows Server 2012 R2. I have about 5 users who use Sage so the company folder was shared out and mapped as a network drive on the workstations. The workstations are all Windows 7 Pro 64 bit. To move the Sage data from the old server to the new server, I performed a company restore from a backup through Sage. The company restore, as well as the data conversion, completed successfully.
Problem:
My users randomly will receive filesystem errors (3110, 3112, 3, etc. just to name a few) on random files (JRNLROW.DAT, LINEITEM.DAT, GENERAL.DAT, etc. just to name a few). Sage crashes after these errors and the users need to start Sage again and log back in. Sage Support, as well as the KB articles, say these errors occur when the workstations lose network connectivity to the server. When the errors occur, the users can successfully browse to the mapped network drive. Here is what I've done so far:
Attempted fixes so far:
- Turned off the Power Save feature on network adapter on both the workstations and server
- Set the Windows Power Plan to "High Performance" on both the workstations and server
- Disabled IPv6 on the workstations (would this need to be done on the server as well?)
- Smokeping against the server looks fine with 1.8ms response time and virtually no packet loss
- Ping and tracert from the workstations to the server look fine
- Pervasive's network and stress test utility reports no issues
- Windows firewall was opened up during the Sage install on both the server and workstations
- Hardware firewall has been confirmed wide open for the server
- Windows Event Log on the server and workstations is free of any network-related errors
- Windows User Account Control (UAC) is disabled on the workstations
- CPU/RAM/HDD are not closed to being maxed out on either the server or workstations
Considering the Sage company restore and data conversion both completed successfully, I find it hard to believe this would be a data corruption issue. I have yet to see any network problems and I have ruled out physical network issues (cabling, wall drop, switch port, workstation, etc.). Server and workstations are on the same domain, but different networks. Should the server and workstations be on the same network?