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

Backup Exec 2010 Odbc Access Error Catalog Error

Contents

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 I'm DONE with Backup Exec Anyone still using Backup Exec? I can count on one hand how many failures we have had in the last year. 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. Source

ODBC access error. Refer to the Hotfix link under Related Articles to obtain the hotfix needed to resolve the issue. I would take the time to evaluate other solutions before giving Symantec a 2nd chance with BE2014. 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.

Odbc Access Error Backup Exec 2014

How can I repair it ? 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. 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 It is possible that updates have been made to the original version after this document was translated and published.

  • Suggested Solutions Title # Comments Views Activity Could you point the better approach on PostgreSQL backup/ restore ? 4 35 113d PIng command and its use 9 56 37d What is
  • Differential backup… Storage Software Windows OS Disaster Recovery Data Deduplication for VM Backups Article by: Anna VM backup deduplication is a method of reducing the amount of storage space needed to
  • The installed IDR feature was installed and I do not need it.
  • We been receiving the following errors from all Windows, Linux and Mac servers.

If you are getting that many failures then something else might really be the problem. And the error messages were easy to understand, no problem to fix the error on my own. Article by: Shakshi Microservice architecture adoption brings many advantages, but can add intricacy. Event Id 34326 Backup Exec 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.

No Yes Did this article save you the trouble of contacting technical support? Networking I've moved recently. 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 Then, yes, it needs to be repaired.

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!!!!!!!! V-280-2003 Possible lost connection to database or unsuccessful access to catalog index in the database." Want to Advertise Here? Possible lost connection to database or unsuccessful access to catalog index in the database" is received in the Application Log and also similar alerts are generated in Alerts tab in Backup Please contact your Symantec Sales representative or the Symantec Partner for upgrade information including upgrade eligibility to the release containing the resolution for this issue.

Backup Exec 15 Odbc Access Error

Reason: Data type mismatch cat_RecordSet::SetField() r:\catalina\1364r\becat\segodbc\seg_odbc.cpp(3613) sp_sproc_columns CatImageInfoProc Environment The Backup Exec Database (BEDB) is located on a remote SQL Server or is not in the default named SQL (BKUPEXEC) Instance. Possible lost connection to database or unsuccessful access to catalog index in the database" when the Backup Exec Database (BEDB) is located on a remote SQL Server or not in the Odbc Access Error Backup Exec 2014 Email Address (Optional) Your feedback has been submitted successfully! Odbc Access Error Backup Exec 2010 You may also refer to the English Version of this knowledge base article for up-to-date information.

Multiple alerts and notifications regarding the catalogs are seen in the Windows Event Viewer and the Backup Exec Alerts tab. this contact form 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 I can count on one hand how many failures we have had in the last year. Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : ODBC access error / BackupExec Catalog not accessi... Catrebuildindex -r

Error Event Viewer Application Log: Event Type: Error Event Source: Backup Exec CatErrorHandler Server Event Category: None Event ID: 34326 Description: Access to catalog index (Catalog index database) failed. The alerts appear when the Backup Exec Services Start and during a backup or catalog job. Snap! http://gatoisland.com/backup-exec/backup-exec-2010-r3-sp1-odbc-access-error.php 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

Now I can monitor the backup of ~50 servers in one location which makes everything much easier. Backup Exec 15 Catalog Error Odbc Access Error Possible lost connection to database or unsuccessful access to catalog index in the database. Note: In some cases, it may be necessary to clear the alerts tab and reboot the server after performing the steps above.

Lenora 0 Chipotle OP qwerty_80486 Sep 29, 2014 at 6:17 UTC No matter what you choose backups are a constant time waster.

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 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 Refer to the Hotfix link under Related Documents in this article to obtain the hotfix needed to resolve the issue. Backup Exec 15 Rev 1180 Feature Pack 1 (TECH228725).  This issue is resolved The conflict occurred in database "BEDB", table "dbo.CatResource", column 'ResourceID'.

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 Change the directory to the Backup Exec installation directory: \Program Files\Symantec\Backup Exec 4. To answer the question: no, database is located on be server with default naming. Check This Out at first i thought it was a licensing issue.

Great for personal to-do lists, project milestones, team priorities and launch plans. - Combine task lists, docs, spreadsheets, and chat in one - View and edit from mobile/offline - Cut down 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: Veeam is a great alternative. Veritas does not guarantee the accuracy regarding the completeness of the translation.

Feature Pack for Microsoft SQL Server 2005 http://www.microsoft.com/downloads/details.aspx?FamilyID=50B97994-8453-4998-8226-FA42EC403D17&displaylang=en sqlncli.msi (Microsoft SQL Server Native Client) SQLServer2005_SQLCMD.msi (Microsoft SQL Server 2005 Command Line Query Utility SQLcmd) 2) Stop the Backup Exec services using For a SSO Primary server: SSOState=1 Catalog Remote Server Name = (Does not exist) III. Join our community for more solutions or to ask questions. Join the community of 500,000 technology professionals and ask your questions.

You may also refer to the English Version of this knowledge base article for up-to-date information. No Yes Did this article save you the trouble of contacting technical support? If you want to post the stupid error messages, I may be able to help 3 Tabasco OP GarfieldMaximus Sep 29, 2014 at 12:14 UTC britv8 wrote: I 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

Look for beutil.exe in the backup exec bin directory. Connect with top rated Experts 9 Experts available now in Live! 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 Its been at least 10 years since I was near Oracle so I will defer to the database experts here! Does Veeam also do regular backups ?

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 Send you a PM. Exchange 2007 - failed - E00095B3 (virtual HD-images could not be loaded - suddenly?) The GRT-issues are coming and going just like good friends. The few weeks per year that all backups succeed it's a great relief.

Backup Exec Alert: Catalog Error ODBC access error.

© Copyright 2017 gatoisland.com. All rights reserved.