SAS write access error

[sarahal]

Hi all,

I've been encountering an issue when I run PROC GEE on SAS studio. I have checked my code quite a few times and still receive this error:

ERROR: An exception has been encountered.

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

The SAS task name is [GEE (2)]

ERROR: Write Access Violation GEE (2)

Exception occurred at (0B20F63C)

Task Traceback

Address Frame (DBGHELP API Version 4.0 rev 5)

000000000B20F63C 000000000B16F650 tkgee:tkgee+0x2E05C

000000000B207AA5 000000000B16F7C0 tkgee:tkgee+0x264C5

000000000B205AA9 000000000B16F9A0 tkgee:tkgee+0x244C9

00000000096B8D2C 000000000B16F9A8 sasgee:tkvercn1+0x7CEC

00000000096B1363 000000000B16FBF0 sasgee:tkvercn1+0x323

00000000019F89DB 000000000B16FBF8 sashost:Main+0x10EBB

00000000019FE61D 000000000B16FF50 sashost:Main+0x16AFD

00007FF8574513D2 000000000B16FF58 KERNEL32:BaseThreadInitThunk+0x22

00007FF8591354F4 000000000B16FF88 ntdll:RtlUserThreadStart+0x34

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

NOTE: PROCEDURE GEE used (Total process time):

real time 0.18 seconds

cpu time 0.18 seconds

619

620

621

622

623

624

625

626

627

628

629

630

631

632 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;

Any help is appreciated,

Sarah

[Kurt_Bremser]

This is not a typical ERROR caused by bad programming. Submit it to SAS technical support.

ERRORs caused by your code have to generate a more graceful response.

[ballardw]

---

@sarahal wrote:

Hi all,

I've been encountering an issue when I run PROC GEE on SAS studio. I have checked my code quite a few times and still receive this error:

ERROR: An exception has been encountered.

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

The SAS task name is [GEE (2)]

ERROR: Write Access Violation GEE (2)

Exception occurred at (0B20F63C)

Task Traceback

---

Post your code here in a code box opened with the forum's {I} icon.

Someone may spot something you missed. Best would be to include a small example data set with the variables used as data step code as well.

I know that I can generate such errors for other procedures by using what may look like good code but is really more invalid than SAS saw to write syntax checking for.