Tax Update installs every time I close Peachtree

[BentFranklin]

Release: Peachtree Pro Accounting® 2007 (SR-3)
Build: 14.0.03.1668
Installed Tax Service: 20070201
Registered Tax Service: 2007

Windows 2000 5.00.2195
Service Pack 4

The February Tax Update reinstalls itself every time I close Peachtree. The account I use to run Peachtree has administrator rights. Does anyone know how to tell Peachtree that this is already installed?

[rick Prindivill]

Rename the update file located in the UPDATES folder.

[sbowman]

I have the same problem, however, I am running a multi-user environment. And the update is getting installed on any workstation with payroll access.

But I am not sure what file you want to rename, and what to rename it to. This is the updates directory in the shared data folder.

http://i11.photobucket.com/albums/a159/sbowman01d/Peachtree-Updates.jpg

[captainship]

I think Rick is saying to rename the Feb Tax update that keeps trying to install.

[sbowman]

I will try it, but it is strange that the Jan file is still there and not causing any problems.

[dgh-afr]

I've got two different servers, in the update directory of one (that works well), the file oupaw14.ini has Version=2007.02.01. while the one that keeps reinstalling the update has Version=2007.02.02. I haven't tried editing this file, but maybe it's the culprit?

[sbowman]

It worked!

But in a Dec post, Rick recommended deleting the whole updates directory. What gives?

http://www.peachtreeusers.com/.forums/showthread.php?t=12605

[CookieMom]

I too starting having the same problem. Mine started when I checked for updates and saw the Feb update. I thought it was a new one so I did a download. I figured if the update was there, it was a new update.

I did rename the file as you all said, but I agree, why did we have to do that?
Thanks,
Cindy

[DonaldFish]

I also checked for updates yesterday and had the same problem as CookieMom. I renamed the file, and the problem stopped.

Today it must have automatically downloaded a 20070202 update and installed it. There does not seem to be the same problem with the …02 update.

[whb]

I have been having this same problem. I can not find an update file on my workstations but I did on the server. I renamed the file but I am still getting the same results. I hate to ask but if someone could take the time and give me a step by step procedure I would be greatful. my system consists of a server and 3 work stations all running xp except for one with 2000pro. Pt seems to be running great except for this. Thanks whb

[Killertunes]

I had the same problem that everyone else has had with this update. I tryed renaming the config file in the updates folder, that did not work. I deleted everything from the updates folder, that worked. :)

[whb]

I went to Sage's web site, wandered around till I found a customer service chat that did not require any kind of support plan for PT complete. I was sent an email that had manual instructions for this update. It worked. I asked if I needed to run it on my server which has only the server componets of PT rather than a peer to peer setup and was told yes. but that isn't correct. I ran it on my workstations and it solved the problem. whb

[TheWolf]

I have had a few clients run into this. The manual fix works but the problem seems to be either a corrupt microsoft installer or a different version. I tested this because I had a laptop I owned having the problem. I downloaded the latest version of microsoft installer and the problem went away.

[LauraG]

Tom, did your problem disappear when you installed the 20070202 update? I think the problem started for most with the 20070201 file. Could it have been bad which prompted Sage to issue a second February update?

[TheWolf]

It could have been a problem with the update. Anytime I have an install problem with any program, and if I have time, I reinstall the Microsoft installer.

[akash]

thanks :) renamed feb tax update and no longer have a problem.. i love this forum