Error message in log

fbl204653 — Thu, 02 Nov 2017 18:04:41 GMT

Hi SAS experts,

An expected error massage came up when I ran a program.

Please see below. I have no idea what's going on.

Thanks!

MPRINT(PROFILE): proc sql;
MPRINT(PROFILE): select max(EXDOSE_STD) into :crsdose from subject4;

ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:

The SAS task name is [SQL]
ERROR: Write Access Violation SQL
Exception occurred at (0AF4C44A)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
000000000AF4C44A 000000000A64DE90 sasrtf:tkvercn1+0xB40A
0000000008041BDA 000000000A64DE98 sasoda:tkvercn1+0x80B9A
0000000007FC232D 000000000A64E2B0 sasoda:tkvercn1+0x12ED
000000000F31160A 000000000A64E2B8 sasmrk:tkvercn1+0x1105CA
000000000F29517E 000000000A64E860 sasmrk:tkvercn1+0x9413E
0000000005F843DA 000000000A64E868 sasods:tkvercn1+0x21339A
0000000005E362CA 000000000A64EC10 sasods:tkvercn1+0xC528A
0000000005DCFA2E 000000000A64F300 sasods:tkvercn1+0x5E9EE
000000000DA3907A 000000000A64F308 sassqx:tkvercn1+0x4803A
000000000DA193D9 000000000A64F7A0 sassqx:tkvercn1+0x28399
000000000DA1800C 000000000A64F8C0 sassqx:tkvercn1+0x26FCC
000000000DA2AB09 000000000A64F910 sassqx:tkvercn1+0x39AC9
000000000DA22FC9 000000000A64F9E0 sassqx:tkvercn1+0x31F89
000000000DA2264C 000000000A64FB50 sassqx:tkvercn1+0x3160C
000000000D9D1330 000000000A64FB58 sassql:tkvercn1+0x2F0
0000000002F7948E 000000000A64FBE8 sashost:Main+0x113BE
0000000002F7F2DD 000000000A64FF50 sashost:Main+0x1720D
00007FF8973113D2 000000000A64FF58 KERNEL32:BaseThreadInitThunk+0x22
00007FF898E354E4 000000000A64FF88 ntdll:RtlUserThreadStart+0x34

NOTE: The SAS System stopped processing this step because of errors.
NOTE: PROCEDURE SQL used (Total process time):
real time 0.02 seconds
cpu time 0.01 seconds

Re: Error message in log

ballardw — Thu, 02 Nov 2017 19:20:23 GMT

My experience with similar errors usually involves syntax that has something that the syntax checker hasn't been programmed to look for.

Since you have MPRINT showing then the code appears to be in a macro. Since it appears that the code generated by the macro is severe you might consider sharing the code for the macro. Unfortunately since macros can be data driven that my not provide sufficient information depending on the complexity of the code and the actual content of any data.

I would say that since your MPRINT does not include a Quit; statement for the given proc sql code that there may be something that SAS can't tell if it belongs as part of that Proc SQL step or not.

topic Error message in log in SAS Programming

Error message in log

Re: Error message in log