Home > Backup Exec > Backup Exec Odbc Access Error 34338

Backup Exec Odbc Access Error 34338

Contents

Open a command prompt on the media server 3. In some cases it has been observed that some backup sets are not expired properly. If the above steps do not correct the catalog issue, it may be necessary to start with a fresh catalog database.  This step should only be taken as a last resort Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem After applying Backup Exec 2012 SP2 an ODBC access error Possible lost connection to Source

Blank restore selection list. Sorry, we couldn't post your feedback right now, please try again later. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

Odbc Access Error Backup Exec 2014

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? 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 No Yes How can we make this article more helpful? 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.

  1. You may also refer to the English Version of this knowledge base article for up-to-date information.
  2. So far it looks promising. 0 Kudos Reply Re: BE15 14.2 Catalog Error / ODBC access error jan_villeres Level 4 Partner Accredited Certified ‎12-25-2015 09:40 PM Options Mark as New Bookmark
  3. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem ODBC Access errors.
  4. Start all of the Backup Exec services using servicesmgr.exe 7.
  5. You may also refer to the English Version of this knowledge base article for up-to-date information.
  6. Create/Manage Case QUESTIONS?
  7. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?
  8. Create/Manage Case QUESTIONS?
  9. Regards!

You may also refer to the English Version of this knowledge base article for up-to-date information. Thank You! Email Address (Optional) Your feedback has been submitted successfully! Backup Exec 15 Odbc Access Error Sorry, we couldn't post your feedback right now, please try again later.

Error Message Application Log Errors: Source:  Backup Exec CatErrorHandler ServerEvent ID: 34327Error :  Update to catalog index (Catalog index database) failed.Reason:    D:\Catalogs\SERVER-NAME\{86794C68-8397-4F24-A2EA-404B54FED371}_31.xml PerformBulkInsert()    e:\nicobar\5204r\becat\catindex\dll\..\catdbupdatethread.cpp(447) Source:  Backup ExecEvent ID: 34338Error :  Backup Odbc Access Error Backup Exec 2012 You may also refer to the English Version of this knowledge base article for up-to-date information. Event ID 34338 and 34327 reported on CAS server running Backup Exec 2012 Error Message Following ODBC access errors are occasionally observed on CASO server : Log Name: Application Source: Backup Possible lost connection to database or unsuccessful access to catalog index in the database.              Solution This issue is resolved in Backup Exec 2014 or later

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 Event Id 34326 Backup Exec Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. No Yes Did this article save you the trouble of contacting technical support? Backup Exec 2012 Rev 1798 Service Pack 2 (TECH203155)   Terms of use for this information are found in Legal Notices.

Related Articles Article Languages x Translated Content Please note

Odbc Access Error Backup Exec 2012

Possible lost connection to database or unsuccessful access to catalog index in the database.   Solution A hotfix is now available for this issue in the current version(s) of the product(s) Veritas does not guarantee the accuracy regarding the completeness of the translation. Odbc Access Error Backup Exec 2014 This entry was posted in Uncategorized by consoko. Odbc Access Error Backup Exec 2010 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

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? http://sovidi.com/backup-exec/backup-exec-2010-r3-sp1-odbc-access-error.php Article:000083813 Publish: Article URL:http://www.veritas.com/docs/000083813 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.  This second  is the unique event tied to this Technote issue.  The highlighted text shows the key Access to catalog index (Catalog index database) failed. Backup Exec 2015 Odbc Access Error

Possible lost connection to database or unsuccessful access to catalog index in the database.     Solution A hotfix is now available for this issue in the current version(s) of the Blog at WordPress.com. %d bloggers like this: Thank You! have a peek here For a SSO Secondary server: SSOState=2 Catalog Remote Server Name = (Name of primary server) Share this:TwitterFacebookLike this:Like Loading...

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 Catrebuildindex -r viewing of backup sets stuck in loading... Solution A hotfix is now available for this issue in the current version(s) of the product(s) mentioned in this article.

If the current Backup Exec version is 2010, run the osql scripts up to the 12_5 version and then run the "catrebuildindex -r".

Stop the Backup Exec Services. 2. Possible lost connection to database or unsuccessful access to catalog index in the database. 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 V-280-2003 Thank You!

Email Address (Optional) Your feedback has been submitted successfully! It is possible that updates have been made to the original version after this document was translated and published. No Yes How can we make this article more helpful? http://sovidi.com/backup-exec/backup-exec-2012-odbc-access-error.php If we get the above error when the backup job is running on a specific backup to disk folder , delete the folder.cfg and changer.cfg and run an inventory on the

c. 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. 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". We are experincing the same symptoms (odbc errors:maldives) and more such as: a.

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 Was catrebuildindex -r run when the BE services were stopped ? 0 Kudos Reply Re: BE15 14.2 Catalog Error / ODBC access error leifr Level 2 Partner Accredited Certified ‎12-16-2015 viewing of job histories stuck in loading... 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

No Yes How can we make this article more helpful? Installed FP3 yesterday. No Yes How can we make this article more helpful? Reason: [Microsoft][ODBC Driver Manager] Function sequence error CCatRecordSet::GetRecordCount r:\maldives\1180r\becat\segodbc\seg_odbc.cpp(3629) {CALL CATDLM_New_GetExpirableMedia(?,?,?,?,?,?,?)} Itried to rebuild the catalog index with catrebuildindex -r , but it does not seems to help at

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. No Yes Did this article save you the trouble of contacting technical support? You may also refer to the English Version of this knowledge base article for up-to-date information. For information on how to contact Symantec Sales, please see http://www.symantec.com.Applies ToBackup Exec 2012 SP2 SQL Agent Backups.   Terms of use for this information are found in Legal Notices.