Cannot Open Status.Dat


D

Daniel Bohner

Howdy all,

I'm a support guy - not a PeachTree person, so help me where you can.

My client has about six machines access Peachtree on a shared server
drive. Starting last week - one machine would get an error message
stating "cannot open p:\peachw\company\status.dat" (slightly changed
to accomidate file structure).

One machine was affected by the issue last week. I checked the share
and the users was able to update create and delete files (test.txt -
that I created). After trying a lot of stuff I removed PeachTree and
reinstalled - after the reinstallation they were able to access
PeachTree.

This morning four machines were not able to access (and they got the
same error message - cannot open status.dat). Later in the morning
all but one machine was able to get into PeachTree.

Anyone have an idea what might be going on?

Your time and contributions are appreciated!

Daniel Bohner
(e-mail address removed)
www.existinglight.net
208.250.1917
 
Ad

Advertisements

F

Fred Deinlein

Most interesting. I had a similar problem happen to me on 1 October. When
I try to start up PCAW, I get a series of error messages that say: "File
system error number: 20 {path to status.dat, company.dat, options.dat, etc}"
before I can even get to a point where I can select a menu. The unhelpful
explanation for this message is that it is "related to swap file space; run
defragmentation and chkdsk". I did in fact have a swap space shortage as a
result of a recent memory upgrade, but fixing that did not fix the error.

Even more interesting, I am able to run PCAW when logged in as
administrator, but not when logged in as myself. I was running PCAW
without setting up user accounts, but even setting up specific accounts for
myself did not fix the problem.

This appears to be some kind of permissions problem, but a check of file and
directory attributes offers no clues as to what kind of problems they might
be.

-- --------------------
F. Deinlein
(e-mail address removed) (remove xxx)
 
R

Ralph A. Jones

Do you have all of your network drive mappings set to re-connect at
boot/logon? And in sync with your datapath= statement in your
[peachtree].ini file? If not, users can throw on Zip drives or
thumb/jump drives that can screw up your drive designations and, hence,
your Peachtree network datapath.

In any event, trouble-shooting step number one is always re-boot the
troublesome machine (step number two often being re-boot the "server"
machine). Hopefully this will re-establish the network drive/share (in
accordance with the datapath= statement) and Peachtree will be happy,
happy, happy again.

Naturally, since the data is sitting in a network share, users can
manually navigate to the data from the Peachtree "Open Company" routine,
even map a network drive to it, but this is usually a wee bit too
cumbersome and technical for your Average Joe user who just wants his
software to work so they can see how much cash came in today.
 
F

Fred Deinlein

I can't speak for the original poster of this problem, but in my case, I'm
running on a stand-alone PC; no network drives are involved. Googling
through some old postings, there are references to users having to set
permissions to registry keys for individual users. I haven't tried that
yet, but it didn't work for another person.
--
F. Deinlein
(e-mail address removed) (remove xxx)

Ralph A. Jones said:
Do you have all of your network drive mappings set to re-connect at
boot/logon? And in sync with your datapath= statement in your
[peachtree].ini file? If not, users can throw on Zip drives or
thumb/jump drives that can screw up your drive designations and, hence,
your Peachtree network datapath.

In any event, trouble-shooting step number one is always re-boot the
troublesome machine (step number two often being re-boot the "server"
machine). Hopefully this will re-establish the network drive/share (in
accordance with the datapath= statement) and Peachtree will be happy,
happy, happy again.

Naturally, since the data is sitting in a network share, users can
manually navigate to the data from the Peachtree "Open Company" routine,
even map a network drive to it, but this is usually a wee bit too
cumbersome and technical for your Average Joe user who just wants his
software to work so they can see how much cash came in today.

Daniel said:
Howdy all,

I'm a support guy - not a PeachTree person, so help me where you can.

My client has about six machines access Peachtree on a shared server
drive. Starting last week - one machine would get an error message
stating "cannot open p:\peachw\company\status.dat" (slightly changed
to accomidate file structure).

One machine was affected by the issue last week. I checked the share
and the users was able to update create and delete files (test.txt -
that I created). After trying a lot of stuff I removed PeachTree and
reinstalled - after the reinstallation they were able to access
PeachTree.

This morning four machines were not able to access (and they got the
same error message - cannot open status.dat). Later in the morning
all but one machine was able to get into PeachTree.

Anyone have an idea what might be going on?

Your time and contributions are appreciated!

Daniel Bohner
(e-mail address removed)
www.existinglight.net
208.250.1917
 
C

Carla F.

Another thing you might check on the problem computers is the .ini file -
all versions of peachtree up to 2003 at least rely on an .ini file in the
windows directory - opening that up in notepad you can see where the
computer is looking for data and program files. PCW2003 is pcw100.ini but
the older ones were something like paw70.ini. Can't remember exactly....
It's pretty easy to look at and correct if it's not pointing the way you
want it to.

carla
 
F

Fred Deinlein

Yes, the .ini file points to the right directory. At any rate, an .ini file
error would not explain why I can run PCAW as administrator but not as a
normal user.
 
Ad

Advertisements

F

Fred Deinlein

Well, you got me on the right track, and I believe it was Mr. Gross' posting
that said one had to be a Win2K Power User in order to run PCAW. I tried
that and it solved the problem. I'm not sure I understand the rationale for
this, but it seems to work while still not requiring that the user have the
full privileges of Administrator.

Thanks all for your suggestions.

F. Deinlein
(e-mail address removed) (remove xxx)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top