Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Help, please: Warning #5334

413 views
Skip to first unread message

Richard R Urena

unread,
Jun 18, 2002, 1:57:10 PM6/18/02
to
Hello, one of our users reports this problem when attempting
to save a data file to a network drive (Netware 5) from his
Windows 2000 workstation:

"Warning #5334. Command name: SAVE
The SAVE command has succeeded. However, due to contention
for the specified file, the data have been saved to a file
with a different name."

Although no data has -yet- been lost, this is abnormal
and I'd like to fix it if possible.

This is with SPSS version 11. Any help would be greatly appreciated.

only me

unread,
Jun 18, 2002, 7:34:36 PM6/18/02
to

"Richard R Urena" <ur...@lessing.oit.umass.edu> wrote in message
news:aens9m$g...@lessing.oit.umass.edu...


This is usually caused by a read-only file


Mike Benton

unread,
Jun 18, 2002, 8:21:45 PM6/18/02
to
I have experienced this with Win98 on a Novell network setup as well with
SPSS v10 and v11. We only did a work around, which was to save file as a
new name (which, SPSS does for you). If you do a lot of saves this can be a
real pain. Some chose to save locally, then transfer to the network drive
when they were completed manipulating the data.

Mike Benton

"Richard R Urena" <ur...@lessing.oit.umass.edu> wrote in message
news:aens9m$g...@lessing.oit.umass.edu...

Raynald Levesque

unread,
Jun 18, 2002, 10:48:55 PM6/18/02
to
On 18 Jun 2002 13:57:10 -0400, ur...@lessing.oit.umass.edu (Richard R
Urena) wrote:

See http://pages.infinit.net/rlevesqu/DebuggingSyntax.htm#FileIsUsed

Regards


Raynald Levesque rlev...@videotron.ca
Visit My SPSS Pages: http://pages.infinit.net/rlevesqu/index.htm

Arthur J. Kendall

unread,
Jun 19, 2002, 12:51:45 PM6/19/02
to
You can really do yourself harm by writing over the same file. I usually advise
being careful not to write over a file unless it is known to be incorrect or you
are critically short of disk space.

If you are doing a lot of data transformations between saves, you can save your
syntax (which you are probably doing anyway) and execute it in sections as you
develop it. Once you have finished developing your syntax you can run it all
one time, then save the file.

If you need to develop a lot of syntax, you can save machine resources by using
only a sample of the data to develop and debug the syntax. Then apply the
syntax to the whole file.

Kees de Boer

unread,
Jun 21, 2002, 9:24:10 AM6/21/02
to
This looks a bit like error 1407 with warning 5322 'Command name: SAVE'

It occurred with one of our users who contacted me because SPSS claimed the
(network)volume would be full.

In no way this was the case and no matter what i tried, it would'nt save in
.SAV-format. It did in .POR-format e.g.

After a lot of trying i suddenly saw that she had two cases (on a total of
2600 cases) with the same name in column 1.
After changing the the name of one of these cases it did save.

This was the complete error-messages:
==========
Error. Command name: SAVE
Program error processing SPSS system file dictionary (DATA1209)
This command not executed.

Error # 1407
Error writing the dictionary to a new data file.

Warning # 5322. Command name: SAVE
The attempt to save the data file has failed because the disk is full, an
I/O error has occurred, or the task was interrupted. IF SAVING OVER AN
EXISTING FILE, THAT FILE HAS BEEN LOST. Clear som disk space or
choos a different device and try again.
==========


Kees de Boer
Co-worker datamanagement
EMGO (Institute of Extramural Health Research)
VUMC, Amsterdam


On 18 Jun 2002 13:57:10 -0400, ur...@lessing.oit.umass.edu (Richard R
Urena) wrote:

Rich Ulrich

unread,
Jun 23, 2002, 4:39:56 PM6/23/02
to
On Fri, 21 Jun 2002 15:24:10 +0200, Kees de Boer
<cpj.de_b...@med.vu.nl> wrote:

