Home > Backup Exec > Backup Exec Odbc Access Error Catalog Error

Backup Exec Odbc Access Error Catalog Error


For more information, click the following link:http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml We have tried: 1. Microsoft to end Windows 7 PC sales, Firefox tackles weak encryption Spiceworks Originals A daily dose of today's top tech news, in brief. © Copyright 2006-2016 Spiceworks Inc. For more details on how to change location of catalogs refer to the link below: http://support.veritas.com/docs/286689 Resolution 3 Ensure the value of the following registry keys are as mentioned below.(Depending on The alerts appear when the Backup Exec Services Start and during a backup or catalog job. have a peek here

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. What is when I have installed 12.5 over my existing 12.5 installation ? 0 Message Active 1 day ago Author Comment by:Eprs_Admin2009-10-21 Can I do this or do I destroy If you're lucky, backups run fine for a while then. Backup Exec - How does this actually work?   1 2 Next ► 37 Replies Datil OP Mark McKinlay Sep 29, 2014 at 9:18 UTC I use BE

Odbc Access Error Backup Exec 2014

Article:000040371 Publish: Article URL:http://www.veritas.com/docs/000040371 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 Email Address (Optional) Your feedback has been submitted successfully! Can you help me out ? ODBC access error.

  1. 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.
  2. Open a command prompt on the media server 3.
  3. You may also refer to the English Version of this knowledge base article for up-to-date information.
  4. Help Desk » Inventory » Monitor » Community » Bengts Blogg Varfr krngla till det?
  5. 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
  6. No Yes Did this article save you the trouble of contacting technical support?
  7. 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.
  8. If you have specific issues, I can try and help though. 1 Jalapeno OP Joe4273 Sep 29, 2014 at 4:45 UTC I HATE HATE HATE HATE HATE BUE!!!!!!!!
  9. Possible lost connection to database or unsuccessful access to catalog index in the database.
  10. You'll need to connect to the media server with the tool first. 0 Message Author Comment by:Operator102008-01-10 Thanks AJ.

A new Catalogs folder will be created.At this point no catalogs are present as this is a new, blank Catalogs folder.It will be necessary to run a Catalog job on each 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. Possible lost connection to database or unsuccessful access to catalog index in the database." Want to Advertise Here? Event Id 34326 Backup Exec Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

Best winds, Robert 3 Chipotle OP Matt (Symantec) Sep 29, 2014 at 3:34 UTC Brand Representative for Symantec I certainly understand your frustration, Robert.  But having been back Odbc Access Error Backup Exec 2012 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. I stopped using is after having one of the most dreadful and difficult years utilizing BE2012. I ran a Long Erase recently and I am running another backup job right now, but I am not too optimistic.Any help would be appreciated.

But if you like error messages, here's some of last nights errors (all happened without _any_ change to the environments): Incremental Exchange 2013: failed - E000035e (BE agent not used for Catrebuildindex -r Multiple alerts and notifications regarding the catalogs are seen in the Windows Event Viewer and the Backup Exec Alerts tab. The grass is greener on the other side when you get there. And there again, it's quicker to just disable it, restore the whole server-vm and pick out what you need instead of trying to solve (or workaround) the problem just to get

Odbc Access Error Backup Exec 2012

SUBSCRIBE Suggested Solutions Title # Comments Views Activity Corrupted file system 10 56 75d Windows Server 2012: Building a Two-Node Failover Cluster with High availability and Performance 1 43 66d Hyper-v 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. Odbc Access Error Backup Exec 2014 Solved how to i resolve this error "ODBC access error. Odbc Access Error Backup Exec 2010 Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We

On average it almost takes me half a day up to a day's work PER WEEK to get the backup $*£%#@ like it should. http://waspsoft.com/backup-exec/backup-exec-alert-catalog-error-odbc-access-error.html I used it for years at various jobs since long before Symantec bought it, and have always hated it. Thank You! Thanks, Matt 2 Sonora OP Robert9332 Sep 29, 2014 at 4:08 UTC Hi Matt, "half a chance" has been given for several times when Symantec told "this will "backup Exec 15" Odbc Access Error

I'm sick of this erratical childish behaviour of my backup system !!! Resolution 2 Change the location of Catalogs folder to another volume using Beutility. Featured Post Free Trending Threat Insights Every Day Promoted by Recorded Future Enhance your security with threat intelligence from the web. http://waspsoft.com/backup-exec/backup-exec-2010-catalog-error-odbc-access-error.html 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:

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. V-280-2003 Restart all of the Backup Exec Services on the media server. The… Storage Software Disaster Recovery Windows Server 2008 Starting and Using File History on Windows 8 Video by: Thomas The viewer will learn how to start File History, a MACINTOSH like

Corrupt catalogs in the Catalogs folder.

We have various BE 2010, BE 2012 and now we upgraded to BE 2014 Enterprise server and I would say without any doubt BE 2014 is the most reliable version I Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Solution A 1) Download and install The Microsoft SQL 2005 Server Native Client and SQL 2005 command line query utility "sqlcmd" on the media server. Backup Exec 15 Catalog Error Odbc Access Error CONTINUE READING Suggested Solutions Title # Comments Views Activity Get ADP file from ADE file 3 7 116d How to backup Master server with Media server 4 51 89d 2016-latest technologies

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. 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. From application event log: Access to catalog index (Catalog index database) failed. http://waspsoft.com/backup-exec/backup-exec-2010-odbc-access-error-catalog-error.html There may be issues with a D2D2T backup scheme that I am not aware of.

After a catalog job is performed the restore selections may show partial or no restore selections. (FIGURE A) Solution: NOTE: There are three possible solutions to resolve this issue. 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 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 Possible lost connection to database or unsuccessful access catalog index database Solution SYMPTOMS: 1.

It is most common among "multi-step upgrades." For example, upgrading from 9.1 > 11d > 12.5 OR 10d > 12.0 > 12.5.