event id 33152 adam mover error Carr Colorado

Address 8806 Indian Village Dr, Wellington, CO 80549
Phone (970) 658-8159
Website Link

event id 33152 adam mover error Carr, Colorado

Any suggestions?? Event ID: 33152 Source: Backup Exec Source: Backup Exec Type: Error Description:Adamm Database Error: Error = Server = "" Active Node = "" Instance = "BkupExec" Database Not a member? Labels: Backing Up Backup and Recovery Backup Exec Monitoring Troubleshooting Windows Server (2003-2008) 1 Kudo Reply 7 Replies Hi, Check the 2 TNs below CraigV Moderator Partner Trusted Advisor Accredited

Check if you have updated the SCSI firmware. VOX : Backup and Recovery : Backup Exec : Backup Exec 10d - Event ID 33152 - Adamm Mover Err... Don't know if this is useful for anyone...? - Capturing to C:\Program Files\VERITAS\Backup Exec\NT\logs\SGMon.logbeserver: 12/18/06 12:20:27 20 Auto Clear Alerts Querybeserver: 12/18/06 12:20:40 -1 SQLLog(1930):AgeSession m_threadMap: SessionThreadID:350, CurrentThreadID:1100beserver: 12/18/06 12:21:28 20 I have the exact same problem with backup exec 10d.

Don’t miss out on this exclusive content! Error = ERROR_IO_DEVICE Drive = "CERTANCE 0001" {B8B580A5-280E-4954-BE43-F89B217F68A9} Media = "Tape 20" {89E1C0C3-3441-463A-90B7-1D3038BACBA5} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(1), ScsiPass(1) EventID 57665 Storage device "CERTANCE 0001" reported Replacing the tape drive stopped this error from reappearing. 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

And so does the event 11.Ive run the SGMON utility and pasted the outputted log below for an Inventory run for about 3 minutes before I cancelled it, as it would Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Backup Exec 10d - Event ID 33152 - Then stop all the backup exec svcs. Event Type:ErrorEvent Source:Backup ExecEvent Categoryevices Event ID:33152Date:5/24/2005Time:12:25:13 AMUser:N/AComputer: Description:Adamm Mover Error: Write Not Ready Failure!Error = ERROR_NO_MEDIA_IN_DRIVEDrive = "DELL 1" {E87560BC-3B50-4CD8-9167-2E13FD24EE27}Media = "DLT000017" {56F31B80-45E9-4C74-BF9A-DBEE1E8F8CD4}Read Mode: SingleBlock(0), ScsiPass(0)Write Mode: SingleBlock(1), ScsiPass(1) Event

Veritas / IBM / anyone who has had this problem before will to tell you the same thing. :) 0 Message Author Comment by:solutions-expert2006-06-12 Apologies for the delay in closing Error = ERROR_NOT_READY Drive = "D51 Drive" {2FF4F000-7C59-4E09-A09F-FBA9A0C9E9F9} Media = "" {00000000-0000-0000-0000-000000000000} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(1), ScsiPass(1) ---------- Message 3 Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. In addition, the problem seems to have tapered off as of mid-December.

The tape drive has its firmware up-to-date ( updated it about 2months ago ). If the problem persists, try a different tape. I'm seeing the exact same types of errors as the two of you. By submitting you agree to receive email from TechTarget and its partners.

Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Event Log: Adamm Mover Error: Read Retry! Unlock and inventory jobs run OK. This error popped up for the first time about 3 to 4 weeks ago ( I believe it was about 1 week after the power outage had occured ). However, I found the following three errors in Windows Event Viewer on the backup server, in the Application log: Error #1) Date: 8/1/2009 Time: 1:16:58PM Type: Warning User: N/A Computer: BackupServer

