cpq32fs2 error after installing Backup Exec 8.X

[Ayman Altounji]

After installing Backup Exec 8.X, I get cpq32fs2 errors in the event log and they cause the Compaq foundation agents to timeout and not start. I've tried reapplying the latest SSD and the NT service pack but it doesn't help. Any ideas?
todd.strawser@firstunion.com

[Ayman Altounji]

The latest Smart Start DC is release 5.0. If you do not have the latest Smart start, you can down load Softpaq 14439 version 2.22 (www.compaq.com./support/files/allsp.html). It includes a fix for Veritas Backup Exes 8.0. Try applying the latest support software drivers and Insight Manager Agents, to the server. If problem still exists:

An issue exists between the Compaq SCSI driver, CPQ32FS2.SYS
Version 5.2.0.0 and VERITAS Backup Exec Version 8.0.

- The Compaq teaming driver, CPQTEAM.SYS v1.0.0.19 (or earlier)
registers as a service under the PNP_TDI group instead of
the NDIS group. When VERITAS stops and starts TDI services for
backups, this affects the teaming driver.

After the latest Support Paq from Compaq, for NT has been applied, perform the following changes to the registry using the Registry Editor.

-----------------------------------------------------------------
|CAUTION: Use the Registry Editor at your own risk! |
| |
| Using the Registry Editor incorrectly can cause serious |
| problems that may require a reinstallation of the |
| operating system. |
| |
| There is no guarantee that problems resulting from |
| incorrect usage of the Registry Editor can be solved. |
| |
| Ensure that a complete backup of the system has been |
| performed and an Emergency Repair Diskette (ERD) has been |
| created before proceeding with this Resolution. |
-----------------------------------------------------------------

1. Click Start, then Run.

2. Type REGEDT32 and click "OK".

3. Find the following entry in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CPQTeam

4. Change the "Group" value from:

PNP_TDI

To:

NDIS

5. Exit the Registry Editor.

6. Cold boot the server.