Backup exec ошибка доступа к odbc

Click here follow the steps to fix Odbc Access Error Backup Exec 2012 and related errors.

Instructions

Note:
This article was updated on 2023-02-03 and previously published under WIKI_Q210794

What is Odbc Access Error Backup Exec 2012 error?

The Odbc Access Error Backup Exec 2012 error is the Hexadecimal format of the error caused. This is common error code format used by windows and other windows compatible software and driver vendors.

This code is used by the vendor to identify the error caused. This Odbc Access Error Backup Exec 2012 error code has a numeric error number and a technical description. In some cases the error may have more parameters in Odbc Access Error Backup Exec 2012 format .This additional hexadecimal code are the address of the memory locations where the instruction(s) was loaded at the time of the error.

What causes Odbc Access Error Backup Exec 2012 error?

The Odbc Access Error Backup Exec 2012 error may be caused by windows system files damage. The corrupted system files entries can be a real threat to the well being of your computer.

There can be many events which may have resulted in the system files errors. An incomplete installation, an incomplete uninstall, improper deletion of applications or hardware. It can also be caused if your computer is recovered from a virus or adware/spyware
attack or by an improper shutdown of the computer. All the above actives
may result in the deletion or corruption of the entries in the windows
system files. This corrupted system file will lead to the missing and wrongly
linked information and files needed for the proper working of the
application.

How to easily fix Odbc Access Error Backup Exec 2012 error?

There are two (2) ways to fix Odbc Access Error Backup Exec 2012 Error:

Advanced Computer User Solution (manual update):

1) Start your computer and log on as an administrator.

2) Click the Start button then select All Programs, Accessories, System Tools, and then click System Restore.

3) In the new window, select «Restore my computer to an earlier time» option and then click Next.

4) Select the most recent system restore point from the «On this list, click a restore point» list, and then click Next.

5) Click Next on the confirmation window.

6) Restarts the computer when the restoration is finished.

Novice Computer User Solution (completely automated):

1) Download (Odbc Access Error Backup Exec 2012) repair utility.

2) Install program and click Scan button.

3) Click the Fix Errors button when scan is completed.

4) Restart your computer.

How does it work?

This tool will scan and diagnose, then repairs, your PC with patent
pending technology that fix your windows operating system registry
structure.
basic features: (repairs system freezing and rebooting issues , start-up customization , browser helper object management , program removal management , live updates , windows structure repair.)

Follow one of those solutions:

Link 1
http://www.symantec.com/business/support/index?page=content&id=TECH59749

Problem

After an Upgrade from Backup Exec for Windows 11d to Backup Exec 12 or 12.5 Catalog Error “ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database” when the Backup Exec Database (BEDB) is located on a remote SQL Server or not in the default named SQL (BKUPEXEC) Instance.

Error

Event Viewer Application Log:

Event Type: Error
Event Source: Backup Exec CatErrorHandler Server
Event Category: None
Event ID: 34326
Description:
Access to catalog index (Catalog index database) failed.
Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored
procedure ‘UpdateCatMediaInfo’. cat_RecordSet::Open()
r:catalina1364rbecatsegodbcseg_odbc.cpp(2404)
{CALL UpdateCatMediaInfo( ?, ?, ?, ?) }

Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 34338
Description:
Backup Exec Alert: Catalog Error
(Server: “SERVERNAME”) ODBC access error. Possible lost connection to database or
unsuccessful access to catalog index in the database.

Event Type: Error
Event Source: Backup Exec CatErrorHandler Server
Event Category: None
Event ID: 34326
Description:
Access to catalog index (Catalog index database) failed.
Reason: Data type mismatch cat_RecordSet::SetField()
r:catalina1364rbecatsegodbcseg_odbc.cpp(3613)
sp_sproc_columns CatImageInfoProc

Environment

The Backup Exec Database (BEDB) is located on a remote SQL Server or is not in the default named SQL (BKUPEXEC) Instance.

Solution

