Anonymous_User Absent Member.
Absent Member.
1276 views

TSANDS causing abend

Last week we loaded TSANDS on a new OES (NetWare) Server with SP4.
During the back it keeps abending. They are running 10551.71 of TSANDS.

Any suggestions?

Thanks,

John Jakus
Labels (2)
0 Likes
6 Replies
Anonymous_User Absent Member.
Absent Member.

Re: TSANDS causing abend

>Any suggestions?

Post an abend log? Log a call with Novell and submit a coredump for
analysis?
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSANDS causing abend

check the novell downloads I think that tsands has been updated to a
different nlm all together


"Andrew C Taubman" <ataubman.RemoveThisToMailMe@novell.AndThis.com> wrote in
message news:K49ef.2125$Ay4.372@prv-forum2.provo.novell.com...
> >Any suggestions?

>
> Post an abend log? Log a call with Novell and submit a coredump for
> analysis?
> --
> Andrew C Taubman
> Novell Support Forums Volunteer SysOp
> http://support.novell.com/forums
> (Sorry, support is not provided via e-mail)
>
> Opinions expressed above are not
> necessarily those of Novell Inc.



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSANDS causing abend

also check to see our server was abending on backing up open files
this was caused by the tsands.nlm we updated to the new tsaf.nlm and it's ok
now

"Darrell Milam" <dmilam@clhnt.com> wrote in message
news:9Toef.2891$Ay4.2028@prv-forum2.provo.novell.com...
> check the novell downloads I think that tsands has been updated to a
> different nlm all together
>
>
> "Andrew C Taubman" <ataubman.RemoveThisToMailMe@novell.AndThis.com> wrote
> in message news:K49ef.2125$Ay4.372@prv-forum2.provo.novell.com...
>> >Any suggestions?

>>
>> Post an abend log? Log a call with Novell and submit a coredump for
>> analysis?
>> --
>> Andrew C Taubman
>> Novell Support Forums Volunteer SysOp
>> http://support.novell.com/forums
>> (Sorry, support is not provided via e-mail)
>>
>> Opinions expressed above are not
>> necessarily those of Novell Inc.

>
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSANDS causing abend

I'm not sure what you are referring to here. EMbackup perhaps?
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSANDS causing abend

Andrew C Taubman wrote:
> >Any suggestions?

>
> Post an abend log? Log a call with Novell and submit a coredump for
> analysis?

Here is the abend log info from Config Reader. Does this show anything?

Server NS1-US halted Friday, November 11, 2005 7:18:32.299 pm
Abend 2 on P00: Server-5.70.04: Page Fault Processor Exception (Error
code 00000000)

Registers:
CS = 0060 DS = 007B ES = 007B FS = 007B GS = 007B SS = 0068
EAX = 80000000 EBX = 00000000 ECX = AD81C13C EDX = 00000000
ESI = 0000000E EDI = B708E5D8 EBP = 00000000 ESP = AD81C100
EIP = 9EDA574A FLAGS = 00010202
9EDA574A 8B4618 MOV EAX, [ESI+18]=?
EIP in TSANDS.NLM at code start +0000974Ah
Access Location: 0x00000026

The violation occurred while processing the following instruction:
9EDA574A 8B4618 MOV EAX, [ESI+18]
9EDA574D 8944240C MOV [ESP+0C], EAX
9EDA5751 85C0 TEST EAX, EAX
9EDA5753 7487 JZ 9EDA56DC
9EDA5755 8B5E54 MOV EBX, [ESI+54]
9EDA5758 85DB TEST EBX, EBX
9EDA575A 7414 JZ 9EDA5770
9EDA575C F6432320 TEST byte ptr [EBX+23], 20
9EDA5760 7482 JZ 9EDA56E4
9EDA5762 53 PUSH EBX



