TKM: Memory Error when first time Launching SAS 9.4, After Installation

[catchnight]

SAS9.4 M2, when I took the initial launching, there is errors as following:

ERROR: TKM: Memory Error [CHECKOWNER] Pool1 [ 259a170] [WM Reb Pool:HOST ] Pool2 [ 25ab360] [UnknownG2]
ERROR: Reason: [TKM Allocation Released to the Wrong pool : ]

Anyone knows what casues this? thx

[Kurt_Bremser]

• open a track with SAS technical support, they are the best for such issues
• since you're doing a fresh install, get a current depot (M7, soon M8); no use to risk having issues that may have been fixed in the current release

[catchnight]

tried to install SAS9.4 m7, first-time launching showed error:

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 (C947E776)

I checked this communities for  possible solution, Solved: Error at start of SAS Base (exception 36092C2 and ... - SAS Support Communities. However, it does not work for my issue.

[Kurt_Bremser]

Then let's see what technical support has to say.

[BrNiel]

Hey there, @catchnight 

By chance, are you running the SAS 9.4 platform on Windows 10?  Did you get the issue resolved?

My team did see a couple instances where - if you had a certain Windows Update applied - and your Windows Print Spooler service was either stopped/disabled, the SAS Windowing Environment may not open.

Thanks

[King-JZF]

Hey,

I also got the same error when I open SAS 9.4.

Thanks to @BrNiel  method. I checked my Windows Print Spooler service, I found it is disabled. The way I solve it is to start Windows Print Spooler and then the SAS 9.4 can be open now without error!

[BrNiel]

Glad to hear that worked for you as well, @King-JZF.

Note: If your organization requires that specific service to stay disabled in an environment (i.e., you wouldn't be able to print anyway) there is a startup option in the SAS 9.4 Windowing Environment that could also be used.  Contact SAS Technical Support to create a Case if so, and we can help you further diagnose.

[ZLX]

The best solution ever!! Thanks!!