After an upgrade from Backup Exec 11d to Backup Exec 12.0 or 12.5 multiple Catalog Errors appear in the Application Log and the Backup Exec Alerts tab when the Backup Exec database (BEDB) is located on a remote SQL server or not in the default named (BKUPEXEC) SQL instance. The alerts appear when the Backup Exec Services Start and during a backup or catalog job. Backup jobs and catalog jobs appear to complete successfully with the alerts and events generated. After a catalog job is performed the restore selections may show partial or no restore selections.

(FIGURE A)

Solution:

NOTE: There are three possible solutions to resolve this issue.

Solution A

1) Download and install The Microsoft SQL 2005 Server Native Client and SQL 2005 command line query utility “sqlcmd” on the media server.

Feature Pack for Microsoft SQL Server 2005
http://www.microsoft.com/downloads/details.aspx?FamilyID=50B97994-8453-4998-8226-FA42EC403D17&displaylang=en

sqlncli.msi (Microsoft SQL Server Native Client)
SQLServer2005_SQLCMD.msi (Microsoft SQL Server 2005 Command Line Query Utility SQLcmd)

2) Stop the Backup Exec services using servicesmgr.exe

3) Open a command prompt on the Media Server to the Backup Exec install directory (C:program
filessymantecbackup exec)

4) Issue the following command:

sqlcmd -E -S %COMPUTERNAME% -dbedb -icatupgrade_12_0.sql

Where %COMPUTERNAME% is the remote SQL server name

Example: C:program filessymantecbackup execsqlcmd -E -S sqlserver01 -dbedb -icatupgrade_12_0.sql

Note: If the Backup Exec database (BEDB) is installed into a “named” SQL instance issue the following command:

sqlcmd -E -S %COMPUTERNAME%%INSTANCENAME% -dbedb -icatupgrade_12_0.sql

Where %COMPUTERNAME% is the remote SQL server name
Where %INSTANCENAME% is the named SQL instance name

Example: C:program filessymantecbackup execsqlcmd -E -S sqlserver01sqlinstance -dbedb -icatupgrade_12_0.sql

5) Start the Backup Exec Services using servicesmgr.exe

OR

Solution B

1) Stop the Backup Exec Services using servicesmgr.exe

2) Copy the sql script catupgrade_12_0.sql from the Backup Exec for Windows Media Server (X:program filessymantecbackup execcatupgrade_12_0.sql) to C:temp on the SQL server hosting the Backup Exec (BEDB) database.

3) Go to the SQL server and open a command prompt to c:temp, then issue the following command:

osql -E -S %COMPUTERNAME% -dbedb -icatupgrade_12_0.sql

Where %COMPUTERNAME% is the SQL server name

Example: C:tempOSQL -E -S sqlserver01 -dbedb -icatupgrade_12_0.sql

(FIGURE B)

Note: If the Backup Exec database (BEDB) is installed into a “named” SQL instance issue the following command:

osql -E -S %COMPUTERNAME%%INSTANCENAME% -dbedb -icatupgrade_12_0.sql

Where %COMPUTERNAME% is the SQL server name
Where %INSTANCENAME% is the named SQL instance name

Example: C:tempOSQL -E -S sqlserver01sqlinstance -dbedb -icatupgrade_12_0.sql

4) Start the Backup Exec Services using servicesmgr.exe

If the ODBC access errors are still displayed in the Alerts, proceed with Solution C.

Solution C

1. Stop the Backup Exec Services using servicesmgr.exe

2. Open a command prompt on the media server

3. Change the directory to the Backup Exec installation directory:

Program FilesSymantecBackup Exec

4. Type the follow and then press Enter:

catrebuildindex -r

5. After the process completes, scroll up and confirm the log show files were successfully migrated

6. Start all of the Backup Exec services using servicesmgr.exe

7. Run a Test Backup Job.

Note: In some cases, it may be necessary to clear the alerts tab and reboot the server after performing the steps above.

