61353 - Performing an object spawner refresh returns an Access Violation error

Problem Note 61353: Performing an object spawner refresh returns an Access Violation error

In some grid configurations, when you try to perform an administrative action (a stop, refresh, or restart) on the object spawner, a crash occurs. The following error is returned to the client application:

"SEVERE: IOM call failed. Internal server exception: access violation."

When you encounter this issue, the object spawner log contains output similar to the following:

2017-10-26T11:24:10,366 ERROR [00000982] 66:sasadm@saspw - /sasbin/SASHome/SASFoundation/9.4/sasexe/tkiomsvc.so(tktracex+0x2e) [0x7f2f9845bb5e]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkiomsvc.so(+0xd8d9) [0x7f2f983e08d9]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkmk.so(bktExcept+0x62) [0x7f2fa6b8f3f2]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7f2fa6b8fa44]

/lib64/libpthread.so.0(+0x3b2320f7e0) [0x7f2fa7eea7e0]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkmk.so(skm_unlinke+0x2a) [0x7f2fa6ba4e9a]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkmk.so(skmMemRelease+0x190) [0x7f2fa6ba1c00]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tklblsf.so(+0x2df82) [0x7f2f8c264f82]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tklblsf.so(+0x2d1f4) [0x7f2f8c2641f4]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkmk.so(sksUnloadExtension+0x17) [0x7f2fa6bb8d07]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkiomlb.so(LBClusterDestroy+0xc9) [0x7f2f8d516699]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkiomobj.so(clusterDestroy+0x172) [0x7f2f8de13b72]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkiomobj.so(obspServerDestroy+0x29e) [0x7f2f8de358ce]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkiomobj.so(+0x676fb) [0x7f2f8de296fb]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkiomobj.so(+0x691ff) [0x7f2f8de2b1ff]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkiomobj.so(obspCompRefresh_impl+0x24e) [0x7f2f8de08a4e]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkiomobj.so(+0x19caf) [0x7f2f8dddbcaf]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkiomobj.so(+0x399f9) [0x7f2f8ddfb9f9]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkiompeb.so(+0x1f676) [0x7f2f9571f676]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkiompeb.so(clientDispatch+0xaf7) [0x7f2f95719527]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkiomsvc.so(svcPuddleMain+0x442) [0x7f2f983fa6d2]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkepdl.so(+0x5b59) [0x7f2f99984b59]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkmk.so(sktMain+0x94) [0x7f2fa6b8d494]

/sasbin/SASHome/SASFoundation/9.4/sasexe/tkmk.so(bktMain+0x71) [0x7f2fa6b8f231]

/lib64/libpthread.so.0(+0x3b23207aa1) [0x7f2fa7ee2aa1]

/lib64/libc.so.6(clone+0x6d) [0x7f2fa7570bcd]

...

2017-10-26T11:24:10,370 DEBUG [00000982] 66:sasadm@saspw - IOM LOGIC MapTKStatusTOWoiStatus() Mapping tkstatus: 803fe188

2017-10-26T11:24:10,370 DEBUG [00000982] 66:sasadm@saspw - IOM RETURN -1={compRef:7f2f97304da0}->ObjectSpawner::Refresh(): text=<?xml version="1.0"?><Exceptions><Exception><SASMessage severity="Error">IOM call failed. Internal server exception: access violation.</SASMessage></Exception></Exceptions>

You can still stop and restart the object spawner to effect configuration changes.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
Product Family	Product	System	Reported	Fixed*	Reported	Fixed*
SAS System	SAS Grid Manager Control Server Configuration	Windows 7 Ultimate 32 bit	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Windows 7 Professional x64	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Windows 7 Professional 32 bit	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Windows 7 Home Premium x64	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Windows 7 Home Premium 32 bit	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Windows 7 Enterprise x64	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Windows 7 Enterprise 32 bit	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Microsoft Windows Server 2016	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Microsoft Windows Server 2012 Std	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Microsoft Windows Server 2012 R2 Std	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Microsoft Windows Server 2012 R2 Datacenter	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Microsoft Windows Server 2012 Datacenter	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Microsoft Windows Server 2008 for x64	9.44		9.4 TS1M5
		Microsoft Windows Server 2008 R2	9.44		9.4 TS1M5
		Microsoft Windows Server 2008	9.44		9.4 TS1M5
		Microsoft Windows 10	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Microsoft Windows 8.1 Pro x64	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Microsoft Windows 8.1 Pro 32-bit	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Microsoft Windows 8.1 Enterprise x64	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Microsoft Windows 8.1 Enterprise 32-bit	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Microsoft Windows 8 Pro x64	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Microsoft Windows 8 Pro 32-bit	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Microsoft Windows 8 Enterprise x64	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Microsoft Windows 8 Enterprise 32-bit	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Microsoft® Windows® for x64	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Windows 7 Ultimate x64	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		64-bit Enabled AIX	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		64-bit Enabled Solaris	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		HP-UX IPF	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Linux for x64	9.44	9.45	9.4 TS1M5	9.4 TS1M6
		Solaris for x64	9.44	9.45	9.4 TS1M5	9.4 TS1M6

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

Type:	Problem Note
Priority:	medium

Date Modified:	2017-11-09 14:29:06
Date Created:	2017-11-03 14:10:11

Support

Problem Note 61353: Performing an object spawner refresh returns an Access Violation error

Operating System and Release Information