Home > Backup Exec > Backup Exec 2010 Odbc Error

Backup Exec 2010 Odbc Error

Contents

George 0 Question by:Eprs_Admin Facebook Twitter LinkedIn Google LVL 23 Active 3 days ago Best Solution byIamthecreator You can refer to the following for possible reasons and the respective resolution. Possible lost connection to database or unsuccessful access to catalog index in the database. 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. This product had such a great reputation and all that withered away with Symantec's poor response to support requests. Source

If the current Backup Exec version is 12.5, run the osql scripts up to the 12_0 version and then run the "catrebuildindex -r". Get 1:1 Help Now Advertise Here Enjoyed your answer? You'll be able to use this tool to add the backup exec service account to have permissions on the database. Veritas does not guarantee the accuracy regarding the completeness of the translation.

Backup Exec Odbc Access Error

The options for this are in the left pane at the bottom. How much work is it for you to maintain ? You will have to repeat this step again until you get a message that states all available updates have been installed. 3.Push install the Remote Agent for Windows Servers to all ODBC access error.

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. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem After restarting the Backup Exec services lots of "ODBC access error. I'm really tired. 2 Cayenne OP Jonathan2738 Sep 29, 2014 at 4:25 UTC We've been using BE2012 going on 2 years now, and really the only issue we Backup Exec 2010 Download Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

I stopped using is after having one of the most dreadful and difficult years utilizing BE2012. Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL 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. I'm going to hear for a quote on the newest 2014 version ...

And their tech support isn't as helpful as they should be. Backup Exec 2010 End Of Life No Yes How can we make this article more helpful? 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. Join Now rant I am getting sick of our backup solution including BE2012.

Odbc Access Error Backup Exec 2014

I'm looking for a new home Wi-Fi router — any advice? You may also refer to the English Version of this knowledge base article for up-to-date information. Backup Exec Odbc Access Error Possible lost connection to database or unsuccessful access to catalog index in the database. Odbc Access Error Backup Exec 2012 Aaaaaaaaaaahhhhhhhhhhh ! /rant Seriously , I'm getting errors , jobs keeping running , part of a newly created job not appearing in the jobs list (so I can't even start it)

Solved ODBC access error. this contact form Veritas does not guarantee the accuracy regarding the completeness of the translation. If you're lucky, backups run fine for a while then. Every week it's a battle to get everything backed-up. Backup Exec 2010 Error 1603

Featured Post Course: JavaScript Coding - Massive 12-Part Bundle Promoted by Experts Exchange Regardless of your programming skill level, you'll go from basics to advanced concepts in a vast array of And meanwhile it's way quicker to setup a new backup server than to go through all the stuff with your support crew. And the error messages were easy to understand, no problem to fix the error on my own. http://gatoisland.com/backup-exec/backup-exec-2010-r3-sp1-odbc-access-error.php 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:

Haven't had a job failure in  the past 6 months. Backup Exec 2010 Administrator's Guide I am a long time user of Backup Exec, since version 7. 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

When you think of replication, your mind drifts to solutions that replicate from one disk frame to another using block level technolo… Storage Software Data Deduplication for VM Backups Article by:

  • Corrupt catalogs in the Catalogs folder.
  • But, we had a working Unitrends solution going forward and less headaches from BE.
  • No Yes How can we make this article more helpful?
  • To check all updates that have already been installed from the Backup Exec interface go to Help ->About   ->Installed updates. 2.If hotfix 327039 is not on the list of installed updates
  • Send you a PM.

I'm hoping to switch to unitrends because I am so sick and tired of this. 3 Habanero OP toby wells Sep 29, 2014 at 1:25 UTC GarfieldMaximus wrote:toby If you're lucky, backups run fine for a while then. 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. Backup Exec 2010 R3 Sp2 There are many alternatives that are just as good or even better.

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 Backup Exec Database (BEDD) is hosted on an invalid SQL Instance.  Solution: First make sure the SQL instance being used for the BEDB is a valid Instance. Email Address (Optional) Your feedback has been submitted successfully! Check This Out By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks.

Tags: Unitrends4,299 FollowersFollow 1 Jalapeno OP CCMIS Sep 29, 2014 at 7:14 UTC Backups always require quite a bit of time regardless of the solution that you use. I've used 2010 and 2014, and all it does is take the bugs from 2010 and shifts them over a foot to the left and turns them 90 degrees. 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. I'm sick of this erratical childish behaviour of my backup system !!!

Sorry, we couldn't post your feedback right now, please try again later. Thanks Operator10 0 Question by:Operator10 Facebook Twitter LinkedIn Google LVL 6 Best Solution byAJermo It sounds like the Backup Exec service account has been change and doesn't have access to the I simply don't know where to start, which customers servers shall I abuse and spend my night with? The conflict occurred in database "BEDB", table "dbo.CatResource", column 'ResourceID'.

Privacy Policy Site Map Support Terms of Use Home Backup Exec ... You may get a better answer to your question by starting a new discussion. As a Symantec partner I have to tell my customers to renew their licenses because BE is a great product and Symantec will fix all the issues. Want to Advertise Here?

a problematic child by GarfieldMaximus on Sep 29, 2014 at 9:13 UTC | Data Backup 0Spice Down Next: Recover from tape drive using ToDo Backup IN THIS DISCUSSION Novastor Veeam Microsoft .Net 3.5 is required. 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. We have a single BE 12 server.

If you want to post the stupid error messages, I may be able to helpThanks for the links , I'll read up on that (second one)   EDIT : That's the I simply don't know where to start, which customers servers shall I abuse and spend my night with? I have BE2012 and 2014 running on different networks, both plain virtual, plain physical and mixed, updated BE-servers and fresh installs - no difference. 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

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 I can count on one hand how many failures we have had in the last year. Article:000041211 Publish: Article URL:http://www.veritas.com/docs/000041211 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 Possible lost connection to database or unsuccessful access to catalog index in the database" on restarting Backup Exec Services.

© Copyright 2017 gatoisland.com. All rights reserved.