waspsoft.com


Home > Backup Exec > Backup Exec Odbc Access Error 34338

Backup Exec Odbc Access Error 34338

Contents

The duplicate key value is (MEDIASERVERNAME). 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. This by default is SQL Express but could be a full version of SQL. Refer to the Hotfix link under Related Documents in this article to obtain the hotfix needed to resolve the issue. Backup Exec 15 Rev 1180 Feature Pack 1 (TECH228725).  This issue is resolved have a peek here

No Yes Did this article save you the trouble of contacting technical support? 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 Article:000019218 Publish: Article URL:http://www.veritas.com/docs/000019218 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 Veritas does not guarantee the accuracy regarding the completeness of the translation.

Odbc Access Error Backup Exec 2014

Please contact your Symantec Sales representative or the Symantec Partner for upgrade information including upgrade eligibility to the release containing the resolution for this issue. 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 Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Services Overview No Yes centosbeginer Just another WordPress.com site Search Main menu Skip to primary content HomeAbout Post navigation ← Previous Symantec Exec Backup: Error catalog after upgrade from 10.5D to12.5 Gallery Posted

Thank You! Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? For information on how to contact Symantec Sales, please see http://www.symantec.com.Applies ToBackup Exec 2012 SP2 SQL Agent Backups.   Terms of use for this information are found in Legal Notices.

Backup Exec 15 Odbc Access Error You may also refer to the English Version of this knowledge base article for up-to-date information.

For a SSO Secondary server: SSOState=2 Catalog Remote Server Name = (Name of primary server) Share this:TwitterFacebookLike this:Like Loading... c. https://www.veritas.com/community/articles/deleting-cleanup-many-alerts-if-gui-slow When BEMCLI is running you will notice in the GUIthat the amount of alerts will go down, when it shows 0 it's finished. Refer to the Hotfix link under Related Documents at the end of this article to obtain the hotfix needed to resolve the issue.

HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Server HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Catalogs I. Event Id 34326 Backup Exec Change the directory to the Backup Exec installation directory: \Program Files\Symantec\Backup Exec 4. Backup jobs and catalog jobs appear to complete successfully with the alerts and events generated. Change the directory to the Backup Exec installation directory: \Program Files\Symantec\Backup Exec 4.

  • viewing of backup sets stuck in loading...
  • Stopping the services and running the "CatRebuildIndex -R"  masks the issue in some cases but the problem reappears some time later.  Error Message The following error messages are registered periodically in
  • Sorry, we couldn't post your feedback right now, please try again later.
  • 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.
  • Hoping that they can resolve this quickly.
  • Was catrebuildindex -r run when the BE services were stopped ? 0 Kudos Reply Re: BE15 14.2 Catalog Error / ODBC access error leifr Level 2 Partner Accredited Certified ‎12-16-2015
  • Possible lost connection to database or unsuccessful access to catalog index in the database.
  • I'm hoping not to have to do a catalog rename. 0 Kudos Reply You need to clear all the rwolf82 Level 2 ‎02-03-2016 03:24 AM Options Mark as New Bookmark Subscribe
  • It is possible that updates have been made to the original version after this document was translated and published.

Odbc Access Error Backup Exec 2012

Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : BE15 14.2 Catalog Error / ODBC access error VOX : Backup and Recovery Sorry, we couldn't post your feedback right now, please try again later. Odbc Access Error Backup Exec 2014 Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Odbc Access Error Backup Exec 2010 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 now! Welcome First Last Your Profile Logout Sign in

Possible lost connection to database or unsuccessful access catalog index database Solution SYMPTOMS: 1. navigate here 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. Possible lost connection to database or unsuccessful access to catalog index in the database.   Source:  Backup Exec CatErrorHandler ServerEvent ID: 34327Error :  Update to catalog index (Catalog index database) failedReason:[Microsoft][ODBC Veritas does not guarantee the accuracy regarding the completeness of the translation. Backup Exec 2015 Odbc Access Error

Sorry, we couldn't post your feedback right now, please try again later. This entry was posted in Uncategorized by consoko. Possible lost connection to database or unssuccessful access to catalog index in the database Figure 1:    Cause This can occur due to connection issues to the Backup Exec database or Check This Out Email Address (Optional) Your feedback has been submitted successfully!

Reason: [Microsoft][ODBC Driver Manager] Function sequence error CCatRecordSet::GetRecordCount r:\maldives\1180r\becat\segodbc\seg_odbc.cpp(3629) {CALL CATDLM_New_GetExpirableMedia(?,?,?,?,?,?,?)} Itried to rebuild the catalog index with catrebuildindex -r , but it does not seems to help at Catrebuildindex -r database repair ended with errors. Create/Manage Case QUESTIONS?

The first is a generic ODBC event:  Log Name:      ApplicationSource:        Backup ExecEvent ID:      34338Task Category: NoneLevel:         ErrorKeywords:      ClassicDescription:Backup Exec Alert: Catalog Error(Server: "SERVERNAME") ODBC access error.

No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Run a Test Backup Job. Catrebuild -r doesn't work. V-280-2003 Possible lost connection to database or unsuccessful access to catalog index in the database.

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 No Yes Did this article save you the trouble of contacting technical support? Veritas does not guarantee the accuracy regarding the completeness of the translation. this contact form It is possible that updates have been made to the original version after this document was translated and published.

No Yes Did this article save you the trouble of contacting technical support? Installed FP3 yesterday.