ERROR: Read Access Violation REPORT (2)

[Asif4862]

Hello All,

I'm having issue when I'm running Proc Report procedure using macros on SAS new maintenance release M7.

FYI: Same program running fine on SAS Maintenance release M5.

Please advise

Error log messages:

NOTE: Multiple concurrent threads will be used to summarize data.

ERROR: An exception has been encountered.

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

The SAS task name is [REPORT (2)]

ERROR: Read Access Violation REPORT (2)

Exception occurred at (104E2215)

Task Traceback

Address Frame (DBGHELP API Version 4.0 rev 5)

00007FFA104E2215 000000F1901F8180 saspso:tkvercn1+0x311D5

00007FFA1059EB47 000000F1901F81C0 saspso:tkvercn1+0xEDB07

00007FFA1051CCEB 000000F1901F8930 saspso:tkvercn1+0x6BCAB

00007FFA16E60087 000000F1901F8938 sasods:tkvercn1+0x2AF047

00007FFA16D7945D 000000F1901F8E50 sasods:tkvercn1+0x1C841D

00007FFA16D7844F 000000F1901F8EE0 sasods:tkvercn1+0x1C740F

00007FFA16E60087 000000F1901F8F20 sasods:tkvercn1+0x2AF047

00007FFA16D7BACD 000000F1901F9030 sasods:tkvercn1+0x1CAA8D

00007FFA16E60087 000000F1901F9070 sasods:tkvercn1+0x2AF047

00007FFA132BEFAF 000000F1901F9078 sasmrk:tkvercn1+0x3DF6F

00007FFA133A3B57 000000F1901F9190 sasmrk:tkvercn1+0x122B17

00007FFA132BEDEE 000000F1901F92D0 sasmrk:tkvercn1+0x3DDAE

00007FFA1059EB47 000000F1901F9310 saspso:tkvercn1+0xEDB07

00007FFA104F49E4 000000F1901F93F0 saspso:tkvercn1+0x439A4

257 The SAS System

00007FFA133A3B57 000000F1901F9430 sasmrk:tkvercn1+0x122B17

00007FFA132B97AC 000000F1901F9620 sasmrk:tkvercn1+0x3876C

00007FFA1059EB47 000000F1901F9660 saspso:tkvercn1+0xEDB07

00007FFA104F31E3 000000F1901F96F0 saspso:tkvercn1+0x421A3

00007FFA133A3B57 000000F1901F9730 sasmrk:tkvercn1+0x122B17

00007FFA132B5956 000000F1901F99F0 sasmrk:tkvercn1+0x34916

00007FFA133A3B57 000000F1901F9A30 sasmrk:tkvercn1+0x122B17

00007FFA1328DEA8 000000F1901F9BC0 sasmrk:tkvercn1+0xCE68

00007FFA133A3B57 000000F1901F9C00 sasmrk:tkvercn1+0x122B17

00007FFA1328D344 000000F1901F9C50 sasmrk:tkvercn1+0xC304

00007FFA0F55CA47 000000F1901F9C58 sasrep7:tkvercn1+0x2BA07

00007FFA0F5478B9 000000F1901FAEC0 sasrep7:tkvercn1+0x16879

00007FFA0F545B1A 000000F1901FB0C0 sasrep7:tkvercn1+0x14ADA

00007FFA0F53B767 000000F1901FBA70 sasrep7:tkvercn1+0xA727

00007FFA0F55CA47 000000F1901FBAB0 sasrep7:tkvercn1+0x2BA07

00007FFA0F541E0B 000000F1901FC740 sasrep7:tkvercn1+0x10DCB

00007FFA0F55CA47 000000F1901FC780 sasrep7:tkvercn1+0x2BA07

00007FFA0F540851 000000F1901FC8C0 sasrep7:tkvercn1+0xF811

00007FFA16E60087 000000F1901FC900 sasods:tkvercn1+0x2AF047

00007FFA16C05188 000000F1901FCB90 sasods:tkvercn1+0x54148

00007FFA16C01929 000000F1901FCE60 sasods:tkvercn1+0x508E9

00007FFA0F66F6A7 000000F1901FCE68 sasrepmn:tkvercn1+0x4E667

00007FFA0F624EB8 000000F1901FED30 sasrepmn:tkvercn1+0x3E78

00007FFA0F6A1125 000000F1901FED38 sasrepor:tkvercn1+0xE5

00007FFA24C1F5A8 000000F1901FF468 sashost:Main+0x15268

00007FFA24C259CC 000000F1901FF790 sashost:Main+0x1B68C

00007FFA336D7974 000000F1901FF798 KERNEL32:BaseThreadInitThunk+0x14

00007FFA3628A271 000000F1901FF7C8 ntdll:RtlUserThreadStart+0x21

NOTE: PROCEDURE REPORT used (Total process time):

real time 0.07 seconds

cpu time 0.04 seconds

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

WARNING: The data set WORK.XXXXX may be incomplete. When this step was stopped there were 3 observations and 18 variables.

NOTE: There were 1034 observations read from the data set WORK.XXXXX.

[SASKiwi]

@Asif4862  - As advised in your SAS log, raising a Tech Support track for this is the best approach. Is this the only program you are having problems with?

[Asif4862]

Thank you @SASKiwi for the update. And yes I'm having this issue only with one program.

Thanks,
Asif

[ballardw]

The code that causes the error and a small number of example records might help (and tech support will ask for that).

One of the causes for such error messages are pathological code when compared with the data values, incompatible options so odd that the syntax checkers cannot identify the issue.

[Asif4862]

Thank you @ballardw for your feedback. I also researched and found this SAS Note: https://support.sas.com/kb/43/753.html 

But it did not work in my case. I'm doing my research and will share my findings in this thread.

Thanks,
Asif

[ballardw]

---

@Asif4862 wrote:

Thank you @ballardw for your feedback. I also researched and found this SAS Note: https://support.sas.com/kb/43/753.html 

But it did not work in my case. I'm doing my research and will share my findings in this thread.

Thanks,
Asif

---

And since you said you were generating the code with macros then the code of the macro and the way the macro is called also becomes a critical component. You might try adding OPTIONS MPRINT; and see if you get some generated log with details that might point to things causing the issue.

I would say that macros are one of the ways to generate pathological code when you make assumptions about the data that are not true.