Summary. The instructions below were previously what Peachtree technicians were advising as a resolution to this problem.

However, as of 6 December 2012, there is a newer and easier resolution.

Follow these steps to correct the problem of not being able to update your client workstations because the upgrade thinks the server hasn’t updated yet.

  1. Make sure your server has the latest release of Peachtree Sage Accounting 2013 SR1 (found here). Then continue.
  2. In the companies / data folder, find the verinfo.ini file and open it. Note that there may be two verinfo files. You want the Configuration File that ends in ini and not any text file.

The verinfo.ini file will likely contain the following:

[VerInfo]
Ver=20.0.00
ServerType=FullServerOrStandalone

Replace the 00 with 01 on the end of the version information so the contents of the verinfo.ini file will read as follows:

[VerInfo]
Ver=20.0.01
ServerType=FullServerOrStandalone

Now when attempting to update the client workstations, you should no longer get the error about the server not being updated.

* * *

Old Problem Resolution. Below is an instructional video we created for the Peachtree Accounting 2011 upgrade to SR4 (Service Release 4). Two years later, there is still a problem of client computers incorrectly identifying what version the server is running. This results in an incorrect error message stating that the server hasn’t been updated, even after it has been updated.

The video below is still applicable as a support resource for this issue. However, the configuration file mentioned in the video (Peachtree180) should be Peachtree200 if you’re working with the latest 2013 version. With this change, the video below will be helpful for those encountering this problem. For more details, visit the Sage support document for this issue.

__________

Document History. This document was published on 20121121at1110 based on the best information available from Sage-Peachtree at that time. It was update on 20121206th1330 when a better resolution was found.

%d bloggers like this: