Error # 1405

[Timo Hursti]

SPSS 17.0 won't open certain data files I've received from other
users, the other users don't experience any problems with these
files. I get the following error message:

GET   FILE='C:\Documents and Settings\timo.hursti\Mina
dokument\Projekt\IBS 2\SPSSnyfilK&J.sav'. >Error.  Command name: GET
FILE >Invalid SPSS Statistics system file: C:\Documents and
Settings\timo.hursti\Mina dokument\Projekt\IBS 2\SPSSnyfilK&J.sav
(DATA1204) >This command not executed. >Error # 1405 in column
8.  Text: C:\Documents and Settings\timo.hursti\Mina
dokument\Projekt\IBS >Error when attempting to get a data file.

Any ideas concerning what this is about and what I should do? Any hel
would be appreciated.

Thanks,

Timo Hursti

Uppsala University

=====================
To manage your subscription to SPSSX-L, send a message to
[hidden email] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD

[SPSS Support]

Hi Timo,

I think we'll need to see one of the files in question.

David Nichols

-----Original Message-----
From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Timo Hursti
Sent: Monday, April 06, 2009 6:41 AM
To: [hidden email]
Subject: [SPSSX-L] Error # 1405

SPSS 17.0 won't open certain data files I've received from other users, the other users don't experience any problems with these files. I get the following error message:

GET   FILE='C:\Documents and Settings\timo.hursti\Mina
dokument\Projekt\IBS 2\SPSSnyfilK&J.sav'. >Error.  Command name: GET FILE >Invalid SPSS Statistics system file: C:\Documents and Settings\timo.hursti\Mina dokument\Projekt\IBS 2\SPSSnyfilK&J.sav
(DATA1204) >This command not executed. >Error # 1405 in column 8.  Text: C:\Documents and Settings\timo.hursti\Mina dokument\Projekt\IBS >Error when attempting to get a data file.

Any ideas concerning what this is about and what I should do? Any hel would be appreciated.

Thanks,

Timo Hursti

Uppsala University

=====================
To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD

=====================
To manage your subscription to SPSSX-L, send a message to
[hidden email] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD

[dmarinova]

Hi,

I have the same problem, and I was wondering if you were able to resolve this issue and how.

Thanks!

SPSS Support wrote

Hi Timo,

I think we'll need to see one of the files in question.

David Nichols

-----Original Message-----
From: SPSSX(r) Discussion [mailto:[e-mail]] On Behalf Of Timo Hursti
Sent: Monday, April 06, 2009 6:41 AM
To: [e-mail]
Subject: [SPSSX-L] Error # 1405

SPSS 17.0 won't open certain data files I've received from other users, the other users don't experience any problems with these files. I get the following error message:

GET   FILE='C:\Documents and Settings\timo.hursti\Mina
dokument\Projekt\IBS 2\SPSSnyfilK&J.sav'. >Error.  Command name: GET FILE >Invalid SPSS Statistics system file: C:\Documents and Settings\timo.hursti\Mina dokument\Projekt\IBS 2\SPSSnyfilK&J.sav
(DATA1204) >This command not executed. >Error # 1405 in column 8.  Text: C:\Documents and Settings\timo.hursti\Mina dokument\Projekt\IBS >Error when attempting to get a data file.

Any ideas concerning what this is about and what I should do? Any hel would be appreciated.

Thanks,

Timo Hursti

Uppsala University

=====================
To manage your subscription to SPSSX-L, send a message to [e-mail] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD

=====================
To manage your subscription to SPSSX-L, send a message to
[e-mail] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD

[SPSS Support]

Hi,

Yes, the following text extracted from resolution 76623 allowed Timo to work around this issue:

This error occurs when a file was created on a non-intel based processor machine such as Mac PowerPC. When this file is opened on a computer with an Intel based processor and this file has a string variable, whose name length is greater than 8 characters and where value labels are attached to that long string variable.

