Highlighted
Anonymous_User Absent Member.
Absent Member.
3209 views

Abend: Bad Resource Tag passed to LSLReturnRcvECB

Hi,

last weekend I updated a NW 6.5 SP6 Server to SP7, now twice a day I get
this Abend:

*********************************************************
Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.07

Server ICC-DEMO halted Monday, 22 October 2007 19:51:07,679
Abend 1 on P00: Server-5.70.07-0: Bad Resource Tag passed to
LSLReturnRcvECB

Registers:
CS = 0008 DS = 0023 ES = 0023 FS = 0023 GS = 0023 SS = 0010
EAX = 86E2D60D EBX = 00000000 ECX = 00000011 EDX = 00000A01
ESI = 870704C4 EDI = 00000000 EBP = 870704C4 ESP = 925E49B8
EIP = 870393DB FLAGS = 00000046
870393DB 83C404 ADD ESP, 00000004
EIP in LSL.NLM at code start +000063DBh

The violation occurred while processing the following instruction:
870393DB 83C404 ADD ESP, 00000004
870393DE B882FFFFFF MOV EAX, FFFFFF82
870393E3 0BC0 OR EAX, EAX
870393E5 C3 RET
870393E6 0000 ADD [EAX], AL
870393E8 0000 ADD [EAX], AL
870393EA 0000 ADD [EAX], AL
870393EC 0000 ADD [EAX], AL
870393EE 0000 ADD [EAX], AL
LSL.NLM|LSLReturnRcvECBNoSave:
870393F0 8B46FC MOV EAX, [ESI-04]



Running process: Server 00:42 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 925E4F40
OS Stack limit: 925DD000
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work
Stack: --86E2D60D ?
8B910D2D (TCP.NLM|UDPSendToAllIf+70C9)
--870704C4 ?
--00000282 (LOADER.NLM|KernelAddressSpace+282)
--8BD17328 ?
8B8F5398 (TCP.NLM|TCPAnyAddrCheck+2B18)
--925E4A4C ?
--7D9AF7B2 ?
--7D9A2912 ?
--8BD17328 ?
--925E4A4C ?
8B8F440B (TCP.NLM|TCPAnyAddrCheck+1B8B)
--8BD17328 ?
--925E4A4C ?
--7D9AF7B2 ?
--00000028 (LOADER.NLM|KernelAddressSpace+28)
--3FFFFFFF ?
--8BD17328 ?
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--925E4A4C ?
8B8F4030 (TCP.NLM|TCPAnyAddrCheck+17B0)
--8BD17328 ?
--925E4A4C ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8BD17328 ?
--925E4A4C ?
8B8F3A38 (TCP.NLM|TCPAnyAddrCheck+11B8)
--8BD17328 ?
--925E4A4C ?
8B8FCD54 (TCP.NLM|TCPMPUnsafeConnectionLookup+5A8)
--87070522 ?
--8BD17328 ?
--8BD17328 ?
--925E4A4C ?
8B8F2CC1 (TCP.NLM|TCPAnyAddrCheck+441)
--8BD17328 ?
--925E4A4C ?
--870704C4 ?
--925E4A78 ?
--925E4A88 ?
--10C6DC9D ?
--7D9A2912 ?
--10C6E250 ?
--000005B4 (LOADER.NLM|KernelAddressSpace+5B4)
--00000014 (LOADER.NLM|KernelAddressSpace+14)
--CEA00010 ?
--0000FFFF (LOADER.NLM|KernelAddressSpace+FFFF)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--23070210 ?
--71D82FD5 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--50000210 ?
--2160AFC6 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00008051 (LOADER.NLM|KernelAddressSpace+8051)
--00000400 (LOADER.NLM|KernelAddressSpace+400)
--0000000A (LOADER.NLM|KernelAddressSpace+A)
--925E4ABC ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00008051 (LOADER.NLM|KernelAddressSpace+8051)
--00000010 (LOADER.NLM|KernelAddressSpace+10)
--90EBFFDC ?
--7FD378AC (ACPIPWR.NLM|__NLM_BSS_End+1FA8)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00001000 (LOADER.NLM|KernelAddressSpace+1000)
--0000000F (LOADER.NLM|KernelAddressSpace+F)
--00000006 (LOADER.NLM|KernelAddressSpace+6)
--90EBF900 ?
--00000007 (LOADER.NLM|KernelAddressSpace+7)
--000000D5 (LOADER.NLM|KernelAddressSpace+D5)
--90EC001C ?
8C4C09EA (NCPIP.NLM|ReplyKeepNoFragments+12A)
--90EBF90C ?
--FDFFFFFF ?
--00000011 (LOADER.NLM|KernelAddressSpace+11)
--90EBF99A ?
--925E4CF0 ?
--00000007 (LOADER.NLM|KernelAddressSpace+7)
--000000D5 (LOADER.NLM|KernelAddressSpace+D5)
--90EBF9C0 ?
8A20B3AE (NCP.NLM|Case23+C2)
--90EBF9C0 ?
--000000D5 (LOADER.NLM|KernelAddressSpace+D5)
-00441AD0 (SERVER.NLM|xxLogNeqPhysSlabCache+0)
--FC42D820 ?
--00001000 (LOADER.NLM|KernelAddressSpace+1000)
--8F068300 ?
--8EA354B0 ?
--8EA354B0 ?
--8EA35440 ?
0031ACB2 (SERVER.NLM|Alloc+FA)
--8EA35440 ?
--8EA354B0 ?
-00440F3C (SERVER.NLM|xAllocSizeTable+54)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8F0E5400 ?

