Home > Backup Exec > Backup Exec 2012 Odbc Access Error

Backup Exec 2012 Odbc Access Error

Contents

Create a new Catalog directory 4. You'll be able to use this tool to add the backup exec service account to have permissions on the database. The conflict occurred in database "BEDB", table "dbo.CatResource", column 'ResourceID'. 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 Source

Now go to the installation Directory C:\Program Files\Symantec\Backup Exec and rename the Catalogs folder. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem After applying Feature Pack 1 for Backup Exec 15, alerts and Windows events may No Yes How can we make this article more helpful? Sorry, we couldn't post your feedback right now, please try again later.

Backup Exec Alert Catalog Error

So I went to Programs and Features and changed the BE settings. Errors occur after upgrading Backup Exec and selections are missing in the Restore Selections window http://support.veritas.com/docs/318287 Go to Solution 3 Comments LVL 23 Overall: Level 23 Storage Software 20 Message Error Message Event Type: ErrorEvent Source: Backup Exec CatErrorHandler ServerEvent Category: NoneEvent ID: 34326Date:  8/30/2011Time:  1:35:45 PMUser:  N/AComputer: SERVERX64 Backup Exec Alert:ODBC access error.

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 Rename the Catalog directory u under the BE installation directory to Catalog.old 3. 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: Backup Exec 15 Odbc Access Error And also errors relating to "value out of range" When I try to restore the Backup Set Number that ends with a negative value (ie, -30577) and catalog File Name ending

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 Fehler Bei Odbc Zugriff Backup Exec 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.

Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'PK_CatDlmProcessedImage'. Possible lost connection to database or unsuccessful access to catalog index in the database" on restarting Backup Exec Services.

ODBC access error. Odbc Access Error Backup Exec 2015 Examine the services. We have a single BE 12 server. Hoping that they can resolve this quickly.

  1. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?
  2. Look for beutil.exe in the backup exec bin directory.
  3. Sorry, we couldn't post your feedback right now, please try again later.
  4. 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.

Fehler Bei Odbc Zugriff Backup Exec

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 As with Backup Exec 2012, the Backup Exec button in the upper left corner. Backup Exec Alert Catalog Error 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. Backup Exec 2012 Error 1603 Possible lost connection to database or unsuccessful access to catalog index in the database." Want to Advertise Here?

Thank You! this contact form Located in the BE install files WINNT\Install\SQLExpress\  Then use BEUtility to move BEDB to the SQL Express instance, Open BEUtility,Select All Media ServersOn the right column right click the Media Server Possible lost connection to database or unsuccessful access to catalog index in the database. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Backup Exec 2012 Error E000e020

Does anyone have any ideas on what maybe causing it?! We been receiving the following errors from all Windows, Linux and Mac servers. 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. http://sovidi.com/backup-exec/backup-exec-2012-odbc-error.php Please help!

ODBC access error. Odbc Access Error Backup Exec 2010 Was VJware Level 6 Employee Accredited Certified ‎10-04-2015 10:10 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content A quick Join & Ask a Question Need Help in Real-Time?

Power off the Tape Drive 3.

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 Possible lost connection to database or unsuccessful access to catalog index in the database. You may also refer to the English Version of this knowledge base article for up-to-date information. Catrebuildindex -r 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

what i can do to try and fix it? Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem After applying Backup Exec 2012 SP2 an ODBC access error Possible lost connection to 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 Check This Out Installed FP3 yesterday.

It takes some time before the alerts are deleted, after that, if you close Backup Exec GUI and start it again it is possible that you still have a slow GUI Access to catalog index (Catalog index database) failed. Do the following and see whether it solves the problem. 1. Email Address (Optional) Your feedback has been submitted successfully!

Backup Exec Alert: Catalog Error ODBC access error. Featured Post Why You Should Analyze Threat Actor TTPs Promoted by Recorded Future After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific How can I repair it ? 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

Article:000025591 Publish: Article URL:http://www.veritas.com/docs/000025591 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 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