It makes such files unreadable on processors with a byte order different from the writing processor.  Since Intel's is the only common little-endian architecture, the boundary is between Intel-architecture processors and all others (e.g., Mac PPC, Solaris, AIX).  In a client-server hookup, it's the server's architecture that matters.

As a workaround, please open this file on the system it was created and autorecode the string variables.


David Nichols

-----Original Message-----
From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of dmarinova
Sent: Wednesday, September 02, 2009 1:47 PM
To: [hidden email]
Subject: Re: [SPSSX-L] Error # 1405

Hi,

I have the same problem, and I was wondering if you were able to resolve this issue and how.

Thanks!


SPSS Support wrote:

>
> Hi Timo,
>
> I think we'll need to see one of the files in question.
>
> David Nichols
>
> -----Original Message-----
> From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf
> Of Timo Hursti
> Sent: Monday, April 06, 2009 6:41 AM
> To: [hidden email]
> Subject: [SPSSX-L] Error # 1405
>
> SPSS 17.0 won't open certain data files I've received from other
> users, the other users don't experience any problems with these files.
> I get the following error message:
>
> GET   FILE='C:\Documents and Settings\timo.hursti\Mina
> dokument\Projekt\IBS 2\SPSSnyfilK&J.sav'. >Error.  Command name: GET
> FILE
> >Invalid SPSS Statistics system file: C:\Documents and
> Settings\timo.hursti\Mina dokument\Projekt\IBS 2\SPSSnyfilK&J.sav
> (DATA1204) >This command not executed. >Error # 1405 in column 8.  Text:
> C:\Documents and Settings\timo.hursti\Mina dokument\Projekt\IBS >Error
> when attempting to get a data file.
>
> Any ideas concerning what this is about and what I should do? Any hel
> would be appreciated.
>
> Thanks,
>
> Timo Hursti
>
> Uppsala University
>
> =====================
> To manage your subscription to SPSSX-L, send a message to
> [hidden email] (not to SPSSX-L), with no body text except
> the command. To leave the list, send the command SIGNOFF SPSSX-L For a
> list of commands to manage subscriptions, send the command INFO
> REFCARD
>
> =====================
> To manage your subscription to SPSSX-L, send a message to
> [hidden email] (not to SPSSX-L), with no body text except
> the command. To leave the list, send the command SIGNOFF SPSSX-L For a
> list of commands to manage subscriptions, send the command INFO
> REFCARD
>
>

--
View this message in context: http://www.nabble.com/Error---1405-tp22907113p25263426.html
Sent from the SPSSX Discussion mailing list archive at Nabble.com.

=====================
To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD

=====================
To manage your subscription to SPSSX-L, send a message to
[hidden email] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD

[Bruce Weaver]

SPSS Support wrote

Hi,

Yes, the following text extracted from resolution 76623 allowed Timo to work around this issue:

This error occurs when a file was created on a non-intel based processor machine such as Mac PowerPC. When this file is opened on a computer with an Intel based processor and this file has a string variable, whose name length is greater than 8 characters and where value labels are attached to that long string variable.

It makes such files unreadable on processors with a byte order different from the writing processor.  Since Intel's is the only common little-endian architecture, the boundary is between Intel-architecture processors and all others (e.g., Mac PPC, Solaris, AIX).  In a client-server hookup, it's the server's architecture that matters.

As a workaround, please open this file on the system it was created and autorecode the string variables.


David Nichols

Hi David.  I forwarded this info to some colleagues who work with a group that uses a mixture of Windows & Apple machines, and received a reply from one of them with some questions I couldn't answer.  So here they are for your consideration.  

--- Response from my colleague ---

I've read the report and the proposed work around but I don't understand  something.  The diagnosis stated that the non-Intel-originated file has to have a string variable with a long name (more than 8 characters), for which value labels have been defined.

