Home > Backup Exec > Backup Exec Odbc Access Error Possible Lost Connection To Database

Backup Exec Odbc Access Error Possible Lost Connection To Database

Contents

This by default is SQL Express but could be a full version of SQL. 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 No Yes Did this article save you the trouble of contacting technical support? 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 Source

But the ODBC errors are now gone. Create/Manage Case QUESTIONS? CCatRecordSet:pen r:\columbuscft_sp\1786.1059r\becat\segodbc\seg_odbc.cpp(1889) { CALL DeleteCatMediaByMediaGuid( ?, ?, ? ) } ;---- I would really like to get rid of this 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

Odbc Access Error Possible Lost Connection To Database Backup Exec 2015

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? 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 Sorry, we couldn't post your feedback right now, please try again later. Never did the catrebuildindex command though, so I´ll do that after SP2.

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. If the above steps do not correct the catalog issue, it may be necessary to start with a fresh catalog database.  This step should only be taken as a last resort Veritas does not guarantee the accuracy regarding the completeness of the translation. Odbc Access Error Backup Exec 2014 You'll be able to use this tool to add Go to Solution 4 Comments LVL 6 Overall: Level 6 Windows Server 2003 2 Storage Software 1 Message Accepted Solution by:AJermo2008-01-10

This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. Backup Exec Odbc Access Error. Possible Loss Connection still no luck! Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? No Yes Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Communities

Join the community of 500,000 technology professionals and ask your questions. Odbc Access Error Backup Exec 2010 You may also refer to the English Version of this knowledge base article for up-to-date information. AND CatMedia.Status & ? = 0 Case History Actions View Case Detail Add Case Comment Add Case Files Close Case Labels: 12.x and Earlier Backup and Recovery Backup Exec Backup Exec 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

  1. Built around industry best-practice guidelines, the IT Cyber Security bundle consists of three in-depth courses.
  2. Check It Out Suggested Solutions Title # Comments Views Activity SharePoint and OneDrive 1 43 42d How to Trigger Volume shadow copy (VSS) for a NAS Drive. 5 50 42d The
  3. And lots of other articles about this error seems to be related to an upgrade or migration.
  4. Backup Exec 15 Rev 1180 Hotfix 232086 (TECH232086).   Terms of use for this information are found in Legal Notices.

    Related Articles Article Languages x Translated Content Please note that
  5. No Yes Did this article save you the trouble of contacting technical support?
  6. It is possible that updates have been made to the original version after this document was translated and published.
  7. fl Level 4 ‎05-28-2010 11:21 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content We're having major issues with our
  8. Solved ODBC access error.
  9. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application.

Backup Exec Odbc Access Error. Possible Loss Connection

I have also removed the Catalog folder and let BE recrate it, and populate it with fullbackups to start over. You'll need to connect to the media server with the tool first. 0 Message Author Comment by:Operator102008-01-10 Thanks AJ. Odbc Access Error Possible Lost Connection To Database Backup Exec 2015 I just deselected the IDR feature and clicked INSTALL. Odbc Access Error Backup Exec 2012 Thank You!

Do I destroyed my BE installation ? this contact form 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 Email Address (Optional) Your feedback has been submitted successfully! Type the follow and then press Enter: catrebuildindex -r 5. Odbc Access Error Possible Lost Connection To Database Or Unsuccessful Access To Catalog Index In The Database

Selecting the right orchestration tool is most important for business specific needs. Possible lost connection to database or unsuccessful access to catalog index in the database alert appears during setcopy of a GRT enabled set post Hotfix 159965 for 2010 R3 Article:000013561 Publish: What is when I have installed 12.5 over my existing 12.5 installation ? 0 Message Active 1 day ago Author Comment by:Eprs_Admin2009-10-21 Can I do this or do I destroy have a peek here No Yes How can we make this article more helpful?

Thanks for the assistance. Backup Exec 15 Odbc Access Error It is possible that updates have been made to the original version after this document was translated and published. We been receiving the following errors from all Windows, Linux and Mac servers.

If I then restart(often using Task Manager for the Job engine) the services the backups resume.

Solution A hotfix is now available for this issue in the current version(s) of the product(s) mentioned in this article. i am logged with full access to the server 0 Message Author Comment by:Operator102008-01-10 Hi Aj, i have managed to change the user credentials on the schedule itself. In my attempts to fix this I have run lots of option in the BEUtility to repair the database. Event Id 34326 Backup Exec The installed IDR feature was installed and I do not need it.

Do advise on this. 0 Write Comment First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. Sorry, we couldn't post your feedback right now, please try again later. One of your technotes explain how to rebuild the catalog by removing and restarting. Check This Out You may also refer to the English Version of this knowledge base article for up-to-date information.

If I look in my Catalogs folder there are none of those, but if I enter the folder ALL files there ends with "_1" or "_2". Connect with top rated Experts 9 Experts available now in Live! Connect with top rated Experts 9 Experts available now in Live! 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.

Refer to the Hotfix link under Related Articles to obtain the hotfix needed to resolve the issue. ODBC access error.