Event Id 34338 Catalog Error
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs odbc access error backup exec 2014 Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research
Odbc Access Error Backup Exec 2015
Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português backup exec 15 odbc access error Español USA Site: Veritas Veritas PartnerNet ODBC Access errors. Event ID 34338 and 34327 reported on CAS server running Backup Exec 2012 Article:000016560 Publish: Article URL:http://www.veritas.com/docs/000016560
Odbc Access Error Backup Exec 2010
Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article event id 34326 backup exec Manage your Subscriptions Problem ODBC Access errors. Event ID 34338 and 34327 reported on CAS server running Backup Exec 2012 Error Message Following ODBC access errors are occasionally observed on CASO server : Log Name: Application Source: Backup Exec CatErrorHandler Server Event ID: 34327 Task Category: None Level: Error Description: Update to catalog index (Catalog index database) failed. Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]***** ERROR CatInsertContainerResourceAssociationProc: ResourceContainer_SynchFromCatalog catch error: DeviceName=Resource: Cannot insert duplicate key row in object 'dbo.ResourceContainer' with unique cat_RecordSet::ExecuteBulkInsert() r:\honshu\1798r\becat\segodbc\seg_odbc.cpp(3155) sp_sproc_columns CatInsertContainerResourceAssociationProc Log Name: Application Source: Backup Exec Event ID: 34338 Task Category: None Level: Error Description: Backup Exec Alert: Catalog Error (Server: "CAS Server name") ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database. Solution A hotfix is now available for this issue in the current version(s) of the product(s) mentioned in this article. Refer to the Hotfix link under Re
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER
Catrebuildindex -r
Customer Center Support Community MyVeritas Customer Success Licensing
V-280-2003
Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Getting "ODBC https://www.veritas.com/support/en_US/article.000016560 access error. Possible lost connection to database or unsuccessful access to catalog index in the database" on restarting Backup Exec Services. Article:000083813 Publish: Article URL:http://www.veritas.com/docs/000083813 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account https://www.veritas.com/support/en_US/article.TECH167225 now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem 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. Error Message Application Log Errors: Source: Backup Exec CatErrorHandler ServerEvent ID: 34327Error : Update to catalog index (Catalog index database) failed.Reason: D:\Catalogs\SERVER-NAME\{86794C68-8397-4F24-A2EA-404B54FED371}_31.xml PerformBulkInsert() e:\nicobar\5204r\becat\catindex\dll\..\catdbupdatethread.cpp(447) Source: Backup ExecEvent ID: 34338Error : Backup Exec Alert: Catalog Error (Server: "SERVER-NAME") ODBC access error. Possible lost connection to database or unsucces
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 https://centosbeginer.wordpress.com/2011/07/12/symantec-exec-backup-error-catalog-after-upgrade-from-10-5d-to-12-5/ 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 backup exec 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:\catalina\1364r\becat\segodbc\seg_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 odbc access error 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:\catalina\1364r\becat\segodbc\seg_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 is