I can't say for sure you are encountering the same root issue, but we did fix a bug in EG 7.1 with a similar symptom.  I think there is a reasonable likelihood the problem you are seeing is caused by the same root issue, which was addressed in EG 7.1.   I'm not aware of any workarounds in EG 6.1.  The unexpected error leads to the query being in an unexpected state, which is not handled gracefully when deserialized. ... View more

Hi @digitmaster,   This issue has been fixed in our upcoming EG 7.12 update, which will be available soon.  EG 7.11 will notify you when 7.12 is available and will allow you to update with one click.   Casey ... View more

As an aside...   You can create conditions in EG process flows to control the order of execution with if/then/else logic.  These EG process flow conditions can be based on macro variable values.  So, storing the "missing value present" result in a macro variable would allow you to use it in a condition in an EG process flow.  For example, if you wanted to use the point-and-click Export as a Step in Project task to export the data rather than code (some do, some don't), you could use the macro variable value (which would reflect whether missing values were present) to decide whether to run the task during a process flow or project run.   Note: EG process flow conditions are only applicable when executed in the context of EG.  So, if you plan to execute outside of EG, you should stick with code to do the conditional logic.  For programmers, the code is often easier anyway. ... View more

Here is what I came up with, but I like @RW9's solution *much* better for brevity and efficiency, assuming you don't need the actual count of missing values:   /* count the number of missing values and store result in a macro variable */ proc sql noprint; select count(case when MISSING(col1) then "count me" end) into :missingCount from mydata; quit; /* if one or more missing values found, export */ %macro exportIfMissing; %if &missingCount > 0 %then %do; %put NOTE: Missing values found, so exporting to Excel...; proc export data=mydata outfile="c:\temp\mydata.xlsx"; run; %end; %else %do; %put NOTE: No missing values found. So, not exporting; %end; %mend; %exportIfMissing;   ... View more

It has been fixed in our next release, which we expect to be available in the first quarter of 2016. ... View more

While you can open the same external content (ex. programs, etc.) in either, moving projects between Enterprise Guide and SAS Studio (without manually recreating) is not currently supported.  We recognize the value this capability would provide and are exploring adding it in a future release. ... View more

Yes, EG 4.305 or later (ex. 5.1, 6.1, 7.1) can be installed on 32-bit Windows 7.  (Starting in EG 5.1, there is a 32-bit and a 64-bit version of EG.)   Here is the EG 4.305 system requirements doc, where Windows 7 support was first explicitly added: http://support.sas.com/documentation/installcenter/en/ikeguidesr/64672/PDF/default/sreq.pdf ... View more

This is an issue (in EG 7.1) that we are aware of and fixed in EG 7.11. As originally noted, you can workaround the issue in EG 7.1 with the one-time step of selecting "Enable Logging" or "Reset to Defaults" in Tools->Options->Application Logging. After doing that, the exception does not happen anymore, even when you turn off logging (uncheck "Enable Logging") to get back to the original state. ... View more

We are aware of certain scenarios in which the editor slows down when the Autocomplete feature is on and you are working with large programs.  The scenarios we are aware of were improved in 7.11. Here is the related SAS Note: 54754 - In SAS® Enterprise Guide®, the Enhanced Editor might respond very slowly when the autocompletion feature is enabled ... View more

What specific version of EG do you have?  (What appears in Help->About?)  There was an issue in EG 7.1 that presented a similar error, but it was fixed in 7.11. ... View more