ODBC access error

[VinnyM0]

I've been fighting with this since I did a fresh install of BE15 on a clean install of WS2008. Deleting the catalogs bought me about 3 weeks with no ODBC errors. They're back again at a rate of about 2000/day. If it happens again the way it did last time, it will be up to 50000/day in a short time. Errors in event log are:

Access to catalog index (Catalog index database) failed.
Reason:  [Microsoft][ODBC SQL Server Driver][SQL Server]An error occurred in the Microsoft .NET Framework while trying to load assembly id 65536. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS o CCatRecordSet::Open
r:\maldives\1180r\becat\segodbc\seg_odbc.cpp(1889)
{ CALL DeleteCatMediaByMediaGuid( ?, ?, ? ) }

 For more information, click the following link:
http://entced.symantec.com/entt?product=BE&module=eng-event&error=V-379-34326&build=retail&version=14.2.1180.2113&language=EN&os=Windows_V-6.0.6002_SP-2.0_PL-0x2_SU-0x110_PT-0x3

and:

Backup Exec Alert: Catalog Error
(Server: "S20-DC001") ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database.

 For more information, click the following link:
http://entced.symantec.com/entt?product=BE&module=eng-event&error=V-379-34338&build=retail&version=14.2.1180.2113&language=EN&os=Windows_V-6.0.6002_SP-2.0_PL-0x2_SU-0x110_PT-0x3

FP3 is installed. Any help would be appreciated.

[pkh · Accepted solution]

See this document for a possible solution

http://www.veritas.com/docs/000099848

[mgmasterv2]

i have the same problem ,

this solution  http://www.veritas.com/docs/000099848 temporary solved my problem but after 1 day i get same errors ( i've done that 2 times but ODBC error comes backup)

[VJware]

This event is different from the one mentioned in the KB article -

Reason:  [Microsoft][ODBC SQL Server Driver][SQL Server]An error occurred in the Microsoft .NET Framework while trying to load assembly id 65536. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS o CCatRecordSet::Open
r:\maldives\1180r\becat\segodbc\seg_odbc.cpp(1889)

Do ensure the BE account has been granted Database Access using BEUtility. Granting "sa" may help as well.

Run the following script (Reference - https://support.microsoft.com/en-us/kb/918040)

USE bedb; 
EXEC Sp_Changedbowner 
'sa'; 
ALTER DATABASE bedb SET TRUSTWORTHY ON;

[pkh]

You need to install this hotfix.

http://www.veritas.com/docs/000080733

See the issue fixed section of the document.