waspsoft.com


Home > Backup Exec > Backup Exec Catalog Error 34338

Backup Exec Catalog Error 34338

Contents

Connect with top rated Experts 9 Experts available now in Live! Some have a Symantec windows agent for GRT and some do not. Thank You! Resolution 2 Change the location of Catalogs folder to another volume using Beutility. Source

It is possible that updates have been made to the original version after this document was translated and published. 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 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. Stop the Backup Exec Services using servicesmgr.exe 2.

Backup Exec 11d Catalog

But when we try to restore mail items, the jobs are failed and we have the following errors in the Job Status: read more

0 0 10/12/15--05:50: Backup sets not removed Privacy Policy Site Map Support Terms of Use MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Contribute Products BackProducts Gigs Live Careers Vendor Services Groups Website No Yes How can we make this article more helpful?

  • Article:000087955 Publish: Article URL:http://www.veritas.com/docs/000087955 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
  • I can still see all these files on the server but for some reasone BE can't find them or access them.
  • This will clear all BE database.
  • Email Address (Optional) Your feedback has been submitted successfully!
  • 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
  • i re-installed the licenses but the error is still persistent.
  • For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml and this: Event Type: Error Event Source: Backup Exec CatErrorHandler Server Event Category: None Event ID: 34326 Date: 1/24/2007 Time: 7:52:09 AM User:
  • CCatRecordSet::Open    r:\maldives\1180r\becat\segodbc\seg_odbc.cpp(1889)    {CALL CATDLM_New_GetExpirableMedia(?,?,?,?,?,?,?)} Solution A hotfix is now available for this issue in the current version(s) of the product(s) mentioned in this article.
  • Get 1:1 Help Now Advertise Here Enjoyed your answer?

Each day, I receive an alter (informational and error) similar to the ones below: 1 - 4:00am - Maintenance of application databases on server CLW-NAS\BkupExec has started. 2 - 4:00am - Type the follow and then press Enter: catrebuildindex -r 5. Possible lost connection to database or unsuccessful access catalog index database Solution SYMPTOMS: 1. Backup Exec Catalog Job Queued You may also refer to the English Version of this knowledge base article for up-to-date information.

Make sure to backup all files before reformatting. Backup Exec Catalog Files My database maintenance change didn't correct the problem but I did finally track down a veritas support article that verifies that this problem occurs when upgrading from version 9 to 11 Solved how to i resolve this error "ODBC access error. How do I create 2 separate Backup jobs that target the same vCenter so I can GRT and non-GRT jobs?

read more

0 0 10/14/15--06:24: VMware backups greatly slowed down Contact us about this article I need a solution I've been running BE15 for a while and it started out Backup Exec Catalog Files Too Large It may be Monday until I post back with the results. You may also refer to the English Version of this knowledge base article for up-to-date information. No Yes centosbeginer Just another WordPress.com site Search Main menu Skip to primary content HomeAbout Post navigation ← Previous Symantec Exec Backup: Error catalog after upgrade from 10.5D to12.5 Gallery Posted

Backup Exec Catalog Files

Or you are searching for a contact that you erased from your MS Outlook ‘Contacts’ folder and now realized that it was important. It is possible that updates have been made to the original version after this document was translated and published. Backup Exec 11d Catalog Then from the windows application event log I got the details of these errors as below:Event ID: 34326Access to catalog index (Catalog index database) failed.Reason:  [Microsoft][ODBC SQL Server Driver][SQL Server]Procedure or Backup Exec Catalog Vs Inventory Suggested Solutions Title # Comments Views Activity Clickfree HD 7 74 102d can not format usb drive says write protected 11 58 78d Recommendation for a 'server' for a 3 computer

I've confirmed the catalog path is correct in the registry as well. this contact form For a Standalone Backup Exec server: SSOState=0 Catalog Remote Server Name = (Does not exist) II. Sorry, we couldn't post your feedback right now, please try again later. Possible lost connection to database or unsuccessful access to catalog index in the database. Backup Exec Catalog Media Password

To install the necessary roles, go to Server Manager, and select Add Roles and Featu… Windows Server 2012 Storage Software Storage Reformatting Your Flash Drive Video by: Faizan This Micro Tutorial Sorry, we couldn't post your feedback right now, please try again later. Refer to the Hotfix link under Related Documents at the end of this article to obtain the hotfix needed to resolve the issue. have a peek here Cannot insert duplicate key in object 'dbo.CatResourceNameNode'.

Open a command prompt on the media server 3. Backup Exec Catalog Cleanup Originally received: Sunday, January 28, 2007 9:00:14 AM 4 - ODBC access error. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

ISSUE: This error usually occurs after an upgrade.

The options for this are in the left pane at the bottom. 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. Join Now For immediate help use Live now! Backup Exec Catalog Folder Is Growing Too Large Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored procedure ‘UpdateCatMediaInfo'.

Sometimes your flash drive may have issues carrying files so this will completely restore it to manufacturing settings. If you don't use an SQL server to store the BE catalogs, Reinstall BE without that option. 0 Message Active 5 days ago Author Comment by:redmanjb2007-01-26 Thank you very much Login By creating an account, you're agreeing to our Terms of Use and our Privacy Policy © Copyright 2006-2016 Spiceworks Inc. Check This Out Covered by US Patent.

Thank You! Join & Ask a Question Need Help in Real-Time? All rights reserved. By creating an account, you're agreeing to our Terms of Use and our Privacy Policy Not a member?

Possible lost connection to database or unsuccessful access to catalog index in the database." Want to Advertise Here? I will do a long erase today on the tape that our weekly backup job will be performing on tonight. Event ID 34338 and 34326 reported on CAS server. Thank You!

Join the IT Network or Login. 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.