If we get the above error when the backup job is running on a specific backup to disk folder , delete the folder.cfg and changer.cfg and run an inventory on the backup to disk folder . This will recreate the folder.cfg and changer.cfg .

Link 2

http://www.symantec.com/business/support/index?page=content&id=TECH67271

Problem

‘ODBC access error’ occurs after upgrading Backup Exec and/or selections are missing in the Restore Selections window.

Error

ODBC access error. Possible lost connection to database or unsuccessful access catalog index database

Solution

SYMPTOMS:

1. ERROR: ODBC access error. Possible lost connection to database or unsuccessful access catalog index database

2. Blank restore selection list.

ISSUE:

This error usually occurs after an upgrade. It is most common among “multi-step upgrades.” For example, upgrading from 9.1 > 11d > 12.5 OR 10d > 12.0 > 12.5. Multiple alerts and notifications regarding the catalogs are seen in the Windows Event Viewer and the Backup Exec Alerts tab.

One of the following can be tried to resolve such issue:

Resolution 1

1. Stop the Backup Exec Services.

2. Open a command prompt on the media server

3. Change the directory to the Backup Exec installation directory: Program FilesSymantecBackup Exec

4. Type the follow and then press Enter: catrebuildindex -r

5. After the process completes, scroll up and confirm the log show files were successfully migrated

6. Restart all of the Backup Exec Services on the media server.

Note: In some cases, it may be necessary to clear the alerts tab and reboot the server after performing the steps above.

Resolution 2

Change the location of Catalogs folder to another volume using Beutility. For more details on how to change location of catalogs refer to the link below:

http://support.veritas.com/docs/286689

Resolution 3

Ensure the value of the following registry keys are as mentioned below.(Depending on the Backup Exec Server configuration)

Warning: Incorrect use of the Windows Registry Editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

HKEY_LOCAL_MACHINESOFTWARESymantecBackup Exec For WindowsBackup ExecServer

HKEY_LOCAL_MACHINESOFTWARESymantecBackup Exec For WindowsBackup ExecCatalogs

I. For a Standalone Backup Exec server:

SSOState=0

Catalog Remote Server Name = (Does not exist)

II. For a SSO Primary server:

SSOState=1

Catalog Remote Server Name = (Does not exist)

III. For a SSO Secondary server:

SSOState=2

Catalog Remote Server Name = (Name of primary server)

On Server A I run the following code and it runs successfully.

DECLARE @server_name   VARCHAR(100);
DECLARE @instance_name VARCHAR(100);
DECLARE @cmdline       VARCHAR(2000);

SET @server_name   = ‘ServerA’;
SET @instance_name = ‘InstanceNameHere’;

SET @cmdline =’ bcp «SELECT DISTINCT + «»%sql_dir%tdpsqlc backup «» + rtrim(ltrim(a.name))  + «» full /configfile=%cfg_dir%’ + @server_name + ‘_tdpsql.cfg /tsmoptfile=%cfg_dir%SQLServer_dsm.opt
/logfile=%cfg_dir%BACKUP_FULL_User_Databases.rpt >> %rpt_dir%BACKUP_FULL_User_Databases.rpt»» FROM sys.databases a WHERE a.database_ID > 4 AND state_desc != »OFFLINE» AND a.name NOT IN (SELECT DISTINCT dbcs.database_name AS [DatabaseName]
FROM master.sys.availability_groups AS AG LEFT OUTER JOIN master.sys.dm_hadr_availability_group_states as agstates   ON AG.group_id = agstates.group_id INNER JOIN master.sys.availability_replicas AS AR   ON AG.group_id = AR.group_id INNER
JOIN master.sys.dm_hadr_availability_replica_states AS arstates   ON AR.replica_id = arstates.replica_id AND arstates.is_local = 1 INNER JOIN master.sys.dm_hadr_database_replica_cluster_states AS dbcs   ON arstates.replica_id = dbcs.replica_id
LEFT OUTER JOIN master.sys.dm_hadr_database_replica_states AS dbrs   ON dbcs.replica_id = dbrs.replica_id AND dbcs.group_database_id = dbrs.group_database_id WHERE ISNULL(arstates.role, 3) = 2 AND ISNULL(dbcs.is_database_joined, 0) = 1)» queryout
«G:’+@instance_name+’BACKUPTSM_Jobs’+@instance_name+’BackupsBACKUP_FULL_User_Databases_Part2.txt» -c -T -x
-S’+@server_name +»+@instance_name

