waspsoft.com


Home > Backup Exec > Backup Exec 2012 Odbc Access Error Catalog Error

Backup Exec 2012 Odbc Access Error Catalog Error

Contents

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 Rename the Catalog directory u under the BE installation directory to Catalog.old 3. Either install or verify the certificate by using the vSphere Data Protection Configuration utility" when you are trying to connect to VDP instance from Vcenter. Sorry, we couldn't post your feedback right now, please try again later. http://waspsoft.com/backup-exec/backup-exec-2012-catalog-error-odbc.html

This will cause issues with DLM resulting in media protection and overwrite issues. Labels: 15 Backup and Recovery Backup Exec Error messages Patch Troubleshooting Upgrade Windows Server (2003-2008) 0 Kudos Reply 9 Replies I've read that this is fixed CraigV Moderator Partner Trusted Advisor 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 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

Odbc Access Error Backup Exec 2014

Log onto the Backup Exec Central Administration Server. we have about 60TB of physical storage across several servers of which we back up to 6TB on a weekly basis (which is another problem for another day) I attempted to it is now using the correct account to backup. 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

No Yes How can we make this article more helpful? From application event log: Access to catalog index (Catalog index database) failed. Access to catalog index (Catalog index database) failed. Catrebuildindex -r You can't delete all the alerts from the GUI, you need to do that with BEMCLI, because the GUI cannot delete all the items at once, the BEMCLI can!

Possible lost connection to database or unsuccessful access to catalog index in the database. Thanks for the assistance. 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 Suggested Solutions Title # Comments Views Activity vmware convert disk size changes from block to file level transfer 2 43 71d Tape vs RDX backup 7 25 15d vsphere 6.-0 limits

If the instance is a SQL MSDE 2000 instance that was not upgraded to SQL Express, this is the problem.  Install another instance with SQL Express installer. Event Id 34326 Backup Exec 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. In my situation I had to do it 15-20 times! 0 Kudos Reply Contact Privacy Policy Terms & Conditions Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Sorry, we couldn't post your feedback right now, please try again later.

Odbc Access Error Backup Exec 2010

Possible lost connection to database or unsuccessful access to catalog index in the database." Posted on 2008-01-10 Storage Software Windows Server 2003 1 Verified Solution 4 Comments 5,610 Views Last Modified: Regards! Odbc Access Error Backup Exec 2014 Do I destroyed my BE installation ? Backup Exec 15 Odbc Access Error Look for beutil.exe in the backup exec bin directory.

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 http://waspsoft.com/backup-exec/backup-exec-2010-catalog-error-odbc-access-error.html Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem The Alert appears when GRT (Granular Restore Technology) set is duplicated from Now go to the installation Directory C:\Program Files\Symantec\Backup Exec and rename the Catalogs folder. 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 Odbc Access Error Backup Exec 2015

As we are not able to do any kind of backups at this point we can not afford to start over and lose months of backups. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? No Yes Did this article save you the trouble of contacting technical support? have a peek here Thank You!

Veritas does not guarantee the accuracy regarding the completeness of the translation. V-280-2003 It is possible that updates have been made to the original version after this document was translated and published. 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:

No Yes How can we make this article more helpful?

Create/Manage Case QUESTIONS? No Yes How can we make this article more helpful? Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. Backup Exec 15 Catalog Error Odbc Access Error Microsoft .Net 3.5 is required.

Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page HELP!!! No Yes Did this article save you the trouble of contacting technical support? So far it looks promising. 0 Kudos Reply Re: BE15 14.2 Catalog Error / ODBC access error jan_villeres Level 4 Partner Accredited Certified ‎12-25-2015 09:40 PM Options Mark as New Bookmark http://waspsoft.com/backup-exec/backup-exec-alert-catalog-error-odbc-access-error.html The options for this are in the left pane at the bottom.

You may also refer to the English Version of this knowledge base article for up-to-date information. If the current Backup Exec version is 2010, run the osql scripts up to the 12_5 version and then run the "catrebuildindex -r". This by default is SQL Express but could be a full version of SQL. Connect with top rated Experts 9 Experts available now in Live!

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 Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? 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 No solution yet.

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.

The duplicate key value is (BE2012). Have worked with Veritas support for the last 2 weeks.

We been receiving the following errors from all Windows, Linux and Mac servers. database repair ended with errors. Join the community of 500,000 technology professionals and ask your questions. Did not make any difference ! 0 Kudos Reply You may have the issue Colin_Weaver Level 6 Employee Accredited Certified ‎12-16-2015 06:57 AM Options Mark as New Bookmark Subscribe Subscribe to

The most popular choice is the Mongoose library. what i can do to try and fix it?