macro and script problems in SPSS 18

[Andrew F. Hayes]

I am curious to know whether anyone has had problems getting macros or
scripts written in SPSS 14-17 to work in SPSS 18.  I have a number of
popular macros (http://www.comm.ohio-state.edu/ahayes/macros.htm) that are
widely used but I am getting reports of problems with people who move to
SPSS 18.  The most common error I am hearing about is a complete failure of
the processor whenever the macros execute.  Typically, the error reads

"The PASW Statistics Processor is terminating due to a catastrophic error.
Any working data file is lost.  A program error has occurred: Attempt to
free unallocated memory. Please note the circumstance under which this error
occurred, attempting to replicate it if possible, and then notify Technical
Support.  Restart the processor?"

The macros work just fine--same data, same command syntax, and so forth--on
prior versions.  It is only SPSS 18 that is producing this error.

I have seen the SPSS 18 Syntax Reference manual and it seems that there have
been no changes to the macro definition or MATRIX commands that would
produce these kinds of errors.

Some users of my scripts get errors that read

"Python scripts cannot be edited.  Please check whether Python and the
Python Integration Plug-In have been installed."

My scripts are not written in Python.

=====================
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]

Andrew F. Hayes wrote

I am curious to know whether anyone has had problems getting macros or
scripts written in SPSS 14-17 to work in SPSS 18.  I have a number of
popular macros (http://www.comm.ohio-state.edu/ahayes/macros.htm) that are
widely used but I am getting reports of problems with people who move to
SPSS 18.  The most common error I am hearing about is a complete failure of
the processor whenever the macros execute.  Typically, the error reads

"The PASW Statistics Processor is terminating due to a catastrophic error.
Any working data file is lost.  A program error has occurred: Attempt to
free unallocated memory. Please note the circumstance under which this error
occurred, attempting to replicate it if possible, and then notify Technical
Support.  Restart the processor?"

The macros work just fine--same data, same command syntax, and so forth--on
prior versions.  It is only SPSS 18 that is producing this error.

I have seen the SPSS 18 Syntax Reference manual and it seems that there have
been no changes to the macro definition or MATRIX commands that would
produce these kinds of errors.

Some users of my scripts get errors that read

"Python scripts cannot be edited.  Please check whether Python and the
Python Integration Plug-In have been installed."

My scripts are not written in Python.

Someone with a suspicious nature might think that SPSS (or is it still PAWS?) is trying to kill the macro language and force everyone to switch to Python.  :-|

[SPSS Support-2]

Hi Andrew,

To the best of my knowledge, we have not had an unusual number of reports of problems running macros or scripts in Release 18, and I don't recall hearing about catastrophic errors. I've run hcreg.sps and meng.sps, and both syntax file macro version (sobel_spss.sps) and script version (sobel_spss.sbs) on both 18.0.0 and 18.0.1 and I have no problems with any of them.

I've opened a support case and will contact you individually to see about getting more specific information to follow up and see if we can reproduce and get this addressed.

David Nichols

> From:
>
> "Andrew F. Hayes" <[hidden email]>
>
> To:
>
> [hidden email]
>
> Date:
>
> 12/21/2009 12:25 PM
>
> Subject:
>
> macro and script problems in SPSS 18
>
> Sent by:
>
> "SPSSX(r) Discussion" <[hidden email]>
>
> I am curious to know whether anyone has had problems getting macros or
> scripts written in SPSS 14-17 to work in SPSS 18.  I have a number of
> popular macros (http://www.comm.ohio-state.edu/ahayes/macros.htm) that are
> widely used but I am getting reports of problems with people who move to
> SPSS 18.  The most common error I am hearing about is a complete failure of
> the processor whenever the macros execute.  Typically, the error reads
>
> "The PASW Statistics Processor is terminating due to a catastrophic error.
> Any working data file is lost.  A program error has occurred: Attempt to
> free unallocated memory. Please note the circumstance under which this error
> occurred, attempting to replicate it if possible, and then notify Technical
> Support.  Restart the processor?"
>
> The macros work just fine--same data, same command syntax, and so forth--on
> prior versions.  It is only SPSS 18 that is producing this error.
>
> I have seen the SPSS 18 Syntax Reference manual and it seems that there have
> been no changes to the macro definition or MATRIX commands that would
> produce these kinds of errors.
>
> Some users of my scripts get errors that read
>
> "Python scripts cannot be edited.  Please check whether Python and the
> Python Integration Plug-In have been installed."
>
> My scripts are not written in Python.
>
> =====================
> 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

[Gyorgy Bea]

Hello,

We are having the same problem when trying to run our scripts in SPSS 18. The scripts are working without problems in the earlier releases, and they are working even in the trial version of SPSS 18.

The Error message is:
"WWBProcessor has encountered a problem and needs to close. We are sorry for the inconvenience.

If you were in the middle of something, the information you were working on might be lost."

Thank you for looking into this.
Regards,
Beata Gyorgy

---

From: SPSS Support <[hidden email]>
To: [hidden email]
Sent: Mon, December 21, 2009 10:47:06 PM
Subject: Re: macro and script problems in SPSS 18


Hi Andrew,

To the best of my knowledge, we have not had an unusual number of reports of problems running macros or scripts in Release 18, and I don't recall hearing about catastrophic errors. I've run hcreg.sps and meng.sps, and both syntax file macro version (sobel_spss.sps) and script version (sobel_spss.sbs) on both 18.0.0 and 18.0.1 and I have no problems with any of them.

I've opened a support case and will contact you individually to see about getting more specific information to follow up and see if we can reproduce and get this addressed.

David Nichols

> From:
>
> "Andrew F. Hayes" <[hidden email]>
>
> To:
>
> [hidden email]
>
> Date:
>
> 12/21/2009 12:25 PM
>
> Subject:
>
> macro and script problems in SPSS 18
>
> Sent by:
>
> "SPSSX(r) Discussion" <[hidden email]>
>
> I am curious to know whether anyone has had problems getting macros or
> scripts written in SPSS 14-17 to work in SPSS 18.  I have a number of
> popular macros (http://www.comm.ohio-state.edu/ahayes/macros.htm) that are
> widely used but I am getting reports of problems with people who move to
> SPSS 18.  The most common error I am hearing about is a complete failure of
> the processor whenever the macros execute.  Typically, the error reads
>
> "The PASW Statistics Processor is terminating due to a catastrophic error.
> Any working data file is lost.  A program error has occurred: Attempt to
> free unallocated memory. Please note the circumstance under which this error
> occurred, attempting to replicate it if possible, and then notify Technical
> Support.  Restart the processor?"
>
> The macros work just fine--same data, same command syntax, and so forth--on
> prior versions.  It is only SPSS 18 that is producing this error.
>
> I have seen the SPSS 18 Syntax Reference manual and it seems that there have
> been no changes to the macro definition or MATRIX commands that would
> produce these kinds of errors.
>
> Some users of my scripts get errors that read
>
> "Python scripts cannot be edited.  Please check whether Python and the
> Python Integration Plug-In have been installed."
>
> My scripts are not written in Python.
>
> =====================
> 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-2]

Hi Beata,

I've also opened a support case for you on this. It would be helpful if you could provide us with the data and commands or specifications so we can try to reproduce the problem. I've tried several of the macros and scripts on Releases 18.0.0 and 18.0.1 without being able to reproduce any errors.

David Nichols


"SPSSX(r) Discussion" <[hidden email]> wrote on 12/23/2009 04:10:04 AM:

> [image removed]
>
> Re: macro and script problems in SPSS 18
>
> Gyorgy Bea
>
> to:
>
> SPSSX-L
>
> 12/23/2009 04:14 AM
>
> Sent by:
>
> "SPSSX(r) Discussion" <[hidden email]>
>
> Please respond to Gyorgy Bea
>
> Hello,
>
> We are having the same problem when trying to run our scripts in
> SPSS 18. The scripts are working without problems in the earlier
> releases, and they are working even in the trial version of SPSS 18.
>
> The Error message is:
> "WWBProcessor has encountered a problem and needs to close. We are
> sorry for the inconvenience.
>
> If you were in the middle of something, the information you were
> working on might be lost."
>

> Thank you for looking into this.
> Regards,
> Beata Gyorgy
>
>

> From: SPSS Support <[hidden email]>
> To: [hidden email]
> Sent: Mon, December 21, 2009 10:47:06 PM
> Subject: Re: macro and script problems in SPSS 18
>
>
> Hi Andrew,
>
> To the best of my knowledge, we have not had an unusual number of
> reports of problems running macros or scripts in Release 18, and I
> don't recall hearing about catastrophic errors. I've run hcreg.sps
> and meng.sps, and both syntax file macro version (sobel_spss.sps)
> and script version (sobel_spss.sbs) on both 18.0.0 and 18.0.1 and I
> have no problems with any of them.
>
> I've opened a support case and will contact you individually to see
> about getting more specific information to follow up and see if we
> can reproduce and get this addressed.
>
> David Nichols
>
> > From:
> >
> > "Andrew F. Hayes" <[hidden email]>
> >
> > To:
> >
> > [hidden email]
> >
> > Date:
> >
> > 12/21/2009 12:25 PM
> >
> > Subject:
> >
> > macro and script problems in SPSS 18
> >
> > Sent by:
> >
> > "SPSSX(r) Discussion" <[hidden email]>
> >
> > I am curious to know whether anyone has had problems getting macros or
> > scripts written in SPSS 14-17 to work in SPSS 18.  I have a number of
> > popular macros (http://www.comm.ohio-state.edu/ahayes/macros.htm) that are
> > widely used but I am getting reports of problems with people who move to
> > SPSS 18.  The most common error I am hearing about is a complete failure of
> > the processor whenever the macros execute.  Typically, the error reads
> >
> > "The PASW Statistics Processor is terminating due to a catastrophic error.
> > Any working data file is lost.  A program error has occurred: Attempt to
> > free unallocated memory. Please note the circumstance under which this error
> > occurred, attempting to replicate it if possible, and then notify Technical
> > Support.  Restart the processor?"
> >
> > The macros work just fine--same data, same command syntax, and so forth--on
> > prior versions.  It is only SPSS 18 that is producing this error.
> >
> > I have seen the SPSS 18 Syntax Reference manual and it seems that there have
> > been no changes to the macro definition or MATRIX commands that would
> > produce these kinds of errors.
> >
> > Some users of my scripts get errors that read
> >
> > "Python scripts cannot be edited.  Please check whether Python and the
> > Python Integration Plug-In have been installed."
> >
> > My scripts are not written in Python.
> >
> > =====================
> > 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

[---pinky---]

In my opinion this ist not a problem with the script, but with the syntax.

(1) I can run every script file via File -> Open -> Script without any errors.
(2) I usually also can run syntaxes via dialog boxes, which I created with the Custom Dialog Builder.

But:

(3) Running a syntax containing the script-command, e.g.

script "C:\Programme\SPSSInc\PASWStatistics18\Samples\Change sig to p.wwd".

fails without exception.

(4) It also fails with dialoges described in number (2), if the embedded syntax-file contains any script-command.



From the WWB-Processor I get the error-message ""WWBProcessor has encountered a problem and needs to close. We are sorry for the inconvenience.

If you were in the middle of something, the information you were working on might be lost." *

In the Output-file I find the error-message

"ERROR : (-1073741819) Kein Fehler." **

I encountered the problem in Version 18.0, but also in v 18.01 under Windows XP Professional.

Hints:
*As I use the german Version, I quoted the error message from Gyorgy Bea´s posting above.
** "Kein Fehler" in english means "no error"

[SPSS Support-2]

I was able to run the "Change sig to p" script from a syntax command in the manner that you describe below, using Statistics 18.0.1 on XP Professional. The script ran without error and produced the desired change. I was unable to find a record of a bug or previous cases where running a script from a syntax window produced the error messages that you described. You may want to create a support case from the Support web site at http://support.spss.com to pursue the problem further.

David Matheson
Statistical Support
SPSS, an IBM company

-----

From:	---pinky--- <[hidden email]>
To:	[hidden email]
Date:	01/18/2010 09:39 PM
Subject:	Re: macro and script problems in SPSS 18
Sent by:	"SPSSX(r) Discussion" <[hidden email]>

---

In my opinion this ist not a problem with the script, but with the syntax.

(1) I can run every script file via File -> Open -> Script without any
errors.
(2) I usually also can run syntaxes via dialog boxes, which I created with
the Custom Dialog Builder.

But:

(3) Running a syntax containing the script-command, e.g.

script "C:\Programme\SPSSInc\PASWStatistics18\Samples\Change sig to p.wwd".

fails without exception.

(4) It also fails with dialoges described in number (2), if the embedded
syntax-file contains any script-command.



From the WWB-Processor I get the error-message ""WWBProcessor has
encountered a problem and needs to close. We are sorry for the
inconvenience.

If you were in the middle of something, the information you were working on
might be lost." *

In the Output-file I find the error-message

"ERROR : (-1073741819) Kein Fehler." **

I encountered the problem in Version 18.0, but also in v 18.01 under Windows
XP Professional.

Hints:
*As I use the german Version, I quoted the error message from Gyorgy Bea´s
posting above.
** "Kein Fehler" in english means "no error"

--
View this message in context: http://old.nabble.com/macro-and-script-problems-in-SPSS-18-tp26878097p27214028.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

[cvdg]

I have the same problem: the script that was made in SPSS version 15 does not work in version 18 or19. I am not a pro when it comes to scripting, so I have no idea what the prolem might be. Does anyone know the solution?

[Tom1234]

2 years and 3 versions later ... (THREAD NECROMANCY)
This problem still persists, syntax that worked fine in earlier versions no longer works (it still works in the older versions)
My script simply changed all the tables in the output window to a single style, rotated inner column labels and set the columns to 'autofit'.
I've also noticed that since 18/19 the way in which SPSS displays the result of Syntax has changed (for the worse) it seems less clear and I generally have to write syntax in the old format and do the output on version 15, despite exactly matching the settings from 15 to 20, (I changed the page setup, cell spacing, and table look and it still looks different from the one in version 15 when printed from the same printer.)

[Jon K Peck]

It is pretty hard to respond to this post, since there isn't a statement of exactly what "this problem" is, what you mean by "no longer works", what you mean by the syntax display being less clear, and what is different about the output that matters.  Have you ever discussed these issues with Technical Support?


Jon Peck (no "h") aka Kim
Senior Software Engineer, IBM
[hidden email]
new phone: [phone]




From:        Tom1234 <[hidden email]>
To:        [hidden email],
Date:        03/04/2013 08:23 AM
Subject:        Re: [SPSSX-L] macro and script problems in SPSS 18
Sent by:        "SPSSX(r) Discussion" <[hidden email]>

---

2 years and 3 versions later ... (THREAD NECROMANCY)
This problem still persists, syntax that worked fine in earlier versions no
longer works (it still works in the older versions)
My script simply changed all the tables in the output window to a single
style, rotated inner column labels and set the columns to 'autofit'.
I've also noticed that since 18/19 the way in which SPSS displays the result
of Syntax has changed (for the worse) it seems less clear and I generally
have to write syntax in the old format and do the output on version 15,
despite exactly matching the settings from 15 to 20, (I changed the page
setup, cell spacing, and table look and it still looks different from the
one in version 15 when printed from the same printer.)



-----

"Lo there do I see my father. Lo there do I see my mother and my sisters and my brothers. Lo there do I see the line of my people, back to the beginning. Lo, they do call to me, they bid me take my place among them, in the Halls of Valhalla, where the brave may live...forever."
--
View this message in context: http://spssx-discussion.1045642.n5.nabble.com/macro-and-script-problems-in-SPSS-18-tp1087993p5718350.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

[Tom1234]

The problem is shown higher in the thread (if you've only seen this in the mailing list and not the forum then I can understand your confusion)

Essentially whenever I attempt to run a script (That I have modified from a version 15 script as per the version change guidelines that spss released) the script fails to execute and throws this Error message:
"WWBProcessor has encountered a problem and needs to close. We are sorry for the inconvenience.
I've checked over and over for errors in the code and as per the language its written in there are none.
The script works perfectly in 15, with no errors of any kind.

I thought it pointless to contact technical support as the way spss displays the output is seemingly part of the program and not something that is easily modified and/or matched to the earlier versions.

The main issue is the way that tabulated data is displayed on a printable page, in version 15 the printed tables are much easier to read and fit to the page much more effectively, however in version 20, despite changing all the settings to match those I have in version 15 including the table look (and every setting within that), the document prints out differently.

[Dittfurth, Monica]

I will be out of the office until Thursday, March 7th. If you have an urgent need or request before I return, please email [hidden email].

 

Thanks,

Monica

 

[David Marso]

Maybe it would help if you attached the problematic script?
Can you isolate the line where it fails?
Probably would need the sample output too.
---
Printing?  I haven't printed anything in months so I can't comment.
---

Tom1234 wrote

The problem is shown higher in the thread (if you've only seen this in the mailing list and not the forum then I can understand your confusion)

Essentially whenever I attempt to run a script (That I have modified from a version 15 script as per the version change guidelines that spss released) the script fails to execute and throws this Error message:
"WWBProcessor has encountered a problem and needs to close. We are sorry for the inconvenience.
I've checked over and over for errors in the code and as per the language its written in there are none.
The script works perfectly in 15, with no errors of any kind.

I thought it pointless to contact technical support as the way spss displays the output is seemingly part of the program and not something that is easily modified and/or matched to the earlier versions.

The main issue is the way that tabulated data is displayed on a printable page, in version 15 the printed tables are much easier to read and fit to the page much more effectively, however in version 20, despite changing all the settings to match those I have in version 15 including the table look (and every setting within that), the document prints out differently.

[Tom1234]

David Marso wrote

Maybe it would help if you attached the problematic script?

Here is the script that is causing problems (although none of the scripts I have will work on V20 any more) I originally got this script from the SPSS tools website.

Option Explicit

Sub Main
'BEGIN DESCRIPTION
'This script changes all tabs to the same 'Tablelook' style.  You will be prompted to choose the tablelook file.
'END DESCRIPTION
'******************
''This script assumes that objSpssApp ist the currently running
'SPSS-Application and assigns every existing Pivot Table
'in the Output Navigator a new TableLook which can be selected
'from a Dialog box. Hidden tables will also be affected.
'Originally Created by SPSS Germany. Author: Arnd Winter.
'******************
'This script is written in the BASIC revision 'WinWrap Basic' code copied from VB or other basic languages may have to be modified to function properly.

On Error GoTo Bye

' Variable Declaration
Dim objOutputDoc As ISpssOutputDoc 'Declares the Output variable
Set objOutputDoc = objSpssApp.GetDesignatedOutputDoc 'Assigns currently active output to Output variable
Dim strAppPath As String
Dim objOutputItems As ISpssItems 'variable defining every item in the current output window
Dim objOutputItem As ISpssItem 'variable defining the current item
Dim objPivotTable As PivotTable
Dim varStrLook As String
Set objOutputItems=objOutputDoc.Items
Dim i As Integer 'for loops we need an INT variable that will be counted against the number of instances 'i' is standard notation
' Find out SPSS Directory
Dim intCount As Integer 'declare the variable that will store the number of instances

strAppPath = objSpssApp.GetSPSSPath

' Select TableLook

'The Parameters you must enter into the GetFilePath() function are as follows:
'(Optional)Firstly you enter the initial file name (if none is required use an asterisk * and the file extention, or *.*)
'(Optional)The second part is the file extention expected, you can choose multiple filetypes if you seperate them with a semi-colon ;
'(Optional)The third parameter is the directory where the file should be opened.(default - Current path)
'The fourth parametre is the Title of the prompt, which should be enclosed in speech marks.
'The Final parametre is the 'Option'
'0 Only allow the user to select a file that exists.
'1 Confirm creation when the user selects a file that does not exist.
'2 Allow the user to select any file whether it exists or not.
'3 Confirm overwrite when the user selects a file that exists.
'+4 Selecting a different directory changes the application's current directory.
'For more detailed information visit the WWB website.
' http://www.winwrap.com/web/basic/language/?p=doc_getfilepath__func.htm
varStrLook = GetFilePath$("*.stt","stt",strAppPath,"Select Tablelook and confirm with Save.",4)

' If user presses Cancel or selected a file with the wrong file type then exit script
If (Len(varStrLook)= 0) Or (Right(varStrLook,3)<>"stt") Then
        Exit Sub
End If

' Loop which assigns a new TableLook to all existing Tables.
intCount = objOutputItems.Count 'Assigns the total number of output items to the count-marker
For i = 0 To intCount-1 'Start loop
        Set objOutputItem=objOutputItems.GetItem(i) 'Get current item
        If objOutputItem.SPSSType=SPSSPivot Then 'If the item is a pivot table then...
                Set objPivotTable=objOutputItem.ActivateTable 'Activate the table for editing
                objPivotTable.TableLook = varStrLook 'Apply the earlier selected table look.
                objPivotTable.RotateColumnLabels=True 'Rotate collumn lables
                objOutputItem.Deactivate 'Confirm changes and deactivate the table
        End If
Next 'End loop

Bye:
End Sub

David Marso wrote

Can you isolate the line where it fails?

When I use the step in debug function the code gets to line 20 -
Set objOutputDoc = objSpssApp.GetDesignatedOutputDoc 'Assigns currently active output to Output variable

David Marso wrote

Probably would need the sample output too.

I'll see if I can rustle something up and grab a screeny of it later, the difference is definitely noticeable