Home > Backup Exec > Backup Exec Alert Catalog Error

Backup Exec Alert Catalog Error


Join the community of 500,000 technology professionals and ask your questions. CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical Covered by US Patent. We trying everything from repair DB, renaming Catalog folders, etc... http://waspsoft.com/backup-exec/backup-exec-alert-catalog-error-odbc-access-error.html

Backup jobs and catalog jobs appear to complete successfully with the alerts and events generated. 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 Veritas does not guarantee the accuracy regarding the completeness of the translation. Backup Exec Database (BEDD) is hosted on an invalid SQL Instance.  Solution: First make sure the SQL instance being used for the BEDB is a valid Instance.

Odbc Access Error Backup Exec 2010

Possible lost connection to database or unsuccessful access to catalog index in the database. Covered by US Patent. I've confirmed the catalog path is correct in the registry as well.

Type the follow and then press Enter: catrebuildindex -r 5. Renaming the Catalogs folder, restarting the services, and then deleting/renaming the original catalogs folder.2. Get 1:1 Help Now Advertise Here Enjoyed your answer? Backup Exec Catalog Files Regards, Operator 0 Message Expert Comment by:solomonraj_abba012009-02-21 I am still not able to grant access to the user account on the BEDB database as mentioned by you.

Corrupt catalogs in the Catalogs folder. Backup Exec 2012 Fehler Bei Odbc Zugriff when is it that you're getting the error mesages? - are they related to a specific task? Thank You! Also, the media labels that BE is using is nothing strange, we're using the following naming scheme: DLT000001.

However, when we try to run an Inventory, we receive the following error: "ODBC access error. Backup Exec Catalog Vs Inventory It is most common among "multi-step upgrades." For example, upgrading from 9.1 > 11d > 12.5 OR 10d > 12.0 > 12.5. Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. No Yes How can we make this article more helpful?

Backup Exec 2012 Fehler Bei Odbc Zugriff

Storage Storage Hardware Storage Software VMware Virtualization Password Protecting an External Drive Video by: doug This video teaches viewers how to encrypt an external drive that requires a password to read 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. Odbc Access Error Backup Exec 2010 After the process completes, scroll up and confirm the log show files were successfully migrated 6. Backup Exec 2014 Catalog Error Odbc Access Error Email Address (Optional) Your feedback has been submitted successfully!

I just deselected the IDR feature and clicked INSTALL. navigate here Sorry, we couldn't post your feedback right now, please try again later. Originally received: Sunday, January 28, 2007 9:00:14 AM 4 - ODBC access error. You may also refer to the English Version of this knowledge base article for up-to-date information. Backup Exec 11d Catalog

  • Solution: Stop all Backup Exec services.Rename the Catalogs folder to Catalogs_OLD (default location - x:\Program Files\Symantec\Backup Exec\)Run the steps from Solution 2 above.Start all BE services.
  • 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
  • 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.
  • it is now using the correct account to backup.
  • As you finish projects in Quip, the work remains, easily accessible to all team members, new and old. - Increase transparency - Onboard new hires faster - Access from mobile/offline Try
  • ODBC access error.

Please help! Possible lost connection to database or unsuccessful access to catalog index in the database. Errors occur after upgrading Backup Exec and selections are missing in the Restore Selections window http://support.veritas.com/docs/318287 After an Upgrade from Backup Exec for Windows 11d to Backup Exec 12, Catalog http://waspsoft.com/backup-exec/backup-exec-alert-media-error-the-backup-to-disk-device-is-offline.html In the mean time, would you happen to have any other ideas? 0 LVL 7 Overall: Level 7 Storage 1 Message Expert Comment by:CGretski2007-01-26 not off the top of my

Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. Backup Exec Catalog Media Password I have connected to the media server but it does not allow me to change any settings. Do I destroyed my BE installation ?

AND CatMedia.MediaFamilyGuid = ?

If the current Backup Exec version is 2010, run the osql scripts up to the 12_5 version and then run the "catrebuildindex -r". For more information, click the following link:http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml We have tried: 1. Refer to the Hotfix link under Related Articles to obtain the hotfix needed to resolve the issue. Backup Exec Catalog Job Queued Possible lost connection to database or unsuccessful access to catalog index in the database.

Does anyone have any other ideas? 0 Message Active 5 days ago Author Comment by:redmanjb2007-02-27 anyone? 0 Message Active 5 days ago Author Comment by:redmanjb2007-04-02 anyone? 0 LVL For a SSO Primary server: SSOState=1 Catalog Remote Server Name = (Does not exist) III. ODBC is an interface used to connect to databases, and if it can't connect it won't know where to save the catalogs. http://waspsoft.com/backup-exec/backup-exec-alert-device-error.html Blank restore selection list.

Possible lost connecti... Thanks for the assistance. All rights reserved. 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

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? But after the restart I get this error: ODBC access error. AND ImageObjectView.PlugInType = ? Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored procedure ‘UpdateCatMediaInfo'.

The alerts appear when the Backup Exec Services Start and during a backup or catalog job. George 0 Question by:Eprs_Admin Facebook Twitter LinkedIn Google LVL 23 Active 3 days ago Best Solution byIamthecreator You can refer to the following for possible reasons and the respective resolution. Posted on 2009-10-19 Storage Software 1 Verified Solution 3 Comments 2,349 Views Last Modified: 2013-12-01 Hello, with my BE 12.5 I tried to change some settings. Backup Exec Alert: Catalog Error ODBC access error.

Privacy Policy Site Map Support Terms of Use Bengts Blogg Varfr krngla till det? 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 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. I still receive the error messages.

All rights reserved Use of this Site constitutes acceptance of our User Agreement (effective 3/21/12) and Privacy Policy (effective 3/21/12), and Ars Technica Addendum (effective 5/17/2012) Your California Privacy Rights The