Hi,
This issue could occur if Backup Exec is installed on a case sensitive SQL instance. To avoid this problem , create SQL Server 2000 instance without
"case-sensitive" option.
It is usually recommended that backup exec be installed on the MSDE instance created by backup exec.please refer to the following Technote:
For optimal results, the Backup Exec Microsoft SQL Server Desktop Engine instance should not be installed into an existing SQL instance.
http://support.veritas.com/docs/273485
Hope it helps!
Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007
http://seer.support.veritas.com/docs/277429.htm
Note : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.