Running process: SMDR 79 Process
Thread Owned by NLM: SMDR.NLM
Stack pointer: AD81C000
OS Stack limit: AD80CF40
Scheduling priority: 67371008
Wait state: 5050030 Blocked on Semaphore
Stack: --00000004 ?
--00000000 ?
--00000000 ?
--AD81C13C ?
--00000000 ?
--0000000E ?
-94BEA75C (TSANDS.NLM|(Data Start)+75C)
--AD81C160 ?
9EDAA04E (TSANDS.NLM|(Code Start)+E04E)
--B708E5D8 ?
--0000000E ?
--00000000 ?
--AD81C13C ?
80000000 (NWSA.NSS|(Code Start)+D000)
--B708E5D8 ?
--00000000 ?
--0000000E ?
--89A3D288 ?
--979C96B8 ?
8AAA9020 ?
--989F9060 ?
--0000000E ?
--FBA00006 ?
--AD81C160 ?
--00000006 ?
8AAA6862 ?
--979C96B8 ?
--8AB69908 ?
8AAA6E00 ?
--8AB69908 ?
--AD81C590 ?
--52444D53 ?
--4D4C4E2E ?
8AA72100 (SMDR.NLM|SMdmem_New+4D6)
--8A597240 ?
--979C9038 ?
--979C96B8 ?
8AA7DB4E (SMDR.NLM|SMvbuf_b_Reset+41)
--979C9748 ?
--5E1AF58D ?
--8D94850A ?
--3624D3C5 ?
--00000046 ?
00105EE6 (LOADER.NLM|kSpinUnlockRestore+26)
--00000046 ?
8472DAAE (WS2_32.NLM|WSPREAD_EventCallback+7A)
--87BB9124 ?
--0000000B ?
--00000000 ?
--00000000 ?
--87BB9700 ?
--867AFBD7 ?
--8D94BB64 ?
--85D333DC (ETHERTSM.NLM|CEtherTSMGetConfigInfo+F26)
--84F8662A (WSPIPX.NLM|configBuff+2172)
--0000002C ?
--00000002 ?
--00000001 ?
--867910CC ?
--00000011 ?
--86791118 ?
--84F8663A (WSPIPX.NLM|configBuff+2182)
--867910CC ?
--84F861C0 (WSPIPX.NLM|configBuff+1D08)
--87BB9700 ?
--00000286 ?
--84F86236 (WSPIPX.NLM|configBuff+1D7E)
--00000246 ?
--FFFFFF0E ?
--87E6B920 ?
--867877F4 ?
8675C06E (Q57.LAN|(Code Start)+E06E)
--85D35F70 (ETHERTSM.NLM|CEtherTSMGetConfigInfo+3ABA)
--867877F4 ?
--00000000 ?
0022A873 (SERVER.NLM|kScheduleFastWorkToDoDirected+57)
--0006212C (LOADER.NLM|NestedInterruptCount+2C)
-BF873610 (LSL.NLM|LSLServiceEventsFWTD+0)
--85D34C84 (ETHERTSM.NLM|CEtherTSMGetConfigInfo+27CE)
--AD81C2D6 ?
--00000001 ?
--00000000 ?
--85D333DC (ETHERTSM.NLM|CEtherTSMGetConfigInfo+F26)
BF868057 (LSL.NLM|InternalLSLServiceEvents+127)
-BF873610 (LSL.NLM|LSLServiceEventsFWTD+0)
--00000000 ?
--00000000 ?
-BF86DE20 (LSL.NLM|HoldQueueLock+0)
86745DEA (MSM.NLM|CMSMServiceEvents+A)
--00000082 ?
--00000001 ?
--00000001 ?
--85D333DC (ETHERTSM.NLM|CEtherTSMGetConfigInfo+F26)
--AD81C2D6 ?
8674FB3E (Q57.LAN|(Code Start)+1B3E)
--85D38EA4 (ETHERTSM.NLM|CEtherTSMGetConfigInfo+69EE)
BF8686A9 (LSL.NLM|LSLAdapterMutexUnlock+19)
-BF873790 (LSL.NLM|AdapterLockTable+20)
--86779000 ?
--00000000 ?

******************************************************************************
PVER: 6.50.04

Server NS1-US halted Saturday, November 12, 2005 5:41:24.547 am
Abend 3 on P00: Server-5.70.04: Page Fault Processor Exception (Error
code 00000000)

Registers:
CS = 0060 DS = 007B ES = 007B FS = 007B GS = 007B SS = 0068
EAX = 80000000 EBX = 00000000 ECX = AEE47EFC EDX = 00000000
ESI = 0000000E EDI = AEE9E1F8 EBP = 00000000 ESP = AEE47EC0
EIP = 9EDA574A FLAGS = 00010202
9EDA574A 8B4618 MOV EAX, [ESI+18]=?
EIP in TSANDS.NLM at code start +0000974Ah
Access Location: 0x00000026

The violation occurred while processing the following instruction:
9EDA574A 8B4618 MOV EAX, [ESI+18]
9EDA574D 8944240C MOV [ESP+0C], EAX
9EDA5751 85C0 TEST EAX, EAX
9EDA5753 7487 JZ 9EDA56DC
9EDA5755 8B5E54 MOV EBX, [ESI+54]
9EDA5758 85DB TEST EBX, EBX
9EDA575A 7414 JZ 9EDA5770
9EDA575C F6432320 TEST byte ptr [EBX+23], 20
9EDA5760 7482 JZ 9EDA56E4
9EDA5762 53 PUSH EBX



