Peachtree locks up on workstation and server.  Causes both machines to crash.

Posted on 2009-02-08
Last Modified: 2013-11-16
I am an IT contractor for a small healtcare business.  They use Peachtree Premium 2009 and have committed to NIS as a security product on their machines.  The current Peachtree server has been the Peachtree server since Peachtree was first put into use (3+ years ago).  We recently added a new PC to the network in the accounting department and installed PT 2009 and NIS 2009.  That is when the problems started.  When the new workstation launches Peachtree, sometimes it will open and sometimes it won't.  When it does open the user will attempt some action like Printing or Saving, and Peachtree locks up.  The bad part is that it not only locks up the workstation, it also locks up the Peachtree server.  When the lockup occurs, if you attempt to browse My Computer on the workstation, it will not refresh.  I assume this is because the network drive (Z:\) is busy or can't refresh.  The computer will literally sit in this state--we have left it for more than 20 minutes.  After hard booting both the workstation and server, Peachtree will then open on the server as normal.  Z:\ reappears on the workstation and is easily browsable through explorer.  I'm at my wit's end here.  Anyone out there have any suggestions?

Peachtree server:  
Windows XP Home Edition SP3 (I know it is not the most ideal choice but it was a decision made before I became IT contractor and we have not changed it yet).  
Norton Internet Security 2009 with all Peachtree program EXEs allowed in Program control (as per Sage knowledge base).  Peachtree data is located at C:\Peachtree\Company\2008.  NIS 2009 has been running here for months and has no effect on the other workstations.
In an attempt to solve the problem, full trust has been set up between both PCs in NIS.
Additionally, the server and the offending workstation have been given static IP addresses via the router.  

Problem Peachtree workstation:
Brand new Dell Optiplex with Windows XP Pro SP3.
NIS 2009 with all Peachtree programs EXEs allowed in Program control (as per Sage knowledge base).  
Drive Z is mapped to \\server\peachtree\company.

Other Peachtree workstations
2 other machines running Win XP Home SP3 and NIS 2008.
Question by:nerhtoc

    Author Comment

    Removed NIS complete.  Problem still exists.

    Accepted Solution

    I have two clients that have near the exact same problem, only one of them does not run Peachtree. But on the client that does run Peachtree, running two stations in a peer network, one of them being the host / server. On the workstation, after installing PT 2009 (Quantum), I would have network access until I started PT, then it would hang,
    I would lose network access and PT would hang up also on the host. On the workstation I  had reinstalled PT multiple times always with the same results.
    I decided to UNINSTALL NIS 2009 on both machines, and the problem was resolved.  So I reinstalled NIS 2009 on both, setup the firewall according to PT instructions,
    And again Peachtree would hang, and my network access would go away.  I Googled and finally found this link in the Norton community:
    of which the resolution for me was in this post by kreativekai:
    Although this problem still exists, I did discover a small "workaround" so you don't need to completely disable Auto-Protect and SONAR.  If you go into your NAV 2009 settings: Computer > Exclusions/Low Risks > Scan Exclusions > Configure[+] and put your shared drives/folders that you need network access to in NAV's "Auto-Protect Exclusions" List (no need to put it under "Scan Exclusions" List), then you can still have Auto-Protect enabled for the rest of your computer... it just will ignore what goes on in the shared drives/folders you excluded AND WON'T BLOCK ACCESS TO THEM EVERY 1-2 HOURS!!!  
    The above resolution was applied to NIS 2009 on the host / server machine. After adding the shares to Auto Protect Exclusions, my problem was resolved.
    Other posts in this message thread elude to Symantec finally admitting they have a problem in this version. My other client has more stations and a different mix of software, but the same issues.  In the near future I will apply this fix to their NIS 2009 setup and report back if it resolves their problem too.


    Author Comment


    Thanks for the information.  I'm not sure that this will help me.  I removed NIS 09 from the offending client machine and it and the server still locked up.  I did not removed NIS from the server since other machines have been connecting to it with no problems for months now since NIS 09 was installed.  

    We have decided to move on to bigger and better things namely a Windows 2003 or 2008 server to host Peachtree and other applications.  We have currently deployed Windows 2003 after downloading a free 180 trial from Microsoft and all is running well at this point.  We have decided that it is probably best to stop depending on a simple workstation as our server in this case.


    Author Comment

    There is some discussion on this topic now.  Please do not delete.

    Expert Comment

    The move to a true server based environment is definitely a step in the right direction.  Desktop OSes were not desinged to be file servers.  My client with only the two workstations doesn't qualify for such a setup, but my other client that I mentioned with a similar problem would benefit.  I only have a couple clients with peer networks and I hate them ( the networks, not the clients..ha), I have much less network issues on domain based server environments.
    Just one thing I want to point out. You stated: "I did not removed NIS from the server since other machines....." It is the server that holds the shares and the workstations target, so the configuration (or removal of NIS 2009) really applies only to the server.  It is the folders on the server machine that NIS 2009 is protecting, and you could only apply the changes (or removal) of NIS 2009 on the server machine to affect the situation.   Other information in the post from the symantec community forums also point out that the amount of data transferred and speed of transfer seemed to have an impact.  My resolution was accomplised by first confirming that NIS 2009 was the problem, then reinstalling and applying the changes (to the server machine) as outlined to bypass scanning of those shared folders. For me...problem resolved.
    Anyway, you have moved passed this into another environment.   Maybe others that research this issue can benefit from our transcriptions.


    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Top 6 Sources for Identifying Threat Actor TTPs

    Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

    In our personal lives, we have well-designed consumer apps to delight us and make even the most complex transactions simple. Many enterprise applications, however, are a bit behind the times. For an enterprise app to be successful in today's tech wo…
    If you're not part of the solution, you're part of the problem.   Tips on how to secure IoT devices, even the dumbest ones, so they can't be used as part of a DDoS botnet.  Use PRTG Network Monitor as one of the building blocks, to detect unusual…
    Viewers will learn how to use the Hootsuite Dashboard.
    The viewer will learn how to back up with the free utility from runtime software, DriveImageXML using Windows 8. Download DriveImageXML from Open folder where it was saved: Start installation by double clicking the install scrip…

    759 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    9 Experts available now in Live!

    Get 1:1 Help Now