SAS does not start

[efims]

Generates SAS message log:

--------------------------------------------------------------------------------------------------------------

ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
The SAS task name is [sasxkern]
ERROR: Read Access Violation sasxkern
Exception occurred at (100895A9)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
00000000100895A9 000000000491C3D0 EF172218:DllGetClassObject+0x8488C
00000000100901D9 000000000491C460 EF172218:DllGetClassObject+0x8B4BC
000000001008F9F8 000000000491CF50 EF172218:DllGetClassObject+0x8ACDB
000000001008ECB5 000000000491D080 EF172218:DllGetClassObject+0x89F98
000000001010BB18 000000000491D0C0 EF172218:DllGetClassObject+0x106DFB
0000000010110250 000000000491D140 EF172218:DllGetClassObject+0x10B533
000000001003EDBB 000000000491D7F0 EF172218:DllGetClassObject+0x3A09E
000007FEE89A5AB1 000000000491D7F8 PS5UI:MxdcGetPDEVAdjustment+0x30E1
000007FEE89EE957 000000000491D8B0 PS5UI:DrvPopulateFilterServices+0x48A47
000007FEE899B06C 000000000491D8E0 PS5UI:DrvDocumentPropertySheets+0x3D4
000007FEE899ACF1 000000000491DD70 PS5UI:DrvDocumentPropertySheets+0x59
000007FEFA7097FF 000000000491DD78 WINSPOOL:DocumentPropertySheets+0x26B
000007FEFA6FF163 000000000491DE40 WINSPOOL:Ordinal212+0x26B
000007FEFA70779B 000000000491DE80 WINSPOOL:DocumentPropertiesW+0x53
000007FEFE85DC31 000000000491DE88 GDI32:XLATEOBJ_iXlate+0x6721
000007FEFE84879D 000000000491E230 GDI32:SetDCBrushColor+0x189
000007FEFE84741D 000000000491E270 GDI32:CreateICA+0x11
00000000040607F4 000000000491E278 sasvwu:tkvercn1+0x12F7B4
0000000004044781 000000000491E860 sasvwu:tkvercn1+0x113741
0000000004055CD5 000000000491F350 sasvwu:tkvercn1+0x124C95
0000000004052614 000000000491F4A0 sasvwu:tkvercn1+0x1215D4
00000000033BCE5A 000000000491F4A8 sashost:Main+0xD59CA
00000000046F3482 000000000491F4D8 sasxkern:tkvercn1+0x2442
00000000046F1987 000000000491FBF0 sasxkern:tkvercn1+0x947
00000000032F833B 000000000491FF20 sashost:Main+0x10EAB
00000000032FDF7D 000000000491FF50 sashost:Main+0x16AED
00000000777159CD 000000000491FF58 kernel32:BaseThreadInitThunk+0xD
000000007797383D 000000000491FF88 ntdll:RtlUserThreadStart+0x1D

NOTE: Unable to open SASUSER.REGSTRY. WORK.REGSTRY will be opened instead.
NOTE: All registry changes will be lost at the end of the session.
NOTE: Unable to open SASUSER.PROFILE. WORK.PROFILE will be opened instead.
NOTE: All profile changes will be lost at the end of the session.

[RW9]

I would suggest contacting techincal support as the error suggests.

[efims]

They promise to answer within 24 hours

I hoped to get faster reply here

[SASKiwi]

Please be aware that there are no official service levels in the SAS community so you should always open a Tech Support track for high priority problems.

Also you need to supply details of what SAS version and what operating system you are using, along with how you are trying to start SAS. Are you using server-based SAS or PC-based SAS?

[SimonDawson]

Typically SAS technical support will reply to support request much faster than 24 hours. The best bet is the use the telephone for urgent problems. You'll get an instant reply that way.

The traceback you have in your log looks be headed into functions dealing with printers in Windows.

I'd suggest doing a bit of fact gathering and putting some data together to work with technical support.

Data that might be useful to the support engineer are things like this -

  Do you have other installation of SAS that are working on that system? (older versions etc)

  What if you logon to the machine with another user?

  Does it work if you run SAS with administrator permissions?

  Does SAS of the same version run on other similar systems?

  When did it start to play up? If it used to work, what changed at about the time the issue was seen.

  Does it always give this error?

  How long after attempting to launch it does the error pop up?

  etc.

[SimonDawson]

If you find that SAS will start on this system as another user and for the userid experiencing the issue its continiously failing. The most likely cause of the issue would be corruption of the SAS users registry. The SAS registry stores the setup of the printers.

You could likely address this by renaming the "9.4" directory from the users "My Documents\My SAS Files" directory in Windows and launching SAS again to have it recreate these catalogs and registry.

[Kurt_Bremser]

Use the {i} button to post log text. It keeps the original formatting, uses a fixed-space font and does not change anything (like you experienced with the unwanted smileys).

I guess you have a corrupted SASUSER. Remove it, and SAS will recreate it on Startup.