Running process: SMDR 90 Process
Thread Owned by NLM: SMDR.NLM
Stack pointer: AEE47DC0
OS Stack limit: AEE38D00
Scheduling priority: 67371008
Wait state: 5050030 Blocked on Semaphore
Stack: --00000004 ?
--00000000 ?
--00000000 ?
--AEE47EFC ?
--00000000 ?
--0000000E ?
-94BEA75C (TSANDS.NLM|(Data Start)+75C)
--AEE47F20 ?
9EDAA04E (TSANDS.NLM|(Code Start)+E04E)
--AEE9E1F8 ?
--0000000E ?
--00000000 ?
--AEE47EFC ?
80000000 (NWSA.NSS|(Code Start)+D000)
--AEE9E1F8 ?
--00000000 ?
--0000000E ?
--89A3D288 ?
--979CA118 ?
8AAA9020 ?
--984D5DE0 ?
--0000000E ?
--D3C00006 ?
--AEE47F20 ?
--00000006 ?
8AAA6862 ?
--979CA118 ?
--97D41068 ?
8AAA6E00 ?
--97D41068 ?
--AEE48350 ?
--52444D53 ?
--4D4C4E2E ?
8AA72100 (SMDR.NLM|SMdmem_New+4D6)
--895BB600 ?
--979C9A98 ?
--979CA118 ?
8AA7DB4E (SMDR.NLM|SMvbuf_b_Reset+41)
--979CA1A8 ?
--0000000B ?
--00000000 ?
--00000000 ?
--8B2828E0 ?
--867B0507 ?
--8D94BB64 ?
--85D333DC (ETHERTSM.NLM|CEtherTSMGetConfigInfo+F26)
--84F864EA (WSPIPX.NLM|configBuff+2032)
--0000002C ?
--00000002 ?
--00000001 ?
--867918C8 ?
--00000011 ?
--86791914 ?
--84F864FA (WSPIPX.NLM|configBuff+2042)
--8678711C ?
8675C06E (Q57.LAN|(Code Start)+E06E)
--85D35F70 (ETHERTSM.NLM|CEtherTSMGetConfigInfo+3ABA)
--8678711C ?
--00000000 ?
0022A873 (SERVER.NLM|kScheduleFastWorkToDoDirected+57)
--0006212C (LOADER.NLM|NestedInterruptCount+2C)
-BF873610 (LSL.NLM|LSLServiceEventsFWTD+0)
--85D34C84 (ETHERTSM.NLM|CEtherTSMGetConfigInfo+27CE)
--AEE48056 ?
--00000001 ?
--00000000 ?
--85D333DC (ETHERTSM.NLM|CEtherTSMGetConfigInfo+F26)
BF868057 (LSL.NLM|InternalLSLServiceEvents+127)
-BF873610 (LSL.NLM|LSLServiceEventsFWTD+0)
--00000000 ?
--00000000 ?
-BF86DE20 (LSL.NLM|HoldQueueLock+0)
86745DEA (MSM.NLM|CMSMServiceEvents+A)
--00000086 ?
--00000001 ?
--00000001 ?
--85D333DC (ETHERTSM.NLM|CEtherTSMGetConfigInfo+F26)
--AEE48056 ?
8674FB3E (Q57.LAN|(Code Start)+1B3E)
--85D333DC (ETHERTSM.NLM|CEtherTSMGetConfigInfo+F26)
--85D333DC (ETHERTSM.NLM|CEtherTSMGetConfigInfo+F26)
--00000001 ?
8674FF09 (Q57.LAN|(Code Start)+1F09)
--85D333DC (ETHERTSM.NLM|CEtherTSMGetConfigInfo+F26)
--06000000 ?
--00000246 ?
--00000000 ?
--00000046 ?
00105EE6 (LOADER.NLM|kSpinUnlockRestore+26)
--00000046 ?
--87E6B2E0 ?
--00000246 ?
--8B282DE4 ?
85E7B77A (WSPIPX.NLM|ipxmapSessnRelease+A)
--8B282DC0 ?
85E79544 (WSPIPX.NLM|SPXS_RxESRHandler+FC)
--8B282DC0 ?
--83FFE000 ?
-0043E4D0 (SERVER.NLM|xAllocSizeTable+630)
--00000000 ?

Thanks,

John Jakus
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSANDS causing abend

That only contains Abend 2 and 3, we need to see Abend 1 including the
full modules listing. Please post the *complete* entry of "Abend 0",
"Abend 1" or "Break 1" from sys:system/abend.log. If there is no Abend
0/1, pls Set auto restart after abend =0 to maximise the chance that the
server can write the first abend to the log next time. Thank you.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.