Help using Base SAS procedures

SAS Crashes: A required resource was unavailable.

Reply
Contributor
Posts: 27

SAS Crashes: A required resource was unavailable.

Hi,

I've had issues with SAS unexpectedly crashing for the past year and a half, which I've been unable to resolve. However, finally SAS has been temporarily unfreezing, enough that I can see the error message displayed.

The message is the following:

SAS Error Message2.png

What is this? I tried a couple Google searches, and it appears to be related to memory leak. Often I'll leave SAS open for a couple days, but I'm really suprised that SAS would have such problems. Overall I've been pretty disappointed by the lack of reliability. I'm using Base SAS 9.3 on Win 7 64bit with 16gb of memory. Also, this error almost exclusively occurs when I'm using the Base SAS GUI, such as switching views from my program code to the log, or when I click to view columns in a dataset. I'm not sure I've posted this under the correct discussion forum, please feel free to move, thanks!

Valued Guide
Posts: 3,208

Re: SAS Crashes: A required resource was unavailable.

You did not mention if you used the 32-bit or 64-bit of SAS. The problem is related to active-x.
Do you have a track-number? I expect a SAS person will be asking for that when he is seriously checking this.

---->-- ja karman --<-----
Contributor
Posts: 27

Re: SAS Crashes: A required resource was unavailable.

I use 64 bit SAS. Yes, I've also submitted to technical support and have a tracking #.

Valued Guide
Posts: 3,208

Re: SAS Crashes: A required resource was unavailable.

I think most people are using the 32-bit version of SAS 9.3 (more reliable). The 64-bit was the first release available in that 32-64 move at Windows.
They will have pushed you all the fixes I think. It is commonly very hard to be the first one having issues.
Nothing to be found with google or in their database, that cannot be the case as claiming all is on internet  :smileylaugh: .

---->-- ja karman --<-----
Ask a Question
Discussion stats
  • 3 replies
  • 463 views
  • 0 likes
  • 2 in conversation