> This looks a bit like error 1407 with warning 5322 'Command name: SAVE'
>
> It occurred with one of our users who contacted me because SPSS claimed the
> (network)volume would be full.
>
> In no way this was the case and no matter what i tried, it would'nt save in
> .SAV-format. It did in .POR-format e.g.
>
> After a lot of trying i suddenly saw that she had two cases (on a total of
> 2600 cases) with the same name in column 1.
> After changing the the name of one of these cases it did save.
>
> This was the complete error-messages:

I know I can't help you with the error, but I think that your report
is going to be frustrating to those people who *might*.

First and foremost,
Did the error come back when you changed
the name BACK? That is just one step for showing
that you actually have 'pinned down' what would then
seem to be a *really weird* error.

What SPSS version 11, and a workstation.
What was the exact SAVE command?
Is this 'network volume' just an alternative to a C: drive,
or are you dealing with a network-version of SPSS?
(If you were saving to a database other than the simple
SPSS -sav file, I could imagine that your name-change
corrected a duplicated value for a unique ID; that could
make your reported solution actually sound logical.)

Hope this helps.

--
Rich Ulrich, wpi...@pitt.edu
http://www.pitt.edu/~wpilib/index.html

Kees de Boer

unread,
Jun 26, 2002, 4:32:28 AM6/26/02
to
On Sun, 23 Jun 2002 16:39:56 -0400, Rich Ulrich <wpi...@pitt.edu> wrote:

>On Fri, 21 Jun 2002 15:24:10 +0200, Kees de Boer
><cpj.de_b...@med.vu.nl> wrote:
>
>> This looks a bit like error 1407 with warning 5322 'Command name: SAVE'
>>
>> It occurred with one of our users who contacted me because SPSS claimed the
>> (network)volume would be full.
>>
>> In no way this was the case and no matter what i tried, it would'nt save in
>> .SAV-format. It did in .POR-format e.g.
>>
>> After a lot of trying i suddenly saw that she had two cases (on a total of
>> 2600 cases) with the same name in column 1.
>> After changing the the name of one of these cases it did save.
>>
>> This was the complete error-messages:
>
>I know I can't help you with the error, but I think that your report
>is going to be frustrating to those people who *might*.

Which is by no means my intention...

>
>First and foremost,
>Did the error come back when you changed
>the name BACK? That is just one step for showing
>that you actually have 'pinned down' what would then
>seem to be a *really weird* error.

No, i did not do that. I was allready too happy that the user how called me
could go on with her work...
I perform at this institute as a first line helpdesk for all kinds of
computer problems and as the error message statet the disk would be full
while there was plenty of space left, she called me. I am not a SPSS-crack.

By no means in my response to the poster did i meant to say that the error
messages of him and the user here were identical, i merely say
similarities.

As i changed the content of one of the case ID's that were identical, the
problem was over. As it was not my intention to proof that this was the
definitive solution i saw my job there as over. We were content that she
coulde save her work in SPSS-format.

>
>What SPSS version 11, and a workstation.

I am not sure. Must be version 9 or perhaps 10. We have a policy of not
updating to the last version every time one comes out. First a course will
be prepared to learn the basics etc to the student. In effect this means no
more updates than 1 every other year.
The platform used was Windows 98

>What was the exact SAVE command?

Simply save the current work through the File-menu. As that did'nt work
Save As... to other mediums but to no avail.

>Is this 'network volume' just an alternative to a C: drive,

The network volume is a Banyan Vines volume and in fact an alternative to
the local hard drive. Advantage of this network volume is that it is backup
up at night and it is available to group members even from home via a
secure homepage.

>or are you dealing with a network-version of SPSS?

No, we have a site licence and install SPSS local on all workstations.

>(If you were saving to a database other than the simple
>SPSS -sav file, I could imagine that your name-change
>corrected a duplicated value for a unique ID; that could
>make your reported solution actually sound logical.)

Saving in the portible format .por worked without problem. The exported
file could also be imported into SPSS without problem. Saving it to
.sav-format under a different filename gave the same error again.

>

>Hope this helps.

Thank you and i hope i did not and do not bring any one to frustration.


Kees de Boer
----------------
Datamanagement at the Institute of Extramural Medicine (EMGO) at the Vrije
University (VUmc) Amsterdam
cpj.de_boer.emgo.med.vu.nl

0 new messages