Not clear whether the secondary source of the problem is owning to the string variable's long name (after all, long names are acceptable) or to the values assigned to the variable being long string values (more than 8 characters) or the value labels.  Long string values are acceptable. As are value labels, up to 40 characters.  So I'm uncertain about the file characteristics that give rise to the non-Intel-to-Intel problem.

The workaround suggests auto-recoding the values assigned to the string variable.  Again, I'm uncertain how that will help.  Auto-recode will create a numeric variable with numeric values and value labels.  But unless the user then deletes the offending string variable, how will auto-recoding resolve anything?

--- End of Response ---

Thanks,
Bruce

[SPSS Support]

Hi Bruce,

Here's a more precise statement of the issue:

This problem has been fixed for Release 17. It occurred when attempting to read a file using an Intel-based processor that was written on a different type of processor (e.g., Macintosh PowerPC, Solaris, AIX) if the file contained a long string variable with value labels. (A long string variable is defined as a string variable with declared length greater than 8 bytes. In English, a character is generally represented by a single byte. In some languages, such as Japanese, characters may be represented using two bytes.) In client-server situations, the server architecture is what matters.

On releases prior to 17, you can work around this problem by opening the file on the system where it was created, using AUTORECODE (Transform>Automatic Recode) to create a numeric version of the long-string variable with the original string values as value labels), and deleting the original long-string variable. We apologize for the inconvenience.

So there was a red herring in there originally (it's having a long-string variable with value labels, not anything having to do with the length of the variable name), and yes, you do need to delete that variable after the AUTORECODE before trying to open the file on the Intel-based machine.

David Nichols

-----Original Message-----
From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Bruce Weaver
Sent: Thursday, September 03, 2009 1:49 PM
To: [hidden email]
Subject: Re: [SPSSX-L] Error # 1405

SPSS Support wrote:

>
> Hi,
>
> Yes, the following text extracted from resolution 76623 allowed Timo
> to work around this issue:
>
> This error occurs when a file was created on a non-intel based
> processor machine such as Mac PowerPC. When this file is opened on a
> computer with an Intel based processor and this file has a string
> variable, whose name length is greater than 8 characters and where
> value labels are attached to that long string variable.
>
> It makes such files unreadable on processors with a byte order
> different from the writing processor.  Since Intel's is the only
> common little-endian architecture, the boundary is between
> Intel-architecture processors and all others (e.g., Mac PPC, Solaris,
> AIX).  In a client-server hookup, it's the server's architecture that matters.
>
> As a workaround, please open this file on the system it was created
> and autorecode the string variables.
>
>
> David Nichols
>
>

Hi David.  I forwarded this info to some colleagues who work with a group that uses a mixture of Windows & Apple machines, and received a reply from one of them with some questions I couldn't answer.  So here they are for your consideration.

--- Response from my colleague ---

I've read the report and the proposed work around but I don't understand something.  The diagnosis stated that the non-Intel-originated file has to have a string variable with a long name (more than 8 characters), for which value labels have been defined.

Not clear whether the secondary source of the problem is owning to the string variable's long name (after all, long names are acceptable) or to the values assigned to the variable being long string values (more than 8
characters) or the value labels.  Long string values are acceptable. As are value labels, up to 40 characters.  So I'm uncertain about the file characteristics that give rise to the non-Intel-to-Intel problem.

The workaround suggests auto-recoding the values assigned to the string variable.  Again, I'm uncertain how that will help.  Auto-recode will create a numeric variable with numeric values and value labels.  But unless the user then deletes the offending string variable, how will auto-recoding resolve anything?

--- End of Response ---

Thanks,
Bruce


-----
--
Bruce Weaver
[hidden email]
http://sites.google.com/a/lakeheadu.ca/bweaver/
"When all else fails, RTFM."

NOTE:  My Hotmail account is for posting only, and is not monitored regularly.
If you wish to send me an e-mail, please use the address shown in my sig file.
--
View this message in context: http://www.nabble.com/Error---1405-tp22907113p25281974.html
Sent from the SPSSX Discussion mailing list archive at Nabble.com.

