Both "ODBC access error" and ".NET Framework is disabled" messages are reported

Problem

"Execution of user code in the .NET Framework is disabled" is reported just before the "ODBC access error" message.
SQL server instance for Backup Exec (MSSQL$BKUPEXEC) reports "unloaded" messages before the disabled messages while running Backup Exec services.

Error Message

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

Error        Backup Exec CatErrorHandler Server    34327    None    "Update to catalog index (Catalog index database) failed.
Reason:  [Microsoft][ODBC SQL Server Driver][SQL Server]Execution of user code in the .NET Framework is disabled. Enable ""clr enabled"" configuration option. CCatRecordSet::ExecuteBulkInsert
r:\fox\1142r\becat\segodbc\seg_odbc.cpp(2681)
sp_sproc_columns CatImageInfoProc

Information        MSSQL$BKUPEXEC    6290    Server    AppDomain 7 (BEDB.dbo[ddl].6) unloaded.
Information        MSSQL$BKUPEXEC    6290    Server    AppDomain 6 (BEDB.dbo[ddl].5) unloaded.
Information        MSSQL$BKUPEXEC    6290    Server    AppDomain 5 (BEDB.dbo[ddl].4) unloaded.
Information        MSSQL$BKUPEXEC    6290    Server    AppDomain 4 (BEDB.dbo[ddl].3) unloaded.
Information        MSSQL$BKUPEXEC    6290    Server    AppDomain 3 (BEDB.dbo[ddl].2) unloaded.
Information        MSSQL$BKUPEXEC    6290    Server    AppDomain 2 (BEDB.dbo[ddl].1) unloaded.

UMI Code : V-280-2003

Cause

If the "unloaded" messages are reported while running Backup Exec services, those indicate that Common language runtime (CLR) functionality in the SQL instance is disabled from outside of Backup Exec.

Solution

Restart Backup Exec services.
Backup Exec enables the CLR functionality when starting up Backup Exec services.

Follow the next step if restarting Backup Exec service does not resolve the error message - "Execution of user code in the .NET Framework is disabled."

1. Stop the Backup Exec Services
2. Open command prompt

Start sqlcmd

sqlcmd -E -S .\bkupexec         (Backup Exec 21 or below)
sqlcmd -E -S .\bkupexec64     (Backup Exec 22)

or OSQL

osql -E -S .\bkupexec
osql -E -S .bkupexec64

3. Execute the following SQL commands:

1> sp_configure 'clr enabled', 1
2> go
Configuration option 'clr enabled' changed from 1 to 1. Run the RECONFIGURE statement to install.
1> reconfigure
2> go
1> USE bedb
2> go
Changed database context to 'BEDB'.
1> EXEC sp_changedbowner 'sa'
2> go
1> ALTER DATABASE bedb SET TRUSTWORTHY ON
2> go
1> exit

4. Start the Backup Exec services

SQL Management Studio Script/Query:

USE bedb
exec sp_configure 'clr enabled', 1
reconfigure
go
EXEC sp_changedbowner 'sa'
go
ALTER DATABASE bedb SET TRUSTWORTHY ON
go