Try this, from Veritas' web site... (looks like maybe adding the /NA switch to NWPA may be the start of the solution)
1. Check the order that the drivers are being loaded in the STARTUP.NCF file. The preferred order is as follows:
LOAD NWASPI.CDM
LOAD CPQSCSI.HAM
LOAD CPQSHD.CDM
2. NWASPI.CDM is the universal SCSI manager for HAM drivers and can be placed in the same directory as SERVER.EXE.
3. Do not load CPQSTP.CDM, NWTAPE.CDM, SCSI2TP.CDM, DLTTAPE.CDM, EXATAPE.CDM, or the SBACKUP driver, CPQSTAPE.DSK. These drivers can conflict with Backup Exec for NetWare's tape driver.
NOTE: These drivers should not be loaded while using Backup Exec for NetWare. These drivers provide support for the SBACKUP utility and compete with Backup Exec's drivers for the tape drives attached to the server. Sometimes NetWare 5 will auto load these drivers if NWPA.NLM is loaded during startup. Adding the /NA switch to the NWPA load line prevents NWPA from auto loading drivers. If otherCDM or HAM drivers were being loaded by NWPA and are required, the specific load statements will need to be added to the STARTUP.NCF file for those drivers after adding the /NA switch.