Free detected corrupt trailing redzone when I start BE 9.0 - Veritas Backup Exec

This is a discussion on Free detected corrupt trailing redzone when I start BE 9.0 - Veritas Backup Exec ; I have BE9.0 on a Netware 6 SBS server with SP5. When I run BESTART, I get error 1006 loading BEPSVR.NLM on the SureStart thing, accompanied by a rapid series of of these errors on the console. 4-21-2005 7:37:52 pm: ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Free detected corrupt trailing redzone when I start BE 9.0

  1. Free detected corrupt trailing redzone when I start BE 9.0


    I have BE9.0 on a Netware 6 SBS server with SP5.
    When I run BESTART, I get error 1006 loading BEPSVR.NLM on the SureStart
    thing, accompanied by a rapid series of of these errors on the console.

    4-21-2005 7:37:52 pm: SERVER-5.60-834 [nmID=2000D]
    Free detected corrupt trailing redzone for node 0x8A247120, no

    4-21-2005 7:37:52 pm: SERVER-5.60-834 [nmID=2000D]
    Free detected corrupt trailing redzone for node 0x8A247180, no

    4-21-2005 7:37:52 pm: SERVER-5.60-834 [nmID=2000D]
    Free detected corrupt preceding redzone for node 0x8A2471C0

    4-21-2005 7:37:52 pm: SERVER-5.60-834 [nmID=2000D]
    Free detected corrupt trailing redzone for node 0x89B4F040, no

    4-21-2005 7:37:52 pm: SERVER-5.60-834 [nmID=2000D]
    Free detected corrupt preceding redzone for node 0x89B4F060

    4-21-2005 7:37:52 pm: SERVER-5.60-834 [nmID=2000D]
    Free detected corrupt preceding redzone for node 0x8A247140

    Any suggestions?


  2. Re: Free detected corrupt trailing redzone when I start BE 9.0

    Bill
    > I have BE9.0 on a Netware 6 SBS server with SP5.


    What build of BE9.0 is it?

    > When I run BESTART, I get error 1006 loading BEPSVR.NLM on the SureStart
    > thing,


    What's the exact message text of the 1006 error?

    > 4-21-2005 7:37:52 pm: SERVER-5.60-834 [nmID=2000D]
    > Free detected corrupt preceding redzone for node 0x8A247140


    Did you by any chance apply NW6LIB6A.EXE?
    See http://support.novell.com/cgi-bin/se...?/10095569.htm

    Michael
    --
    "If it jams, force it. If it breaks, you probably
    needed a new one anyway"

    * Please post replies via the newsgroup *

  3. Re: Free detected corrupt trailing redzone when I start BE 9.0


    Thanks very much for pointing out this TID.
    http://support.novell.com/cgi-bin/se...?/10095569.htm
    It appears to have fixed the problem.

    For the historical record, I'm using BE 9.0 Revision 4202.
    The original error I saw was...
    Error 1006:
    Error loading required module BEPSRV.NLM (or words to that effect)
    But after a while, I started getting a different error instead:
    Error: 1004
    A timeout occurred waiting for NDMPD.NLM to initialize.

    Both of these were accompanied by multiple "Free detected
    corrupt leading (or trailing) redzone..." errors.

    I don't remember ever applying NW6LIB6a, but I did recently
    upgrade eDirectory to 8.7.3, and the problem started shortly
    after that. So either I applied NW6LIB6a and forgot
    about it, or there's another way for the NCP.NLM bug to be
    exposed to Backup Exec. In any event the problem seems to
    be fixed by the patched NCP.NLM dated 11/22/2004.

    Thanks again for your help.

    Michael wrote:
    >Bill
    >> I have BE9.0 on a Netware 6 SBS server with SP5.

    >
    >What build of BE9.0 is it?
    >
    >> When I run BESTART, I get error 1006 loading BEPSVR.NLM on the SureStart
    >> thing,

    >
    >What's the exact message text of the 1006 error?
    >
    >> 4-21-2005 7:37:52 pm: SERVER-5.60-834 [nmID=2000D]
    >> Free detected corrupt preceding redzone for node 0x8A247140

    >
    >Did you by any chance apply NW6LIB6A.EXE?
    >See http://support.novell.com/cgi-bin/se...?/10095569.htm
    >
    >Michael
    >--
    >"If it jams, force it. If it breaks, you probably
    >needed a new one anyway"
    >
    >* Please post replies via the newsgroup *



  4. Re: Free detected corrupt trailing redzone when I start BE 9.0

    Bill
    > Thanks very much for pointing out this TID.
    > http://support.novell.com/cgi-bin/se...?/10095569.htm
    > It appears to have fixed the problem.


    Excellent news - thanks for the report back :-)

    Michael
    --
    "If it jams, force it. If it breaks, you probably
    needed a new one anyway"

    * Please post replies via the newsgroup *

+ Reply to Thread