reckon
asked on
Peachtree service release update help needed--soon!
We're stuck in a loop.
Peachtree Complete Accounting 2007 is running on computer 1. It is also installed on computers 2 and 3, which are networked with comp 1. The database (company file) is on comp 1. All computers are running Win XP.
We updated comp 1 with Peachtree Complete Accounting service releases 1 and 2. When we went to install these releases on comps 2 and 3, we get the following message:
Setup has detected that you are using Peachtree Accounting on multiple computers. You must install this update on your Peachtree server before installing it on this computer.
The update IS installed on the "server." How can I get the updates to install on comps 2 and 3? Until we do, payroll done on those machines is wrong . . .
Peachtree Complete Accounting 2007 is running on computer 1. It is also installed on computers 2 and 3, which are networked with comp 1. The database (company file) is on comp 1. All computers are running Win XP.
We updated comp 1 with Peachtree Complete Accounting service releases 1 and 2. When we went to install these releases on comps 2 and 3, we get the following message:
Setup has detected that you are using Peachtree Accounting on multiple computers. You must install this update on your Peachtree server before installing it on this computer.
The update IS installed on the "server." How can I get the updates to install on comps 2 and 3? Until we do, payroll done on those machines is wrong . . .
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Just wondered if pulling the plug would help :)
ASKER
Sorry, about the delay, but my colleagues are reluctant to pull it off the network.
I think your way may be the only way to go (no other solutions have presented themselves), so we'll see who wears down faster . . . will report back as soon as we've tried your solution.
I think your way may be the only way to go (no other solutions have presented themselves), so we'll see who wears down faster . . . will report back as soon as we've tried your solution.
ASKER
Still no resolution on my end--
ASKER
Would you please leave the question open for at least two more weeks?
ASKER
Please keep this open longer--thanks
ASKER
Sorry about the delay--no resolution here. I'm going to accept the one suggestion just to close the question.
I had the exact same problem. I found that there is a file named "PTX160.ini" that you can change that will allow you to do the update. Just open the file and set the DATAPATH to the same value as the LOCALDATAPATH. Then do the update. Once you have done the update you can change the DATAPATH back to the original value and you should be good to go. I don't care about the question credit. I spent the better part of three weeks before I figured out how to hack this upgrade so if this helps anyone else I'm glad to share.
Where is this "PTX160.ini" located ?
Here is the path: "%HOMEDRIVE%%HOMEPATH%\WIN DOWS\PTX16 0.INI". So for most windows XP machines that would be "C:\Documents and Settings\<username>\WINDOW S\PTX160.i ni". You should not have to make the change for each user, just make sure that noone else connects untill after you have finished doing the update.
ASKER