PDA

View Full Version : Need help! Old Peachtree version with error!

cswimc
04-09-2010, 12:54 PM
I am new to these forums and ran into a situation that I need help with.

I do freelance IT work and a client I am currently helping recently fired thier IT Tech Support guy. I am now their IT support and they run Peachtree accounting software. Unfortunately, the old IT guy refuses to give me the administrator account for the network. That is one problem. Everything was fine because I am hired to gut their whole network and rebuild a new upgraded one from scratch. Until then I need to keep the company running smoothly. Here is where the problem occurs...

The company is running an obsolete version of Peachtree (version 6.0.1). Today, I was called to make an onsite visit and cannot fix the problem. There is an error that says STATUS.DAT cannot be opened. How can I fix this? I dont have admin rights and cannot login to their server.

When I upgrade the network we will be getting the newest versions of everything over the next few weeks. In the mean time I am dealing with this 'organized chaos' left behind until the new system is up and running. Any help is greatly appreciated. Thanks!
Marques Ward
04-09-2010, 04:21 PM
It doesn't sound promising. The status.dat file is located where the company data is. Peachtree must find and have access to the status.dat in order to open Peachtree. If you have a backup abd have access to it. you might be able to reinstall Peachtree, otherwise I think you have to get that password.
rick Prindivill
04-09-2010, 07:42 PM
Typically when a user sees any error message referencing STATUS.DAT, it means that there is a communication problem. In your case, seemingly the Peachtree program on the workstation has lost its mapping or connection to the Server.
cswimc
04-11-2010, 08:32 PM
Typically when a user sees any error message referencing STATUS.DAT, it means that there is a communication problem. In your case, seemingly the Peachtree program on the workstation has lost its mapping or connection to the Server.

You were right! It was a communication error. It turns out that the STATUS.DAT file got renamed on the server somehow which is very strange but after renaming it from STATUS1.DAT to STATUS.DAT, everything was back up and running this afternoon.

Thanks for your help!