x Want to participate? Join the group to interact
Options
  • State Suggested Answer
  • Replies 47 replies
  • Answers 5 answers
  • Subscribers 97 subscribers
  • Views 22974 views
  • Users 0 members are here
Browse Forums
Announcements
150
topics
113
replies
General Discussion
5k
topics
13k
replies
Payroll & Tax
631
topics
887
replies
Reporting and Analytics
573
topics
1k
replies
Service Alerts
1
topics
0
replies
Software Development Kit (SDK)
434
topics
671
replies
Year End
83
topics
128
replies
toomanyerrors

Errors after Sage 2016 Upgrade

SUGGESTED
Posted By

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?

  • 0
    I have the exact same setup/migration as you and almost Identical errors:

    "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." The company restore, as well as the data conversion, completed successfully.

    Every time a user access a Payment Sage freezes and crashes instantly for everyone with weird errors that one give a 4 digit error code and nothing else.

    I have attempted almost all the fixes you have posted and sage support hasn't been able to accomplish anything.
  • 0 in reply to Kevin.S
    My users say they get the "Fatal filesystem error "#" "file"" at random. It doesn't seem to matter what specifically they're doing in Sage. Do you have a physical server, or is it a VM? Mine is a VM through VMware vSphere (same as the Server 2003 and Sage 2013).
  • 0 in reply to toomanyerrors
    The Old Sage 2013 installation was on a Physical server and I have the new Installation on a Physical Server, However there are some Hyper-V VM's that are sitting on top of the new MS Server 2012 R2 Physical server. I would say that it is highly unlikely that a VM is causing the problem. I doubt it is even a networking issue due to the timing of what we both did.

    Its more likely to be that the conversion program which preps the Sage data for Sage 2016 is missing something when doing a conversion on data that resided on MS 2003 Server. Do you mind if I ask when you migrated from the MS Server 2003 to the new MS Server 2012 R2.

    I migrated mine over on Monday 4/2016.
  • 0 in reply to Kevin.S
    I also think the problem lies with either the backup, restore or conversion aspect of the migration. I did my migration on 11/19/2015.
  • 0 in reply to toomanyerrors
    I backed up all the files from the MS Server 2003 onto a Synology NAS before doing anything, and I have not removed the MS Server 2003 installation of Sage 2013(Just Shut it down). Yesterday Sage support told me that they could convert the data for me if we can't solve it, and it opens correctly on the old server without errors. Problem with checking the data on the old server is that sage is only installed as a service and all my clients have been updated to the newest 2016.2.

    I'm really hoping for a better solution to this but so far that's all I got.
  • 0 in reply to Kevin.S
    So they converted 2016 data back to 2013 and it worked on the old server? For sure sounds like their conversion wizard messes something up or there is an issue with Sage and Windows Server 2012 R2 that no one is aware of yet. Are your server and workstations both on the same network? With my old setup they were, but now the new server is on a different network. I've been thinking maybe Sage having to talk between two different networks might be causing a problem?
  • 0 in reply to toomanyerrors

    No I still have the 2013 data. I need to confirm it is still good before they will convert it into the 2016 data. 4 of the workstations are on the same network, the 5 PC is on a VPN connection. Being that I have workstations both on the network and remotely connected over a VPN I would say that having workstations on a different network is not a problem.

  • 0 in reply to Kevin.S
    Unfortunately that's not an option for me. My users have been using Sage 2016 for over a month now so there would be a ton of data loss if I had to go back. I honestly thought this would be a simple fix initially. We'll need to stay in touch, hopefully one of us can get this working properly!
  • 0 in reply to toomanyerrors
    Yes I agree, the data loss of even 3 days is bothering me so I understand where you are coming from. If I find anything about how to fix or solve this issue I will absolutely post what I discover here for you.
  • 0
    SUGGESTED
    Sage should be installed on a physical drive on ServerXYZ and all workstations accessing Sage should be mapped to ServerXYZ. .

*Community Hub is the new name for Sage City