Additional Information:
The NetWare OS detected a problem with the system while executing a
process owned by LSL.NLM. It may be the source of the problem or there may
have been a memory corruption.

.... snip ...

The Server also runs Border Manger 3.8 current SP.

This Abend was documented and fixed in wsock6m, SP 7 contains a newer
WSPIP.NLM but I get this Abend.

Any ideas how to solve this issue ?


Walter


Labels (2)
0 Likes
8 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Abend: Bad Resource Tag passed to LSLReturnRcvECB

Gack, I hate those.... Basically this means that something ate the
resource header which precedes the ECB ( e.g. precedes the packet
receive buffer in memory ) and when LSL goes to take ownership and
change the resource in-use counters for the owner, it explodes because
the resource tag points to oblivion.

This can happen when a ECB is freed twice, or is corrupted some how, or
when the resource tag is not managed properly. So its hard to track
down what is causing the problem. Typically you need a core to figure
out what is the real source of these.

So we can vaguely blame it on Border Manager, right? 😉

By any chance, do you have multiple processors on this box? If so,
disable them and see if that gets you any stability. It might.

Of course there is the general advice to patch the server, NBM, and the
LAN drivers, ensure hyperthreading / virtual processor is disabled.
Blah, blah, blah... its what we always say in here, I know. A full
abend log with modules listing might help someone see a specific trouble
spot.

Also cross post or refer to this thread in a post to the NBM support
forum, if you have not already.

-- Bob

- - - - - - - - - - - - - - - - -
Robert Charles Mahar
Traffic Shaping Engine for NetWare
http://www.TrafficShaper.com
- - - - - - - - - - - - - - - - -


