"Invalid object specified to bridge protocol engine" error

[Nietzsche]

Hi I am doing SAS Programming 1 Essentials

I ran the following code

proc print data=pg1.storm_summary;
where maxwindmph>156 or minpressure <920;
run;

and got the following error. I am very certain that there is nothing with my code as I am following the instruction video. I think this is a error or crash on the SAS Studio backend side? Just want to confirm.

here is the log with 70 errors

77        

 78        

 79         OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;

 ERROR:  An exception has been encountered.

 Please contact technical support and provide them with the following traceback information:

 The SAS task name is [OBJECT_E]

 Segmentation Violation

 Traceback of the Exception:

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/sas(+0x16844e) [0x55999c74d44e]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/sas(+0x4ee1f) [0x55999c633e1f]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7f835c3efac4]

 /lib64/libpthread.so.0(+0xf630) [0x7f835da18630]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/saspdpdf(__intel_ssse3_rep_memcpy+0xb8) [0x7f82fa039958]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/saspdpdf(+0xa6897) [0x7f82f9fea897]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/saspdpdf(setGroupStructureValues+0xeba) [0x7f82f9fdf73a]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/saspdpdf(+0xafc56) [0x7f82f9ff3c56]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/saspdpdf(parsePdfElements+0x1118) [0x7f82f9ff2f38]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/saspdpdf(processAccessibilityValues+0x3b) [0x7f82f9ff1deb]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/saspdpdf(yugextn+0x2a8) [0x7f82f9f6ed38]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saspso(render_page+0xe68) [0x7f82fa466ad8]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saspso(+0x229f1) [0x7f82fa4659f1]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saspso(wobmth+0x57) [0x7f82fa4d5567]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saspso(+0x35453) [0x7f82fa478453]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saspso(wobmth+0x57) [0x7f82fa4d5567]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saspso(+0xedb3) [0x7f82fa451db3]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/sasods(wobmth+0x57) [0x7f82ffa4fde7]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/sasods(+0x10e5c2) [0x7f82ff9095c2]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/sasodst(wobmth+0x57) [0x7f82ff3a5447]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/sasodst(+0x11285) [0x7f82ff3a4285]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/sasods(wobmth+0x57) [0x7f82ffa4fde7]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/sasods(+0x151729) [0x7f82ff94c729]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/sasxshel(ysprstm+0xbf8) [0x7f8342cf6288]

 ERROR:  An exception has been encountered.

 Please contact technical support and provide them with the following traceback information:

 The SAS task name is [OBJECT_E]

 Segmentation Violation

 ERROR:  An exception has been encountered.

 Please contact technical support and provide them with the following traceback information:

 The SAS task name is [OBJECT_E]

 Segmentation Violation

 71         proc print data=pg1.storm_summary;

 72        

 73        

 74         where maxwindmph>156 or minpressure <920;

 75        

 76         run;

 ERROR:  An exception has been encountered.

 Please contact technical support and provide them with the following traceback information:

 The SAS task name is [PRINT (2]

 Segmentation Violation

 Traceback of the Exception:

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/sas(+0x16844e) [0x55b43023844e]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/sas(+0x4ee1f) [0x55b43011ee1f]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7f3ccd053ac4]

 /lib64/libpthread.so.0(+0xf630) [0x7f3cce67c630]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/saspdpdf(__intel_ssse3_rep_memcpy+0xb8) [0x7f3c6e321958]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/saspdpdf(+0xa6897) [0x7f3c6e2d2897]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/saspdpdf(setGroupStructureValues+0xeba) [0x7f3c6e2c773a]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/saspdpdf(+0xafc56) [0x7f3c6e2dbc56]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/saspdpdf(parsePdfElements+0x1118) [0x7f3c6e2daf38]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/saspdpdf(processAccessibilityValues+0x3b) [0x7f3c6e2d9deb]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/saspdpdf(yugextn+0x2a8) [0x7f3c6e256d38]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saspso(render_page+0xe68) [0x7f3c6e74ead8]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saspso(place_+0x3aae) [0x7f3c6e75de4e]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saspso(+0x4603b) [0x7f3c6e77103b]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saspso(+0x44172) [0x7f3c6e76f172]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saspso(+0x432b7) [0x7f3c6e76e2b7]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saspso(wobmth+0x57) [0x7f3c6e7bd567]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saspso(+0x481a1) [0x7f3c6e7731a1]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/sasmrk(wobmth+0x57) [0x7f3c7197c057]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/sasmrk(+0x1b863) [0x7f3c71876863]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saspso(wobmth+0x57) [0x7f3c6e7bd567]

 /pbr/sfw/sas/940/SASFoundation/9.4/sasexe/saspso(+0x2b7f1) [0x7f3c6e7567f1]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/sasprt7(wobmth+0x57) [0x7f3c669aa8d7]

 /pbr/sfw/sas/940/SASFoundation/9.4/dbcs/sasexe/sasprt7(+0x1385e) [0x7f3c669a585e]

 NOTE: The SAS System stopped processing this step because of errors.

 ERROR:  An exception has been encountered.

 Please contact technical support and provide them with the following traceback information:

 The SAS task name is [PRINT (2]

 Segmentation Violation

 NOTE: There were 359 observations read from the data set PG1.STORM_SUMMARY.

       WHERE (maxwindmph>156) or (minpressure<920);

 NOTE: PROCEDURE PRINT used (Total process time):

       real time           0.95 seconds

       user cpu time       0.96 seconds

       system cpu time     0.00 seconds

       memory              38432.06k

       OS Memory           65072.00k

       Timestamp           15/10/2022 09:12:40 AM

       Step Count                        36  Switch Count  6

       Page Faults                       0

       Page Reclaims                     10272

       Page Swaps                        0

       Voluntary Context Switches        22

       Involuntary Context Switches      3

       Block Input Operations            0

       Block Output Operations           544

User: u62043935

Messages: 87

[Nietzsche]

just an update

if I run

proc print data=pg1.storm_summary;
where maxwindmph>156 or 0<minpressure <920;
run;

basically just adding "minpressure" to be between 0 and 920, the SAS Studio runs fine with no error. But removing  "0<" from the code, SAS Studio crashes.

here is the log

1 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;

70

71 proc print data=pg1.storm_summary;

72

73

74 where maxwindmph>156 or 0<minpressure <920;

75

76 run;

NOTE: There were 161 observations read from the data set PG1.STORM_SUMMARY.

WHERE (maxwindmph>156) or (minpressure>0 and minpressure<920);

NOTE: PROCEDURE PRINT used (Total process time):

real time 0.57 seconds

user cpu time 0.56 seconds

system cpu time 0.01 seconds

memory 30188.28k

OS Memory 56624.00k

Timestamp 15/10/2022 09:24:36 AM

Step Count 78 Switch Count 3

Page Faults 0

Page Reclaims 7249

Page Swaps 0

Voluntary Context Switches 17

Involuntary Context Switches 1

Block Input Operations 0

Block Output Operations 376

77

78

79 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;

90

---

[dxiao2017]

Hi @Nietzsche , I happened to read your "certification log" post, I think some of your posts are very interesting. I have also passed the base exam and want to take the adv. exam in near future (and get a job). I encountered same disconnection problem for my SAS OnDemand for academics (signed out and got error message every 5 seconds, which drive me mad, the problem gets better now and I do not think I can figure out the reason). 

And I happened to read this one, I have no idea what was going on with your log message, the only issue I would like to mention is that, the syntax of your code is not correct for the where statement:

proc print data=pg1.storm_summary;
where maxwindmph>156 or 0<minpressure <920;
run;

The correct syntax (of the where statement), the log, and the output are as follows, when there is an "or" condition in your where statement, parentheses are needed:

the code

proc print data=pg1.storm_summary;
   where (maxwindmph>156 or 0<minpressure <920);
run;

the log

NOTE: There were 161 observations read from the data set PG1.STORM_SUMMARY.
       WHERE (maxwindmph>156) or (minpressure>0 and minpressure<920);

the output (rows with maxwindmph>156 or 0<minpressure<920 are printed)

[dxiao2017]

I made a mistake here. Today I found that the code without brackets also runs well and produce the same results. However I do remember somewhere with the OR condition the brackets are needed, I forget what was the scenario. But here the two codes produce the same results with normal and same logs.

proc print data=pg1.storm_summary;
   where maxwindmph>156 or 
         0<minpressure <920;
run;

proc print data=pg1.storm_summary;
   where (maxwindmph>156 or 0<minpressure <920);
run;

69         proc print data=pg1.storm_summary;
 70            where maxwindmph>156 or
 71                  0<minpressure <920;
 72         run;
 
 NOTE: There were 161 observations read from the data set PG1.STORM_SUMMARY.
       WHERE (maxwindmph>156) or (minpressure>0 and minpressure<920);

 74         proc print data=pg1.storm_summary;
 75            where (maxwindmph>156 or 0<minpressure <920);
 76         run;
 
 NOTE: There were 161 observations read from the data set PG1.STORM_SUMMARY.
       WHERE (maxwindmph>156) or (minpressure>0 and minpressure<920);