Error Encountered When Attempting To Execute Media Label Library Be
Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample report Custom views/filters Servers list, organized in groups Integration with EventID.Net Consolidated view for all logs Free for subscribers Event ID: 152 Source: Removable Storage Service Source: Removable Storage Service Type: Error Description:Error encountered when attempting to execute Media Label Library "
drive [ ] information with the replaced drive [ ] because the current drive type [ ] is different from the new drive type [ ] If you have replaced the drives of IBM ULTRIUM library and performed drive detection from Library and Drive configuration, then the drive detection process might fail with the following error message. Cannot update the drive [IBM ULTRIUM-TD4_1(IBM ULTRIUM-TD4, xxx)] information with the replaced drive [Drive (IBM ULTRIUM-TD5, xxx)] because the current drive type http://www.eventid.net/display-eventid-152-source-Removable%20Storage%20Service-eventno-3913-phase-1.htm [ULTRIUM-V4] is different from the new drive type [ULTRIUM-V5]. Symptom This error message appears and drive detection process would fail if IBM ULTRIUM library is attached to a MediaAgent running on Windows Server 2003. Resolution To resolve this issue: Deconfigure and delete the drives. See Deconfigure Drives for instructions. Install the Microsoft Hotfix on both MediaAgent. Refer to http://documentation.commvault.com/commvault/v10/article?p=features/library_drive_config/library_drive_configuration_troubleshoot.htm Microsoft KB article 9716500. Perform device detection process. See to Device Detection for instructions. Unable to Detect Non-IBM Libraries on AIX Symptom By default, AIX does not have a driver that attaches to non-IBM libraries. The driver provided by IBM, Atape, attaches only to IBM libraries. Resolution If you have AIX 5.3 (maintenance level 5 and above), AIX 6.1 or AIX 7.1, use the following procedure to detect any non-IBM libraries that are not detected. If you have IBM only libraries connected to the MediaAgent, install the IBM Atape driver on this MediaAgent and proceed to step 9. Arm-changer will be detected as smcX device (where X=1,2,3...). Ensure that no jobs are running in the CommCell Console. Stop the Simpana services on this MediaAgent. Run cfgmgr command to configure devices currently detected by the OS.If the adapter ID is known, use the -l option to limit action to adapter. cfgmgr -v Go to
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas https://vox.veritas.com/t5/NetBackup/Vault-job-failing-with-error-encountered-executing-Media-Manager/td-p/617998 Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you http://www.cerious.com/sp/manual45/tp45man-2737.html quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup error encountered and Recovery : NetBackup : Vault job failing with error encountered executing... VOX : Backup and Recovery : NetBackup : Vault job failing with error encountered executing... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! error encountered when Go to Solution Vault job failing with error encountered executing Media Manager command(303), while everything else is working fine. Sahana Level 2 ‎04-24-2013 09:32 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi All, Vault job on one of our master servers is failing with "error encountered executing Media Manager command(303)". Below is the detailed status: 4/25/2013 3:31:53 AM - requesting resource kynudcms033.NBVAULT.MAXJOBS 4/25/2013 3:31:53 AM - requesting resource kynudcms033.NBU_POLICY.MAXJOBS.Ejection_Notification 4/25/2013 3:31:53 AM - granted resource kynudcms033.NBVAULT.MAXJOBS 4/25/2013 3:31:53 AM - granted resource kynudcms033.NBU_POLICY.MAXJOBS.Ejection_Notification 4/25/2013 3:31:54 AM - estimated 0 kbytes needed 4/25/2013 3:31:54 AM - begin Parent Job 4/25/2013 3:31:54 AM - begin Vault, Start Notify Script 4/25/2013 3:31:54 AM - started process RUNCMD (4724) 4/25/2013 3:31:54 AM - ended process 0 (4724) Status 0 4/25/2013 3:31:54 AM - end Vault, Start Notify Script
program exception occurred in the main ThumbsPlus process. This is most likely the result of a program bug. This type of exception will cause ThumbsPlus to terminate. You will need to restart ThumbsPlus. You can generate (and email to Cerious Software: support@cerious.com) a technical support log, which includes detailed information about this error, by running ThumbsPlus again and pressing Ctrl+Alt+Shift+E. 5001 Out of memory! ThumbsPlus was unable to allocate the amount of memory required to do the function you selected. There are several things you can do to make more memory available: Close (rather than minimize) any applications that you aren't using. Close any ThumbsPlus view windows which are open. You can increase the amount of virtual memory that is available for programs under Windows. Please refer to your Windows documentation or the on-line help for information. If all else fails, you can buy more memory! If the problem seems unrelated to actual memory usage on your machine, please report it to Cerious Software technical support. 5002 Error creating child window! ThumbsPlus failed during initialization or re-initialization to create a necessary window (i.e., the thumbnail view, the folder tree, the toolbar, etc). This is a fatal error. ThumbsPlus will exit. The only known causes are insufficient or corrupted memory. Restart Windows and try again. 5003 Error creating dialog box! ThumbsPlus could not create a dialog box for the selected function. Possible reasons for this error are: The Windows system is hosed and needs to be restarted. Memory or resources are very low, so Windows should be restarted. The executable file: THUMBS.EXE is corrupt and needs to be reinstalled after running SCANDISK. 5004 Error registering window class for toolbar! ThumbsPlus could not create the toolbar. Your system may be low on mem