Walter Hofstädtler wrote:
> Hi,
>
> last weekend I updated a NW 6.5 SP6 Server to SP7, now twice a day I get
> this Abend:
>
> *********************************************************
> Novell Open Enterprise Server, NetWare 6.5
> PVER: 6.50.07
>
> Server ICC-DEMO halted Monday, 22 October 2007 19:51:07,679
> Abend 1 on P00: Server-5.70.07-0: Bad Resource Tag passed to
> LSLReturnRcvECB
>
> Registers:
> CS = 0008 DS = 0023 ES = 0023 FS = 0023 GS = 0023 SS = 0010
> EAX = 86E2D60D EBX = 00000000 ECX = 00000011 EDX = 00000A01
> ESI = 870704C4 EDI = 00000000 EBP = 870704C4 ESP = 925E49B8
> EIP = 870393DB FLAGS = 00000046
> 870393DB 83C404 ADD ESP, 00000004
> EIP in LSL.NLM at code start +000063DBh
>
> The violation occurred while processing the following instruction:
> 870393DB 83C404 ADD ESP, 00000004
> 870393DE B882FFFFFF MOV EAX, FFFFFF82
> 870393E3 0BC0 OR EAX, EAX
> 870393E5 C3 RET
> 870393E6 0000 ADD [EAX], AL
> 870393E8 0000 ADD [EAX], AL
> 870393EA 0000 ADD [EAX], AL
> 870393EC 0000 ADD [EAX], AL
> 870393EE 0000 ADD [EAX], AL
> LSL.NLM|LSLReturnRcvECBNoSave:
> 870393F0 8B46FC MOV EAX, [ESI-04]
>
>
>
> Running process: Server 00:42 Process
> Thread Owned by NLM: SERVER.NLM
> Stack pointer: 925E4F40
> OS Stack limit: 925DD000
> Scheduling priority: 67371008
> Wait state: 50500F0 Waiting for work
> Stack: --86E2D60D ?
> 8B910D2D (TCP.NLM|UDPSendToAllIf+70C9)
> --870704C4 ?
> --00000282 (LOADER.NLM|KernelAddressSpace+282)
> --8BD17328 ?
> 8B8F5398 (TCP.NLM|TCPAnyAddrCheck+2B18)
> --925E4A4C ?
> --7D9AF7B2 ?
> --7D9A2912 ?
> --8BD17328 ?
> --925E4A4C ?
> 8B8F440B (TCP.NLM|TCPAnyAddrCheck+1B8B)
> --8BD17328 ?
> --925E4A4C ?
> --7D9AF7B2 ?
> --00000028 (LOADER.NLM|KernelAddressSpace+28)
> --3FFFFFFF ?
> --8BD17328 ?
> --00000001 (LOADER.NLM|KernelAddressSpace+1)
> --925E4A4C ?
> 8B8F4030 (TCP.NLM|TCPAnyAddrCheck+17B0)
> --8BD17328 ?
> --925E4A4C ?
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --8BD17328 ?
> --925E4A4C ?
> 8B8F3A38 (TCP.NLM|TCPAnyAddrCheck+11B8)
> --8BD17328 ?
> --925E4A4C ?
> 8B8FCD54 (TCP.NLM|TCPMPUnsafeConnectionLookup+5A8)
> --87070522 ?
> --8BD17328 ?
> --8BD17328 ?
> --925E4A4C ?
> 8B8F2CC1 (TCP.NLM|TCPAnyAddrCheck+441)
> --8BD17328 ?
> --925E4A4C ?
> --870704C4 ?
> --925E4A78 ?
> --925E4A88 ?
> --10C6DC9D ?
> --7D9A2912 ?
> --10C6E250 ?
> --000005B4 (LOADER.NLM|KernelAddressSpace+5B4)
> --00000014 (LOADER.NLM|KernelAddressSpace+14)
> --CEA00010 ?
> --0000FFFF (LOADER.NLM|KernelAddressSpace+FFFF)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --23070210 ?
> --71D82FD5 ?
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --50000210 ?
> --2160AFC6 ?
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00008051 (LOADER.NLM|KernelAddressSpace+8051)
> --00000400 (LOADER.NLM|KernelAddressSpace+400)
> --0000000A (LOADER.NLM|KernelAddressSpace+A)
> --925E4ABC ?
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00008051 (LOADER.NLM|KernelAddressSpace+8051)
> --00000010 (LOADER.NLM|KernelAddressSpace+10)
> --90EBFFDC ?
> --7FD378AC (ACPIPWR.NLM|__NLM_BSS_End+1FA8)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00001000 (LOADER.NLM|KernelAddressSpace+1000)
> --0000000F (LOADER.NLM|KernelAddressSpace+F)
> --00000006 (LOADER.NLM|KernelAddressSpace+6)
> --90EBF900 ?
> --00000007 (LOADER.NLM|KernelAddressSpace+7)
> --000000D5 (LOADER.NLM|KernelAddressSpace+D5)
> --90EC001C ?
> 8C4C09EA (NCPIP.NLM|ReplyKeepNoFragments+12A)
> --90EBF90C ?
> --FDFFFFFF ?
> --00000011 (LOADER.NLM|KernelAddressSpace+11)
> --90EBF99A ?
> --925E4CF0 ?
> --00000007 (LOADER.NLM|KernelAddressSpace+7)
> --000000D5 (LOADER.NLM|KernelAddressSpace+D5)
> --90EBF9C0 ?
> 8A20B3AE (NCP.NLM|Case23+C2)
> --90EBF9C0 ?
> --000000D5 (LOADER.NLM|KernelAddressSpace+D5)
> -00441AD0 (SERVER.NLM|xxLogNeqPhysSlabCache+0)
> --FC42D820 ?
> --00001000 (LOADER.NLM|KernelAddressSpace+1000)
> --8F068300 ?
> --8EA354B0 ?
> --8EA354B0 ?
> --8EA35440 ?
> 0031ACB2 (SERVER.NLM|Alloc+FA)
> --8EA35440 ?
> --8EA354B0 ?
> -00440F3C (SERVER.NLM|xAllocSizeTable+54)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --8F0E5400 ?
>
> Additional Information:
> The NetWare OS detected a problem with the system while executing a
> process owned by LSL.NLM. It may be the source of the problem or there may
> have been a memory corruption.
>
> ... snip ...
>
> The Server also runs Border Manger 3.8 current SP.
>
> This Abend was documented and fixed in wsock6m, SP 7 contains a newer
> WSPIP.NLM but I get this Abend.
>
> Any ideas how to solve this issue ?
>
>
> Walter
>
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Antw: Re: Abend: Bad Resource Tag passed to LSLReturnRcvECB

