x Want to participate? Join the group to interact
Options
  • State Suggested Answer
  • Replies 47 replies
  • Answers 5 answers
  • Subscribers 97 subscribers
  • Views 23111 views
  • Users 0 members are here
Browse Forums
Announcements
151
topics
113
replies
General Discussion
5k
topics
13k
replies
Payroll & Tax
633
topics
894
replies
Reporting and Analytics
574
topics
1k
replies
Service Alerts
1
topics
0
replies
Software Development Kit (SDK)
436
topics
673
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 in reply to KimClement

    @Kim

    It's a good suggestion but there is the following two issues with what you have suggested.

    1.He was running on a VM before the upgrade and everything was fine.

    2. I'm not on a VM.... Its on a physical drive.

    Also does "Physical" take into account for Class 0 Hypervisors and VM's?

    I almost forgot I have a another client running the newest version of sage 2016 on a VM and everything works fine...

  • 0 in reply to Best Business Strategies
    Yes, all the devices are hard wired for me.
  • 0
    You said "When the errors occur, the users can successfully browse to the mapped network drive". This suggests the datapath stored in the Peachtree230.ini is not actually where the data is located. Please verify each workstations datapath statement in the Peachtree 230.ini (Sage v2016) located in Program Files (x86), Common Files, Peach against where the actual data is stored.
  • 0 in reply to Kevin.S
    You may simply have data issues. If you send us a recent back up, we will assess the data and get back with you. Send us an email and we will send you a link. I am running my office on Server 2012 without issues.
  • 0 in reply to KimClement
    I get the same error code every time I attempt to access a payment; even when I am directly logged onto the MS Server 2012, and I know for a fact I'm pointed at the right data because one of the sage support staff in a remote session confirmed it.

    The other Tech in this thread who originally posted gets different error codes each time but the syntax, description, and crashing of sage is identical based on what he posted.
  • 0 in reply to toomanyerrors
    I've been thinking maybe Sage having to talk between two different networks might be causing a problem? Yes I do agree with you on that.
  • 0 in reply to KimClement
    I wouldn't be so fast to say it's a networking issue.

    Look at the errors that are being returned for him:

    "JRNLROW.DAT, LINEITEM.DAT, GENERAL.DAT"

    Any systems analyst could tell you that these names are in reference to a database. Also having workstations on other networks is a very common thing, I have several clients running sage and connecting to it on different networks.
  • 0 in reply to Kevin.S

    Pervasive PSQL v11 sp3 is the engine that runs Sage v 2016. Perhaps the cause of the problem is Pervasive loosing it's connection at random which will end Sage 50 abruptly and display what datafiles were affected, such as journal, line item, general, etc. You might want to investigate issues between Pervasive and Server 2012 r2 in the VM environment.

    Hope this helps you.

    Solution Notes http://supportservices.actian.com/kb/

    Pervasive PSQL v11 and Pervasive PSQL v10 are supported in a Virtual machine configuration when the minimum database hardware requirements are met as defined in the Pervasive "Getting Started" documentation.   Pervasive recommends that optimal resources (Processor and Memory) be assigned to the virtual systems to assure stability. This support policy excludes support for the actual configuration and installation of the Virtual software itself.  A different license is required for each vm image (including clones and copies) where the PSQL engine is installed and actively in use. 

    PSQL v11 and PSQL v10 have limited support for virtual environments.  Both will work on virtual machines but do not support moving the license used by one virtual image from one host to a different host.   For a product specifically designed for virtual environments, we recommend PSQL Vx.

  • 0 in reply to KimClement
    If you go to Pervasive's site: www.pervasive.com/.../PSQLv11SP3_readme.htm Windows Server 2012 R2 is not listed under the Supported Platforms. Windows Server 2012 and Windows Server 2012 R2 are different. Could this be causing the errors?

*Community Hub is the new name for Sage City