Ensure that the Removable Storage Service is stopped, it should be deactivated.-----------------------------------------------------------------------Additional Information:If you are not at the latest build of Backup Exec 9.1 for Windows Serversrevision 4691, we would suggest Computer Hope Forum Main pageFree helpTipsDictionaryForumLinksContact Welcome, Guest. read more... Privacy Reply Processing your reply...

Ensure that the Removable Storage Service is stopped, it should be deactivated.How to Troubleshoot Event 9 and Event 11 Error Messageshttp://support.microsoft.com/default.aspx?scid=kb;en-us;154690Hopefully this helps you resolve the issue. Our current configuration is to run a full backup of our main disk array/fileserver on Friday, at 11:00PM. Clean the tape drive, and then try the job again. After scouring the veritas knowledgebase I conducted a long erase on all tapes previously used.

Error = ERROR_NOT_READY Drive = "IBM 1" According to a support forum, this message was recorded on a system using an IBM tape drive. There were signs of internal damage (and this was on freshly purchased tapes.) Quantum tried to tell me to go read their tape handling documentation, but I literally take these tapes Mike_Wild Level 3 ‎08-27-2007 01:19 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Just to add to thefun... nReval:0x0.pvlsvr: 12/18/06 12:25:42 AdammSession::MediaUtilityThreadProc( ADAMM_SESSION_EXECUTE_INVENTORY_READ_MEDIA_HEADER ) Session = {EB70FEC7-6651-4D2A-924C-15818F651550} Job = {5F1F648D-3BF8-4026-A585-CBE60061F8A2}, "Inventory Drive 00002" Drive = {F29FDA30-E512-4FD3-893F-EA7575C9443E}, "HP 1" Slot = 0000 Side = 0000beserver: 12/18/06 12:25:48 -1 End Inventorybeserver:

Running the inventory job was successful also. How do I get the hardware to message it needs cleaning. Error = ERROR_NOT_READY Drive = "Drive 1" {A2B872F4-4681-4D45-B6BB-4FDE132C962E} Media = "" {00000000-0000-0000-0000-000000000000} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(1), ScsiPass(1) Error #2) Date: 8/1/2009 Time: 1:17:13PM Type: Warning User: N/A Computer: Submit your e-mail address below.

Register Hereor login if you are already a member E-mail User Name Password Forgot Password? What exactly is behind this? I'm switching to Bacula. and here is the problem folks....As soon as I do anything with the Device, i.e run an Inventory, Eject, Backup etc...

By comparison, I have had successfull differential and full backups run (even one last night) and this error does not occur. I first noticed a problem when I came in on Saturday and found the following error after the full backup job had 'finished': Job ended: Saturday, August 01, 2009 at 12:28:00 x 3 John Rigali The drive in my scenario was a Seagate STT320000A IDE Travan drive. Which, didn't resolve the problem.

Following Follow Symantec Backup Exec 11D Good morning, I have just taken over the position of backup operator in my department, so please forgive any seemingly obvious questions. Errors Click an error below to locate it in the job log V-79-57344-33039 - Error - Mount failed. For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml Please review. Final error category: Backup Media Errors For additional information regarding this error refer to link V-79-57344-34028 Backup- \ LRDCVOLStorage device "Drive 1" reported an error on a request to write data

If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case. When I arrived at work Monday morning, BackupExec told me that the cleaning job ran normally and completed. I could go and try the things here: http://support.microsoft.com/kb/154690/en-us, but I'm not completely convinced that that is the problem. Don't reboot yet. 3) Get into the Removable Storage manager and remove the library and drives. 4) Reboot 5) The reboot will cause the media changer and drives to be detected

shweta_rege Level 6 ‎12-28-2006 03:47 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello,Please check,whether the device that you The combined actions have resolved all issues. Error = ERROR_IO_DEVICE Drive = "HP 2" It turned out that one of the SCSI terminators on the HP LTO Ultrium-3 tape drive was damaged. See EV100262 (How to read the ADAMM.LOG file, and what various errors mean within the log).

Thanks. Covered by US Patent.