Robert,

all products (NBM) and all drivers are patched to current level.
The Intel LAN cards the driver is end 2005 ...


With hyper threading I verify this on next Abend.

Creating a core dump is easy but where analyses the coredump?

I also attached 2 abend.logs

Walter


>>> Robert Charles Mahar<info@trafficshaper.com> schrieb am Montag, 22.

Oktober
2007 um 22:40 in Nachricht <rV7Ti.17194$NG7.2985@kovat.provo.novell.com>:
> Gack, I hate those.... Basically this means that something ate the
> resource header which precedes the ECB ( e.g. precedes the packet
> receive buffer in memory ) and when LSL goes to take ownership and
> change the resource in-use counters for the owner, it explodes because
> the resource tag points to oblivion.
>
> This can happen when a ECB is freed twice, or is corrupted some how, or
> when the resource tag is not managed properly. So its hard to track
> down what is causing the problem. Typically you need a core to figure
> out what is the real source of these.
>
> So we can vaguely blame it on Border Manager, right? 😉
>
> By any chance, do you have multiple processors on this box? If so,
> disable them and see if that gets you any stability. It might.
>
> Of course there is the general advice to patch the server, NBM, and the
> LAN drivers, ensure hyperthreading / virtual processor is disabled.
> Blah, blah, blah... its what we always say in here, I know. A full
> abend log with modules listing might help someone see a specific trouble
>
> spot.
>
> Also cross post or refer to this thread in a post to the NBM support
> forum, if you have not already.
>
> -- Bob
>
> - - - - - - - - - - - - - - - - -
> Robert Charles Mahar
> Traffic Shaping Engine for NetWare
> http://www.TrafficShaper.com
> - - - - - - - - - - - - - - - - -
>
>
> Walter Hofstädtler wrote:
>> Hi,
>>
>> last weekend I updated a NW 6.5 SP6 Server to SP7, now twice a day I get
>> this Abend:
>>
>> *********************************************************
>> Novell Open Enterprise Server, NetWare 6.5
>> PVER: 6.50.07
>>
>> Server ICC-DEMO halted Monday, 22 October 2007 19:51:07,679
>> Abend 1 on P00: Server-5.70.07-0: Bad Resource Tag passed to
>> LSLReturnRcvECB
>>
>> Registers:
>> CS = 0008 DS = 0023 ES = 0023 FS = 0023 GS = 0023 SS = 0010
>> EAX = 86E2D60D EBX = 00000000 ECX = 00000011 EDX = 00000A01
>> ESI = 870704C4 EDI = 00000000 EBP = 870704C4 ESP = 925E49B8
>> EIP = 870393DB FLAGS = 00000046
>> 870393DB 83C404 ADD ESP, 00000004
>> EIP in LSL.NLM at code start +000063DBh
>>
>> The violation occurred while processing the following instruction:
>> 870393DB 83C404 ADD ESP, 00000004
>> 870393DE B882FFFFFF MOV EAX, FFFFFF82
>> 870393E3 0BC0 OR EAX, EAX
>> 870393E5 C3 RET
>> 870393E6 0000 ADD [EAX], AL
>> 870393E8 0000 ADD [EAX], AL
>> 870393EA 0000 ADD [EAX], AL
>> 870393EC 0000 ADD [EAX], AL
>> 870393EE 0000 ADD [EAX], AL
>> LSL.NLM|LSLReturnRcvECBNoSave:
>> 870393F0 8B46FC MOV EAX, [ESI-04]
>>
>>
>>
>> Running process: Server 00:42 Process
>> Thread Owned by NLM: SERVER.NLM
>> Stack pointer: 925E4F40
>> OS Stack limit: 925DD000
>> Scheduling priority: 67371008
>> Wait state: 50500F0 Waiting for work
>> Stack: --86E2D60D ?
>> 8B910D2D (TCP.NLM|UDPSendToAllIf+70C9)
>> --870704C4 ?
>> --00000282 (LOADER.NLM|KernelAddressSpace+282)
>> --8BD17328 ?
>> 8B8F5398 (TCP.NLM|TCPAnyAddrCheck+2B18)
>> --925E4A4C ?
>> --7D9AF7B2 ?
>> --7D9A2912 ?
>> --8BD17328 ?
>> --925E4A4C ?
>> 8B8F440B (TCP.NLM|TCPAnyAddrCheck+1B8B)
>> --8BD17328 ?
>> --925E4A4C ?
>> --7D9AF7B2 ?
>> --00000028 (LOADER.NLM|KernelAddressSpace+28)
>> --3FFFFFFF ?
>> --8BD17328 ?
>> --00000001 (LOADER.NLM|KernelAddressSpace+1)
>> --925E4A4C ?
>> 8B8F4030 (TCP.NLM|TCPAnyAddrCheck+17B0)
>> --8BD17328 ?
>> --925E4A4C ?
>> --00000000 (LOADER.NLM|KernelAddressSpace+0)
>> --8BD17328 ?
>> --925E4A4C ?
>> 8B8F3A38 (TCP.NLM|TCPAnyAddrCheck+11B8)
>> --8BD17328 ?
>> --925E4A4C ?
>> 8B8FCD54 (TCP.NLM|TCPMPUnsafeConnectionLookup+5A8)
>> --87070522 ?
>> --8BD17328 ?
>> --8BD17328 ?
>> --925E4A4C ?
>> 8B8F2CC1 (TCP.NLM|TCPAnyAddrCheck+441)
>> --8BD17328 ?
>> --925E4A4C ?
>> --870704C4 ?
>> --925E4A78 ?
>> --925E4A88 ?
>> --10C6DC9D ?
>> --7D9A2912 ?
>> --10C6E250 ?
>> --000005B4 (LOADER.NLM|KernelAddressSpace+5B4)
>> --00000014 (LOADER.NLM|KernelAddressSpace+14)
>> --CEA00010 ?
>> --0000FFFF (LOADER.NLM|KernelAddressSpace+FFFF)
>> --00000000 (LOADER.NLM|KernelAddressSpace+0)
>> --23070210 ?
>> --71D82FD5 ?
>> --00000000 (LOADER.NLM|KernelAddressSpace+0)
>> --00000000 (LOADER.NLM|KernelAddressSpace+0)
>> --50000210 ?
>> --2160AFC6 ?
>> --00000000 (LOADER.NLM|KernelAddressSpace+0)
>> --00000000 (LOADER.NLM|KernelAddressSpace+0)
>> --00008051 (LOADER.NLM|KernelAddressSpace+8051)
>> --00000400 (LOADER.NLM|KernelAddressSpace+400)
>> --0000000A (LOADER.NLM|KernelAddressSpace+A)
>> --925E4ABC ?
>> --00000000 (LOADER.NLM|KernelAddressSpace+0)
>> --00008051 (LOADER.NLM|KernelAddressSpace+8051)
>> --00000010 (LOADER.NLM|KernelAddressSpace+10)
>> --90EBFFDC ?
>> --7FD378AC (ACPIPWR.NLM|__NLM_BSS_End+1FA8)
>> --00000000 (LOADER.NLM|KernelAddressSpace+0)
>> --00000000 (LOADER.NLM|KernelAddressSpace+0)
>> --00001000 (LOADER.NLM|KernelAddressSpace+1000)
>> --0000000F (LOADER.NLM|KernelAddressSpace+F)
>> --00000006 (LOADER.NLM|KernelAddressSpace+6)
>> --90EBF900 ?
>> --00000007 (LOADER.NLM|KernelAddressSpace+7)
>> --000000D5 (LOADER.NLM|KernelAddressSpace+D5)
>> --90EC001C ?
>> 8C4C09EA (NCPIP.NLM|ReplyKeepNoFragments+12A)
>> --90EBF90C ?
>> --FDFFFFFF ?
>> --00000011 (LOADER.NLM|KernelAddressSpace+11)
>> --90EBF99A ?
>> --925E4CF0 ?
>> --00000007 (LOADER.NLM|KernelAddressSpace+7)
>> --000000D5 (LOADER.NLM|KernelAddressSpace+D5)
>> --90EBF9C0 ?
>> 8A20B3AE (NCP.NLM|Case23+C2)
>> --90EBF9C0 ?
>> --000000D5 (LOADER.NLM|KernelAddressSpace+D5)
>> -00441AD0 (SERVER.NLM|xxLogNeqPhysSlabCache+0)
>> --FC42D820 ?
>> --00001000 (LOADER.NLM|KernelAddressSpace+1000)
>> --8F068300 ?
>> --8EA354B0 ?
>> --8EA354B0 ?
>> --8EA35440 ?
>> 0031ACB2 (SERVER.NLM|Alloc+FA)
>> --8EA35440 ?
>> --8EA354B0 ?
>> -00440F3C (SERVER.NLM|xAllocSizeTable+54)
>> --00000000 (LOADER.NLM|KernelAddressSpace+0)
>> --00000000 (LOADER.NLM|KernelAddressSpace+0)
>> --8F0E5400 ?
>>
>> Additional Information:
>> The NetWare OS detected a problem with the system while executing a
>> process owned by LSL.NLM. It may be the source of the problem or there

> may
>> have been a memory corruption.
>>
>> ... snip ...
>>
>> The Server also runs Border Manger 3.8 current SP.
>>
>> This Abend was documented and fixed in wsock6m, SP 7 contains a newer
>> WSPIP.NLM but I get this Abend.
>>
>> Any ideas how to solve this issue ?
>>
>>
>> Walter
>>
>>





0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Antw: Re: Abend: Bad Resource Tag passed to LSLReturnRcvECB

We have the same problem with nw65sp7 and bordermanager 3.9.
When unloading the http proxy the server stops abending?

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Antw: Re: Abend: Bad Resource Tag passed to LSLReturnRcvECB

Thanks to mysterious, our customers server has stopped abending woth this
error. He suggested that I install TCP680b.exe August 2007 over the SP7.

Since I did this, the server has stayed up for 2 hours (unlike before
where the maximum was 40 mins).

This may not be a fix, but everything is looking good at the moment, and
there were definate changes in the TCP/IP in SP7 from the above modules.

Hope this works,

Regards,

ChasR

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Antw: Re: Abend: Bad Resource Tag passed to LSLReturnRcvECB

Had to uninstall the SP7 as I was getting "out of short term memory
problems" with the GWIA, which would eventually cause the server to abend.
(Server is running both Border manager and Groupwise). The GWIA was
upgraded to the latest Hot Fix.

Regards,

ChasR.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Antw: Re: Abend: Bad Resource Tag passed to LSLReturnRcvECB

Hi,

I use BM, GWIA and Tobit on this server, no memory problems up to now.

Since down dating to TCP680b.exe the server is up for 3 hours now.


Walter



>>> ChasR<chas@northern-connection.co.uk> schrieb am Dienstag, 23. Oktober

2007
um 21:05 in Nachricht <xBrTi.17805$NG7.11573@kovat.provo.novell.com>:
> Had to uninstall the SP7 as I was getting "out of short term memory
> problems" with the GWIA, which would eventually cause the server to
> abend.
> (Server is running both Border manager and Groupwise). The GWIA was
> upgraded to the latest Hot Fix.
>
> Regards,
>
> ChasR.

0 Likes
snidelydev Absent Member.
Absent Member.

Re: Antw: Re: Abend: Bad Resource Tag passed to LSLReturnRcv

ChasR;1293099 wrote:
Had to uninstall the SP7 as I was getting "out of short term memory
problems" with the GWIA, which would eventually cause the server to abend.
(Server is running both Border manager and Groupwise). The GWIA was
upgraded to the latest Hot Fix.


Could you be as specific as possible about the configuration which had problems, so that someone can try to reproduce this? Are there any log files which include the error?

Also, did you back out the whole SP, or just specific parts? I ask because of your tcp msg before this.

/dps

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Abend: Bad Resource Tag passed to LSLReturnRcvECB

The abend log files are in the post Abend after Sp7. I did a complete back
out of Sp7 (Using NWCONFIG) which gets rid of any TCP/IP problems, but
beware that iManager no longer works (Separate post under iManaer). I am
still getting problems with running out of short term but this is not
connected.

Regards

Chasr

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.