—PRINT @cmdline

EXEC master..xp_cmdshell @cmdline

Now I go onto a second server, Server B, and run the same code.  Just changing the parameter for the server name and instance name.  I get the following error message.

SQLState = S1000, NativeError = 0
Error = [Microsoft][ODBC Driver 13 for SQL Server]Unable to open BCP host data-file
NULL

So I attempted to place the full path for the bcp.  Here is the code

DECLARE @server_name   VARCHAR(100);
DECLARE @instance_name VARCHAR(100);
DECLARE @cmdline       VARCHAR(2000);

SET @server_name   = ‘ServerB’;
SET @instance_name = ‘InstanceNameHere’;

SET @cmdline =’ C:Program Files (x86)Microsoft SQL ServerClient SDKODBC130ToolsBinnbcp.exe «SELECT DISTINCT + «»%sql_dir%tdpsqlc backup «» + rtrim(ltrim(a.name))  + «» full /configfile=%cfg_dir%’
+ @server_name + ‘_tdpsql.cfg /tsmoptfile=%cfg_dir%SQLServer_dsm.opt /logfile=%cfg_dir%BACKUP_FULL_User_Databases.rpt >> %rpt_dir%BACKUP_FULL_User_Databases.rpt»» FROM sys.databases a WHERE a.database_ID > 4 AND state_desc !=
»OFFLINE» AND a.name NOT IN (SELECT DISTINCT dbcs.database_name AS [DatabaseName] FROM master.sys.availability_groups AS AG LEFT OUTER JOIN master.sys.dm_hadr_availability_group_states as agstates   ON AG.group_id = agstates.group_id INNER JOIN
master.sys.availability_replicas AS AR   ON AG.group_id = AR.group_id INNER JOIN master.sys.dm_hadr_availability_replica_states AS arstates   ON AR.replica_id = arstates.replica_id AND arstates.is_local = 1 INNER JOIN master.sys.dm_hadr_database_replica_cluster_states
AS dbcs   ON arstates.replica_id = dbcs.replica_id LEFT OUTER JOIN master.sys.dm_hadr_database_replica_states AS dbrs   ON dbcs.replica_id = dbrs.replica_id AND dbcs.group_database_id = dbrs.group_database_id WHERE ISNULL(arstates.role,
3) = 2 AND ISNULL(dbcs.is_database_joined, 0) = 1)» queryout «G:’+@instance_name+’BACKUPTSM_Jobs’+@instance_name+’BackupsBACKUP_FULL_User_Databases_Part2.txt» -c -T -x
-S’+@server_name +»+@instance_name

—PRINT @cmdline

EXEC master..xp_cmdshell @cmdline

But then I get the message

‘C:Program’ is not recognized as an internal or external command,
operable program or batch file.
NULL

So then I tried to place quotes around the executable but I must have place them inappropriatly?  Here is the code now.

DECLARE @server_name   VARCHAR(100);
DECLARE @instance_name VARCHAR(100);
DECLARE @cmdline       VARCHAR(2000);

SET @server_name   = ‘ServerB’;
SET @instance_name = ‘InstanceNameHere’;

