sas error message: Freeing Memory Not Allocated

[abcd123]

hello, all

I got following error message:

ERROR: Freeing Memory Not Allocated  Pool [0000000009602A00] Value [000000000C71B3C0] WM Reb Pool:Kernel  .

Traceback for Thread [00000000002651A0] WM Reb Pool:Kernel  

0000000001E4AB00  000000000594F200  tkmk:tkBoot+0x9AE0

00000000034348FE  000000000594F230  sashost:Main+0x1B22E

000000000CA0B8B8  000000000594F2D0  sasioodb:tkvercn1+0x1A878

000000000A161096  000000000594F350  sasxdbi:tkvercn1+0x30056

000000000A141CA0  000000000594F3B0  sasxdbi:tkvercn1+0x10C60

0000000004ACB283  000000000594F3B8  sasyh:tkvercn1+0xA243

0000000004AC157D  000000000594F4D0  sasyh:tkvercn1+0x53D

00000000048A57C0  000000000594F4D8  sasxkern:tkvercn1+0x4780

000000000341E872  000000000594FAB0  sashost:Main+0x51A2

000000000341BBD3  000000000594FC50  sashost:Main+0x2503

000000000341C26B  000000000594FCB0  sashost:Main+0x2B9B

0000000003428B1B  000000000594FF20  sashost:Main+0xF44B

000000000342D13D  000000000594FF50  sashost:Main+0x13A6D

000000007741652D  000000000594FF80  kernel32:BaseThreadInitThunk+0xD

000000007764C541  000000000594FFD0  ntdll:RtlUserThreadStart+0x21

By the way, I got this error message NOT from sas log; rather the error message appear in a separate window. What is this error message about?  I googled and find following link

( support.sas.com/kb/31/007.html    ); but the instruction looks scary :--) Is there a simple way to fix such error? Thanks

[Amir]

Hi,

If you are not comfortable carrying out the solution provided then try contacting SAS Technical Support: Technical Support Form

They should be able to help confirm what the error is as well as provide guidance if you get stuck.

Regards,

Amir.

[machwhat]

I am seeing the exact same error.

Did you ever find a solution to this issue?

[Kurt_Bremser]

Submit this to SAS TS. This could be a bug inside the SAS software.

[SASKiwi]

I checked your link and the error documented is not the same as you have put in your post even though some of the text is similar. Also unless you were using SAS OLAP Server when the error occurred then it is probably not related.

You don't state what you were doing to cause the error. Please post any SAS code that was running at the time.

[sophia_zhang]

I am having the same issue, have anyone find the solution to this ?

[SASKiwi]

What were you running or doing in SAS when the error occured? Is your error exactly the same or just similar - please post. As has already been mentioned, this type of problem is better progressed by contacting SAS Tech Support.

[machwhat]

SAS TS is pointing to server hardware - in particular RAM, but that seems odd considering three people in this thread have the same issue.

[machwhat]

Seeing this error

ERROR: Freeing Memory Not Allocated  Pool [1101e62a0] Value [1110101f0] WM Reb Pool:Kernel  .

Traceback for Thread [1101f9cf0] WM Reb Pool:Kernel  

skmMemRelease+0x178

vmfree_tkm@AF14_6+0x1c

vmfree_handler+0x14

ducon+0x83c

dbicon+0x6bc

yoeopen+0xaec

yyoopen+0x2768

yoopen+0x250

xo

open+0x38 -- bridge stub

dsopen+0x3ec

rslv_ds+0x378

rslv_tables+0xdc

sqlrslv+0x8c

sqlprep+0x87c

sqlprep+0x38 -- bridge

stub

process_sql+0x270

sqlloop+0xd40

sqlloop+0x38 -- bridge stub

sassql+0x18c

vvtentr+0x194

_pthread_body+0xf0

ERROR: Freeing Memory Not Allocated  Pool [1101e62a0] Value [1110101f0] WM Reb Pool:Kernel  .

Traceback for Thread [1101f9cf0] WM Reb Pool:Kernel  

skmMemRelease+0x178

vmfree_tkm@AF14_6+0x1c

vmfree_handler+0x14

ducon+0x83c

dbicon+0x6bc

yoeopen+0xaec

yyoopen+0x2768

yoopen+0x250

xo

open+0x38 -- bridge stub

dsopen+0x3ec

rslv_ds+0x378

rslv_tables+0xdc

sqlrslv+0x8c

sqlprep+0x87c

sqlprep+0x38 -- bridge

stub

process_sql+0x270

sqlloop+0xd40

sqlloop+0x38 -- bridge stub

sassql+0x18c

vvtentr+0x194

_pthread_body+0xf0

^L8    

We *think* it's when running this SAS code:

proc sql feedback _method;

create table work.mp(SORTEDBY=NotificationID) as

select a.NotificationID, "MP"  as source

from acdc_ci as a inner join

      careone.ManagedPerson(where=(RecordStatus=0 and

                                   &inc_dt. <= datepart(UpdateDate) <= &extrdt.)) as b

on a.ManagedPersonID=b.ManagedPersonID

order by NotificationID;

quit;

[Tim_SAS]

You should report this problem to Technical Support. They're in the best position to analyze the problem and supply fixes or workarounds.

[machwhat]

Had a track open for months but TS was not able to figure the issue out.

We are having other network issues on that server related to transferring files to and from it, so perhaps it's related to that.

[carmencody]

I'm getting the same message now. Did you ever get this fixed?