Snapshot failure

[Kevin Witty]

"Report snapshot was not created because you didn't have enough free disk
space available for temporary work files"

I have plenty of space. Any ideas????

Thanks,

Kevin

 

[rolaaus]

Here is one possibility, but you didn't give any configuration stats. Are
you trying to create the snapshot on a netowrked share drive? If you don't
have permission to create files, the error will say you are out of space.

If you are trying to create the snapshot locally, then I'm at a loss.

 

[Kevin Witty]

I'm trying to create the snapshot file on the same drive and directory the
backend is located on, so I have to presume I have the rights. Here's the
weirdness: if I run the master front end from the network drive it's located
on (the backend is in a directory below it), it works fine. But running a
copy of the master which has been put on the user's desktop (including my
own, using the same terminal services session), I get the error. The backend
works fine, otherwise. (Well, except for the topic of my other current
message here.)

 

[Stephen Lebans]

This error can be caused by an illegal character in the filename/path.

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.

 

[Kevin Witty]

Thanks, but the path is the same running it from the network copy of the .mde
and the user's Desktop copy of the mde, and the path is that which points to
the backend, which works, so that dog don't hunt. The network copy does not
give the error; the desktop copy does, in all cases.

What's wrong with this picture? <g>

Kevin

 

[Stephen Lebans]

In my personal experience, the error you described can be caused by one
of four issues:

1) You don't the proper permissions to create a file in the destination
folder.

2) There is an illegal character in the full filename/path

3) There are more than 256 characters in the full filename/path

4) There really is not enough free disk space to create the Snapshot
file

I've listed the issues in the order of appearance in the NG's.

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.

 

[Kevin Witty]

Thanks, Stephen. The error doesn't APPEAR to be caused by any of those
problems. Again, I and most of the other users are accessing this app via
Terminal Services. If I run the mde from the network, the file is created
fine. If I run it, in the same Terminal Services session, from my desktop,
it fails. Unless running it from the network directory gives me different
permissions than running from the desktop, I don't think permissions are the
issue. There apparently aren't illegal characters in the path, or I couldn't
access the backend. Ditto more than 256 characters. And there really is
enough free space. (Hey, Terminal Services... everything is basically
running from the same PC, right??)

One of my old beta testers used to sign himself as "Breaker Bill". Maybe
I'm Killer Kevin? Lord knows this stuff is killing me.

Kevin

 

[Stephen Lebans]

Sorry Kevin, I have limited experience with TS. Perhaps you should start
a new thread. Keep it simple and focus on the TS/file creation issue.

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.