NetWare 5.1 Server Abending after Veritas Backup Exec Loads

- Network:  NetWare 5.1 SP 6
- Server:  Compaq ProLiant ML350 G2
- Server Memory:  2GB

- Abend Date: 7/5/05

- Abend Error Msg:  Server PPISERV2 halted Tuesday, July 5, 2005   6:11:55.369 pm
  Abend 1 on P00: Server-5.00k: General Protection Processor Exception (Error code 00000000)

- Addl Abend.Log Info:  
    Registers:
    CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
    EAX = C37514F0 EBX = C374E8B8 ECX = 00000003 EDX = FFFFFFFF
    ESI = C5C31160 EDI = C374E9E0 EBP = C374E860 ESP = C374E84C
    EIP = C19FB399 FLAGS = 00010286
    C19FB399 8B12           MOV     EDX,[EDX]=?
    EIP in GWTSA.NLM at code start +00026399h

The violation occurred while processing the following instruction:
C19FB399 8B12           MOV     EDX,[EDX]
C19FB39B 8955F0         MOV     [EBP-10],EDX
C19FB39E 833DA4E5A0C100 CMP     [C1A0E5A4]=FFFFFFFF,00000000
C19FB3A5 740B           JZ      C19FB3B2
C19FB3A7 8B15A4E5A0C1   MOV     EDX,[C1A0E5A4]=FFFFFFFF
C19FB3AD 8B12           MOV     EDX,[EDX]
C19FB3AF 8955F4         MOV     [EBP-0C],EDX
C19FB3B2 E811EBE915     CALL    CLIB.NLM|__get_timezone
C19FB3B7 B93C000000     MOV     ECX,0000003C
C19FB3BC 8B00           MOV     EAX,[EAX]



Running process: VxNDMP_c42a5520 Process
Created by: NetWare Application
Thread Owned by NLM: NDMPD.NLM
Stack pointer: C374E200
OS Stack limit: C373F5E0
Scheduling priority: 67371008
Wait state: 5050030  (Blocked on Semaphore)
Stack: --C374E874  ?
       --00000E10  ?
       --00000001  ?
       --C374E8B8  ?
       --C374E8B8  ?
       --C374E874  ?
       C19FB25C  ?
       --C374ED44  ?
       --C3740001  ?
       --C5C31160  ?
       --C374EBF0  ?
       C19D7E69  (GWTSA.NLM|(Code Start)+2E69)
       --32E491B8  ?
       --C374E8B8  ?
       --7FFFFFFD  ?
       --00000000  ?
       --C374E880  ?
       --00000008  ?
       --C503B060  ?
       --00000002  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       00019904  (LOADER.EXE|(Code Start)+5694)
       --07D50246  ?
       --0D120407  ?
       --00000030  ?
       --00000000  ?
       --10000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000013  ?
       --00000000  ?
       --00000000  ?
       --C374D6DE  ?
       --00000004  ?
       --00000000  ?
       --00000000  ?
       --00000002  ?
       --00000000  ?
       --00000002  ?
       --00000001  ?
       --00000000  ?
       --00000000  ?
       --C374D6E0  ?
       --0000000A  ?
       --00000000  ?
       --00000000  ?
       --00000008  ?
       --C5C1BA69  ?
       --00000008  ?
       --20000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --20000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --20000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       
Additional Information:
    The CPU encountered a problem executing code in GWTSA.NLM.  The problem may be in that module or in data passed to     that module by a process owned by NDMPD.NLM.

- Background:  Server and all associated NLMS have been running fine.  No recent changes made to NOS.  No recent server     apps have been installed.  The server abended within a minute after Veritas BUEXEC loaded.  On 7/6/05 server experienced a recoverable abend at almost the same time as the unrecoverable abend on 7/5.  Below is a partial SYS$LOG.ERR:

 7-05-2005   6:11:57 pm:    SERVER-5.0-4631
   Severity = 3  Locus = 18  Class = 6
   WARNING! Server PPISERV2 experienced a critical error.  The offending process was suspended or recovered.  However, services hosted by this server may have been affected.

Please let me know if you need additional info.

Thanks your your help,
Gary
pcguru_garyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PsiCopCommented:
Are you running GroupWise on this server? If so, what version, SP level, and which agents?
PsiCopCommented:
Also, is this a clustered server?
ShineOnCommented:
What version and build number of Backup Exec is it?
OWASP Proactive Controls

Learn the most important control and control categories that every architect and developer should include in their projects.

pcguru_garyAuthor Commented:
GroupWise 6.5.2 MTA & POA are running on this server.  No, it is not a clustered server.
pcguru_garyAuthor Commented:
Running Backup Exec 9.10 Rev 1154 (current ver available).

Thanks
ShineOnCommented:
NDPS is running on this server, too?  Anything else?
PsiCopCommented:
Or SMDR? Putting together GroupWise v6.x, NetWare v5.x and SMDR can cause problems in GWTSA.NLM.

If you are loading SMDR but don't actually use it, ditch it.

If you load and use it, then try blanking its config (in SYS:ETC, I believe), which may have become corrupted.

I'd suggest moving to GroupWise v6.5 SP4, ditching GWTSA.NLM and using the TSAFS.NLM /ENABLEGW=YES option instead, but you're on NetWare v5.1, and I don't think TSAFS works with that old a version of NetWare.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pcguru_garyAuthor Commented:
Yes, NDPS Broker V 3.00g.  Also CA eTrust Antivirus 7.1 & NW Printer Server 5.00.  That's about it.  Server CPU utilization averages 8-10%.  Resources do not seem to be a problem.  Plenty of hard drive capacity(mirrored drives).  The BUExec config includes 2 HP SureStore 6000 drives configured as a cascaded pool.  I can email you the section of the Abend.Log as it pertains to this issue so you can see all loaded NLM's if you like.

Thanks
pcguru_garyAuthor Commented:
Not sure from where (or why) SMDR is loading .  It is not loaded separately in Autoexec.Ncf and don't see it in the other NCF's loading.  Do you know if it loads as part of the core OS?
ShineOnCommented:
Autoexec.ncf might be loading it using an NCF file, like SMSSTART.NCF.  If so, edit the SMSSTART.NCF and rem out the load of SMDR, just leaving the TSA loads - unless your TSA's are being loaded elsewhere, which makes it redundant, which would lead me to recommend REMming out the SMSSTART line in autoexec.ncf.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Novell Netware

From novice to tech pro — start learning today.