SET @cmdline =’ «C:Program Files (x86)Microsoft SQL ServerClient SDKODBC130ToolsBinnbcp.exe» «SELECT DISTINCT + «»%sql_dir%tdpsqlc backup «» + rtrim(ltrim(a.name))  + «» full /configfile=%cfg_dir%’
+ @server_name + ‘_tdpsql.cfg /tsmoptfile=%cfg_dir%SQLServer_dsm.opt /logfile=%cfg_dir%BACKUP_FULL_User_Databases.rpt >> %rpt_dir%BACKUP_FULL_User_Databases.rpt»» FROM sys.databases a WHERE a.database_ID > 4 AND state_desc !=
»OFFLINE» AND a.name NOT IN (SELECT DISTINCT dbcs.database_name AS [DatabaseName] FROM master.sys.availability_groups AS AG LEFT OUTER JOIN master.sys.dm_hadr_availability_group_states as agstates   ON AG.group_id = agstates.group_id INNER JOIN
master.sys.availability_replicas AS AR   ON AG.group_id = AR.group_id INNER JOIN master.sys.dm_hadr_availability_replica_states AS arstates   ON AR.replica_id = arstates.replica_id AND arstates.is_local = 1 INNER JOIN master.sys.dm_hadr_database_replica_cluster_states
AS dbcs   ON arstates.replica_id = dbcs.replica_id LEFT OUTER JOIN master.sys.dm_hadr_database_replica_states AS dbrs   ON dbcs.replica_id = dbrs.replica_id AND dbcs.group_database_id = dbrs.group_database_id WHERE ISNULL(arstates.role,
3) = 2 AND ISNULL(dbcs.is_database_joined, 0) = 1)» queryout «G:’+@instance_name+’BACKUPTSM_Jobs’+@instance_name+’BackupsBACKUP_FULL_User_Databases_Part2.txt» -c -T -x
-S’+@server_name +»+@instance_name

—PRINT @cmdline

EXEC master..xp_cmdshell @cmdline

‘C:Program’ is not recognized as an internal or external command,
operable program or batch file.
NULL

Have I placed the double quotes in the wrong spot?

lcerni

Backup Exec services lots of «ODBC access error

Con la herramienta de backup , backup exec, tenemos el siguiente mensaje de error:

After restarting the Backup Exec services lots of «ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database» is received in the Application Log and also similar alerts are generated in Alerts tab in Backup Exec.

El backup comienza a realizarse correctamente, y al final acaba bien, no obstante el problema viene cuando probamos a restaurar, no nos deja debido a que no puede almacenar en la base de datos los indices para restaurar.

Hay un hotfix según veritas:

Backup Exec 15 Rev 1180 Feature Pack 1 (TECH228725).

El problema es que NO nos sirve ya que en nuestro caso ya tenemos una revisión mayor.

Por tanto, única solución, siguiente script para la bd.

C:UsersAdministrator>osql -E -S localhostbkupexec
1> USE bedb;
2> go
1> EXEC Sp_Changedbowner ‘sa’;
2> go
1> ALTER DATABASE bedb SET TRUSTWORTHY ON;
2> go
1> sp_configure ‘show advanced options’, 1;
2> go
Configuration option ‘show advanced options’ changed from 1 to 1. Run the
RECONFIGURE statement to install.
1> RECONFIGURE;
2> go
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
1> if exists (select * from dbo.sysobjects where name =
‘PK_CatDlmProcessedImage
‘) exec (‘ALTER TABLE [dbo].[CatDlmProcessedImage] DROP CONSTRAINT
[PK_CatDlmPro
cessedImage]’;
2> go
Msg 102, Level 15, State 1, Server MCWINBCKPBKUPEXEC, Line 1
Incorrect syntax near ‘;’.
1> if exists (select * from dbo.sysobjects where name =
‘PK_CatDlmProcessedImage
‘) exec (‘ALTER TABLE [dbo].[CatDlmProcessedImage] DROP CONSTRAINT
[PK_CatDlmPro
cessedImage]’
2> go
Msg 102, Level 15, State 1, Server MCWINBCKPBKUPEXEC, Line 1
Incorrect syntax near ‘ALTER TABLE [dbo].[CatDlmProcessedImage] DROP
CONSTRAINT
[PK_CatDlmProcessedImage]’.
1> exit

Por si a alguien le ocurre, que no dé mil vueltas …(a no ser que tenga la versión que dice la revisión).

Un saludo,