Home > Event Id > Event Id 34327

Event Id 34327

Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem After the Backup Exec services start multiple Backup Exec Catalog and ODBC Event ID errors It also doesn't have any older catalog information for my media, but c'est la vie, apparently. Solved! 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 Source

Thinking about it now, perhaps if I ran a Catalog Media job on all the media used between 4/12 and 4/16 --the period when the original ODBC errors were causing bad Reason: Unrecognized database format 'C:\Program Files\VERITAS\Backup Exec\NT\Catalogs\BeTopCat.idx'. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem ODBC Access errors. I only find those error message in the Windows Event Log when the BE services start (either upon reboot, or simple restart of services [manually or using the BE Utility]). 0

Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended But a brand new Catalog folder does not have those errors (I tested this). read more...

TheEventId.Net for Splunk Add-onassumes thatSplunkis collecting information from Windows servers and workstation via the Splunk Universal Forwarder. Veritas does not guarantee the accuracy regarding the completeness of the translation. I'm not sure there would be a good reason to keep it around. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking

But a brand new Catalog folder does not have those errors (I tested this). Thank You! It is possible that updates have been made to the original version after this document was translated and published. It also doesn't have any older catalog information for my media, but c'est la vie, apparently.

Event ID: 34327 Source: Backup Exec Catalog Type: Error Description:Update to catalog index (C:\Program Files\VERITAS\Backup Exec\NT\Catalogs\BeTopCat.idx) failed. Stats Reported 6 years ago 1 Comment 1,407 Views Other sources for 34327 Backup Exec Catalog Server Others from Backup Exec CatErrorHandler Server 34326 IT's easier with help Join millions of I'll review space issues vis-a-vis the catalog size. Possible lost connection to database or unsuccessful access to catalog index in the database.

A bit of a mess to clean up.) Doing one-off full backups of previously failed jobs did fix some of their problems, but this last weekend's suite of full backups resulted Stop all BE services 2. cat_RecordSet::ExecuteBulkInsert() e:\nicobar\5204r\becat\segodbc\seg_odbc.cpp(3113) sp_sproc_columns CatInsertSetCopyVirtualSet Subsequent instances of Event ID 34327 describe themselves thusly: Update to catalog index (Catalog index database) failed. Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot insert the value NULL into column 'ImageID', table 'BEDB.dbo.CatFragment'; column does not allow nulls.

Event ID: 34327 Source: Backup Exec Catalog Type: Error Description:Update to catalog index (C:\Program Files\VERITAS\Backup Exec\NT\Catalogs\BeTopCat.idx) failed. http://0pacity.com/event-id/event-viewer-event-id-list.html Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? Refer to the Hotfix link under Related Documents at the end of this article to obtain the hotfix needed to resolve the 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

read more... I think the best for you would be to contact Symantec Technical support having the debug files of the media server so they can do a further investigation, with the event Do I need to re-catalog all the Disk backup media? http://0pacity.com/event-id/frs-event-id-13508-without-frs-event-id-13509.html Somehow, that hotfix introduced errors into the Catalog folder.

By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. Reason: Unrecognized database format 'C:\Program Files\VERITAS\Backup Exec\NT\Catalogs\BeTopCat.idx'. Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Event ID 34327 - multiple ODBC Errors, Catalog iss...

Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Event ID 34327 - multiple ODBC Errors, Catalog

My main questions are: Is there a way to clean up these ODBC/Catalog errors? This is despite the media's overwrite protection period is not over and the media is not overwritten. 0 Kudos Reply Got a similar issue once, King_Julien Level 5 ‎04-24-2012 06:07 PM Keeping an eye on these servers is a tedious, time-consuming process. 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

Without investigating the nPc Level 4 ‎04-26-2012 11:38 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Without investigating the Since the ODBC errors do not appear to be causing any problems with the backup jobs, there is apparently little to worry about. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? http://0pacity.com/event-id/event-id-40961-event-source-vss.html Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Vision 2016 Vision 2016 Blog