Home > Backup Exec > Backup Exec Odbc Access Error

Backup Exec Odbc Access Error

Contents

Create/Manage Case QUESTIONS? 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 The conflict occurred in database "BEDB", table "dbo.CatResource", column 'ResourceID'. have a peek here

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 Please can someone provide some info or a solution.

Odbc Access Error Backup Exec 12

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 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 Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Corrupt database index of catalogs.  Solution: Run CatRebuildIndex to rebuild the Catalog indexes. (Figure 2) Stop all BE ServicesOpen command prompt and browse to x:\Program Files\Symantec\Backup ExecRun "CatRebuildIndex -r".Start all BE services.

Change the directory to the Backup Exec installation directory: \Program Files\Symantec\Backup Exec 4. Email Address (Optional) Your feedback has been submitted successfully! 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 Odbc Access Error Backup Exec 2015 Join Now For immediate help use Live now!

http://support.veritas.com/docs/288459 0 Message Active 1 day ago Author Comment by:Eprs_Admin2009-10-20 But no section fits here. 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 Great care should be taken when making changes to a Windows registry. No Yes How can we make this article more helpful?

checked FP3 install logs but no errors during the BEMIG. Odbc Access Error Backup Exec 2010 Email Address (Optional) Your feedback has been submitted successfully! No Yes Did this article save you the trouble of contacting technical support? Event Type: Error Event Source: Backup Exec CatErrorHandler Server Event Category: None Event ID: 34326 Description: Access to catalog index (Catalog index database) failed.

  1. All rights reserved.
  2. 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
  3. 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
  4. Join Now For immediate help use Live now!
  5. Join our community for more solutions or to ask questions.
  6. CCatRecordSet::Openr:\avian\1180.1160u\becat\segodbc\seg_odbc.cpp(1889){CALL CATDLM_New_GetExpirableMedia(?,?,?,?,?,?,?)}   Cause During the Data Lifecycle Management (DLM) grooming process of expired Microsoft Exchange backup sets, these alerts may occur.
  7. ODBC access error.

Backup Exec Odbc Access Error Catalog Error

No Yes How can we make this article more helpful? One of the following can be tried to resolve such issue: Resolution 1 1. Odbc Access Error Backup Exec 12 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. Fehler Bei Odbc Zugriff Backup Exec For information on how to contact Symantec Sales, please see http://www.symantec.com.ntec.com.   Terms of use for this information are found in Legal Notices.

Related Articles Article Languages x Translated Content

Try Free For 30 Days Suggested Solutions Title # Comments Views Activity EMC VNX storage pool Vs raid group question 3 77 110d iscsi and LUN discovery 1 43 103d Windows navigate here 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. Cause This Issue was Introduced with Backup Exec 2010 R3 Hotfix 159965.  The errors are cosmetic in nature.  The backup completes and data can be restored from the duplicated set.  Symantec recommends You'll need to connect to the media server with the tool first. 0 Message Author Comment by:Operator102008-01-10 Thanks AJ. Backup Exec 15 Odbc Access Error

Feature Pack for Microsoft SQL Server 2005 http://www.microsoft.com/downloads/details.aspx?FamilyID=50B97994-8453-4998-8226-FA42EC403D17&displaylang=en sqlncli.msi (Microsoft SQL Server Native Client) SQLServer2005_SQLCMD.msi (Microsoft SQL Server 2005 Command Line Query Utility SQLcmd) 2) Stop the Backup Exec services using This is how video conferencing should work! No Yes Did this article save you the trouble of contacting technical support? http://sovidi.com/backup-exec/backup-exec-2012-odbc-access-error.php 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

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. Event Id 34326 Backup Exec Possible lost connection to database or unsuccessful access to catalog index in the database. Join & Ask a Question Need Help in Real-Time?

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

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. Possible lost connection to database or unsuccessful access to catalog index in the database. Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored procedure ‘UpdateCatMediaInfo'. Catrebuildindex -r CCatRecordSet:pen r:\maldives\1180r\becat\segodbc\seg_odbc.cpp(1889) {CALL CATDLM_New_GetExpirableMedia(?,?,?,?,?,?,?)} Access to catalog index (Catalog index database) failed.

Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. If the current Backup Exec version is 2010 R2 or 2010 R3, run the osql scripts up to the 13_0 version and then run the "catrebuildindex -r".     4. Covered by US Patent. this contact form 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

Join the community of 500,000 technology professionals and ask your questions. Leave a Reply Cancel reply Enter your comment here... Veritas does not guarantee the accuracy regarding the completeness of the translation. 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:

How can I repair it ?