SAS error

[Strs1309]

Hello guys! I have got this strange error when I use Strata option in proc lifetest.

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

The SAS task name is [LIFETEST]
Exception occurred at (0FE95E62)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
0FE95E62 2D3FE1B8 saslifet:tkvercn1+0x24E22
0FE9A9D9 2D3FE378 saslifet:tkvercn1+0x29999
0FE948C1 2D3FEF78 saslifet:tkvercn1+0x23881
0FE8B910 2D3FFEF8 saslifet:tkvercn1+0x1A8D0
0363766E 2D3FFF5C sashost:Main+0xF7FE
03768038 2D3FFF70 sashost:tkStartSas+0x1AE88
76F100C9 2D3FFF80 KERNEL32:BaseThreadInitThunk+0x19
772C7B4E 2D3FFFDC ntdll:RtlGetAppContainerNamedObjectPath+0x11E
772C7B1E 2D3FFFEC ntdll:RtlGetAppContainerNamedObjectPath+0xEE

What shall I do? Have anyone faced this kind of problem before?

[StatsMan]

Please contact technical support and provide your code (and data). The traceback helps. Seeing your code helps more. Also, provide the number of observations in the data set and the levels in your STRATA statement.

[ballardw]

These exception errors in my experience fall into 3 classes

1) requesting a combination of options that don't make real world sense and that the programmers at SAS didn't provide a check for because "no one will ever do that"

2) pathological data. This means data for a specific purpose that misbehaves. The specific analysis and data determines what that may be. I suspect that is why @StatsMan asked for the number of levels for the strata variable. Many levels may make it harder to deal with.

3) System problems. This can be anything from bad installation media so one program file is corrupted (I had this happen so that the DATA step wouldn't run once), or something relying on external SAS files is incompatible such as Java, Microsoft Office (32 vs 64 bit can still be an issue) or similar.

But diagnosing almost anything like this is a tech support issue.