=====================
To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD

=====================
To manage your subscription to SPSSX-L, send a message to
[hidden email] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD

[Bruce Weaver]

Thanks very much, David.  I'll pass this along to my colleague.

Cheers,
Bruce

SPSS Support wrote

Hi Bruce,

Here's a more precise statement of the issue:

This problem has been fixed for Release 17. It occurred when attempting to read a file using an Intel-based processor that was written on a different type of processor (e.g., Macintosh PowerPC, Solaris, AIX) if the file contained a long string variable with value labels. (A long string variable is defined as a string variable with declared length greater than 8 bytes. In English, a character is generally represented by a single byte. In some languages, such as Japanese, characters may be represented using two bytes.) In client-server situations, the server architecture is what matters.

On releases prior to 17, you can work around this problem by opening the file on the system where it was created, using AUTORECODE (Transform>Automatic Recode) to create a numeric version of the long-string variable with the original string values as value labels), and deleting the original long-string variable. We apologize for the inconvenience.

So there was a red herring in there originally (it's having a long-string variable with value labels, not anything having to do with the length of the variable name), and yes, you do need to delete that variable after the AUTORECODE before trying to open the file on the Intel-based machine.

David Nichols

-----Original Message-----
From: SPSSX(r) Discussion [mailto:[e-mail]] On Behalf Of Bruce Weaver
Sent: Thursday, September 03, 2009 1:49 PM
To: [e-mail]
Subject: Re: [SPSSX-L] Error # 1405

SPSS Support wrote:
>
> Hi,
>
> Yes, the following text extracted from resolution 76623 allowed Timo
> to work around this issue:
>
> This error occurs when a file was created on a non-intel based
> processor machine such as Mac PowerPC. When this file is opened on a
> computer with an Intel based processor and this file has a string
> variable, whose name length is greater than 8 characters and where
> value labels are attached to that long string variable.
>
> It makes such files unreadable on processors with a byte order
> different from the writing processor.  Since Intel's is the only
> common little-endian architecture, the boundary is between
> Intel-architecture processors and all others (e.g., Mac PPC, Solaris,
> AIX).  In a client-server hookup, it's the server's architecture that matters.
>
> As a workaround, please open this file on the system it was created
> and autorecode the string variables.
>
>
> David Nichols
>
>

Hi David.  I forwarded this info to some colleagues who work with a group that uses a mixture of Windows & Apple machines, and received a reply from one of them with some questions I couldn't answer.  So here they are for your consideration.

--- Response from my colleague ---

I've read the report and the proposed work around but I don't understand something.  The diagnosis stated that the non-Intel-originated file has to have a string variable with a long name (more than 8 characters), for which value labels have been defined.

Not clear whether the secondary source of the problem is owning to the string variable's long name (after all, long names are acceptable) or to the values assigned to the variable being long string values (more than 8
characters) or the value labels.  Long string values are acceptable. As are value labels, up to 40 characters.  So I'm uncertain about the file characteristics that give rise to the non-Intel-to-Intel problem.

The workaround suggests auto-recoding the values assigned to the string variable.  Again, I'm uncertain how that will help.  Auto-recode will create a numeric variable with numeric values and value labels.  But unless the user then deletes the offending string variable, how will auto-recoding resolve anything?

--- End of Response ---

Thanks,
Bruce


-----
--
Bruce Weaver
[e-mail]
http://sites.google.com/a/lakeheadu.ca/bweaver/
"When all else fails, RTFM."

NOTE:  My Hotmail account is for posting only, and is not monitored regularly.
If you wish to send me an e-mail, please use the address shown in my sig file.
--
View this message in context: http://www.nabble.com/Error---1405-tp22907113p25281974.html
Sent from the SPSSX Discussion mailing list archive at Nabble.com.

=====================
To manage your subscription to SPSSX-L, send a message to [e-mail] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD

=====================
To manage your subscription to SPSSX-L, send a message to
[e-mail] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD