Home > Backup Exec > Backup Exec 2010 Odbc Access Error

Backup Exec 2010 Odbc Access Error

Contents

They really seemed to have pick up their game in 2014 though. 4 Thai Pepper OP britv8 Sep 29, 2014 at 10:33 UTC I would suggest hanging out I should be very surprised when things fail ... I can count on one hand how many failures we have had in the last year. No Yes How can we make this article more helpful? Source

From application event log: Access to catalog index (Catalog index database) failed. My previous home was wired with Cat5E in almost every room. Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored procedure 'UpdateCatMediaInfoForDriveLetterChanged'. VOX : Backup and Recovery : Backup Exec : "ODBC access error.

Odbc Access Error Backup Exec 2014

Want to Advertise Here? There are many alternatives that are just as good or even better. 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 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.

But, we had a working Unitrends solution going forward and less headaches from BE. Still thinking about it but I found Veeam unbeatable for my vmware backups and a very nice backup tool called backupassist.com for files and folders on Win Servers 7 Was the orginal Backup Exec 2010 R3 media available in the same path as used during the original install at the time that you ran LiveUpdate? 0 Kudos Reply Now it Backup Exec 15 Catalog Error Odbc Access Error I have been working as an IT Consultant through various contracting consultancy organizations for the past two and a half years, but lately things have been a little off.

I'm looking for a new home Wi-Fi router — any advice? I waste WAY too much time in Backup Exec.  I should be checking job successes every morning, not going into the server room wondering what error I will be resolving for This morning I already downloaded the latest version of my software. Possible lost connection to database or unsuccessful access to catalog index in the database." + Hotfix 164220 error atos Level 4 ‎09-19-2011 12:49 AM Options Mark as New Bookmark Subscribe Subscribe

This product had such a great reputation and all that withered away with Symantec's poor response to support requests. V-280-2003 We been receiving the following errors from all Windows, Linux and Mac servers. 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. View solution in original post 0 Kudos Reply 5 Replies have you read the release Colin_Weaver Level 6 Employee Accredited Certified ‎09-19-2011 12:53 AM Options Mark as New Bookmark Subscribe Subscribe

  • Error in Event Log: Backup Exec Alert: Catalog Error (Server: "SERVERNAME") ODBC access error.
  • http://support.veritas.com/docs/303035 Catalog events are generated when catalogs are upgraded from Backup Exec 9.x to 11.x http://support.veritas.com/docs/288076 Inventory, export or other maintenance operations take an extended time to complete and
  • If yes, then refer to the following article and please open a case with us for a possible workaround:http://www.symantec.com/docs/TECH215936 0 Kudos Reply Hi Saini Thank you for JackEmu Level 2 Partner
  • If it is BE2012 SP4 then is your Backup Exec Database located on a Remote SQL server?
  • This by default is SQL Express but could be a full version of SQL.
  • Thanks for the assistance.
  • 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 15 Odbc Access Error

You may also refer to the English Version of this knowledge base article for up-to-date information. Create/Manage Case QUESTIONS? Odbc Access Error Backup Exec 2014 Labels: 2010 Backup and Recovery Backup Exec 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! Catrebuildindex -r Create/Manage Case QUESTIONS?

Was the orginal Backup Exec 2010 R3 media available in the same path as used during the original install at the time that you ran LiveUpdate? this contact form Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? All rights reserved. In short, I am impressed with the quality and functionality of the new BE. -Steven E.  2 Chipotle OP The Spruce Bruce Sep 29, 2014 at 9:32 UTC Event Id 34326 Backup Exec

Further the clear error messages we get out of the appliance isn't some cryptic code with a dead link to a website like BE always was. It is possible that updates have been made to the original version after this document was translated and published. Successfull updates: 159961 159965 160008 161270 161390 162830 Failed Update: 164220 Does anyone have a cause and/or a solution for the ODBC access error message? (and does the http://gatoisland.com/backup-exec/backup-exec-2010-r3-sp1-odbc-access-error.php And I'm not willing to risk my reputation for recommending flawed products to my customers anymore so about a dozen of them will move to Veeam when maintenace is over.

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: Or do you have to use other software for physical servers ?Veeam only works with virtual servers, not physical ones. 3 Pimiento OP Saul2641 Sep 29, 2014 at AND CatMedia.PartitionID = ?

cat_RecordSet::ExecuteBulkInsert()    e:\nicobar\5204r\becat\segodbc\seg_odbc.cpp(3113)    sp_sproc_columns CatImageInfoProc   Source:  Backup Exec CatErrorHandler ServerEvent ID: 34327Error :  Update to catalog index (Catalog index database) failedReason:   D:\Catalogs\SERVER-NAME\{3E4F622C-8411-47A3-9EDC-449192907CED}_8.xml PerformBulkInsert()    e:\nicobar\5204r\becat\catindex\dll\..\catdbupdatethread.cpp(447)  Solution A hotfix is now available for

power outages). Sysprep is a utility developed by Microsoft to facilitate the ma… Storage Software How to install and configure Carbonite Server Backup Article by: Carbonite A quick step-by-step overview of installing and 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. No Yes Did this article save you the trouble of contacting technical support?

Corrupt catalogs in the Catalogs folder. My new house... I'm really tired.Hey Robert 9332,       I hear you.  I am sitting right next to an outstanding Partner support team that I would like to get you hooked up Check This Out Did a 2012 install at the secondary site and did not have any real issues with it at all (when others were saying the sky was falling, but that was because

Networking I've moved recently. The only maintenance free backup is the "lazy" backup. No Yes Did this article save you the trouble of contacting technical support? 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.

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 Possible lost connection to database or unsuccessful access to catalog index in the database. 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. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

Join Now For immediate help use Live now! If Symantec support answers, I cannot afford to update, restart, test, change settings, restart, test the production servers several times during working hours and I'm also not willing to spend 3 Copy the old Catalogs to C:\Program Files\Symantec\Backup Exec Now go to the command prompt and perform the following steps Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : HELP!!!

And meanwhile it's way quicker to setup a new backup server than to go through all the stuff with your support crew. Thank You! ODBC access error. 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.

Cleaning it not fixing it? Before we upgraded from 2012 we would occasionally get a failure but not very often.  Also probably one of the reasons I've stuck with BE is because I have never had Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Every time Backup Exec (BE) services start, the following Errors are observed in the

© Copyright 2017 gatoisland.com. All rights reserved.