Home > Cannot Write > Cannot Write To Device 1167

Cannot Write To Device 1167

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. The lack of an error for the controller would indicate that only the OS experienced a loss of communication with the tape drive. [6300] [Windows NT SCSI PORT Error] is the So it sounds like for that particular data source you have a combination of compressible and not-so compressible files. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. this contact form

Joe Tuesday, May 27, 2014 2:44 PM Reply | Quote 0 Sign in to vote Mike, Thanks for the information on using the utility you've listed. This is not a "DPM rebuild" per se but a rebuild of the OS on that server. We've got the exact same problem, no hardware problems whatsoever. However the exceptions should be fixed. https://community.hpe.com/t5/Data-Protector-Practitioners/Cannot-write-to-device-Details-unknown/td-p/5939399

Thursday, June 26, 2014 5:02 PM Reply | Quote Moderator 0 Sign in to vote Hi, DPMRA is the process that writes to the tapes, so the "NeedMoreMedia = [1]" should Proposed as answer by Mike JacquetMicrosoft employee, Moderator Monday, November 11, 2013 8:20 PM Monday, November 11, 2013 8:19 PM Reply | Quote Moderator 0 Sign in to vote Mike, Thanks I rebooted a 2nd time and manually ran long-term recovery points to tape of all Protection Group members. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

Joe Tuesday, May 27, 2014 2:47 PM Reply | Quote 0 Sign in to vote Hi Joe, Just a quick update, we're not going to re-install DPM for now, we have Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. I was getting nowhere with HP re: the "breakage" of the DPM Reporting and Recovery tabs. In spiritual matters, Erasmus continues to be pressed harder to take a firm position for or against Luther.

Thanks. I am just glad that it is now working properly!!! :-) Joe Marked as answer by Joe OConnor - Harron Wednesday, June 25, 2014 5:19 PM Unmarked as answer by Joe The last communication I received (yesterday) from 2nd level HP Support was that there are some reports that applying the latest Proliant Support Packs and/or performing a cleaninstall using theHP-provided server https://community.hpe.com/hpeb/attachments/hpeb/itrc-251/95743/1/356430.txt No worries, I found the cause and the reason for tape spanning.

The operation failed because of a protection agent failure. (ID 998 Details: The device is not connected (0x8007048F))" The error code 0X8007048f is returned from Windows and means “ERROR_DEVICE_NOT_CONNECTED” None of You need the symbolic name for the tape drive you loaded media into - look in the DPM console by clicking the tape drive and look at the details for \\.\tape########. I did have to click "No" (numerous times) when the Program Files subfolder was clicked because it contains the Volumes subfolder. This can be beneficial to other community members reading the thread.

We even have a separate HP Smart Array P212 controller just for the tape drive. go to this web-site Over the weekend, I forwarded Mike's comments (and the link to this thread) to the HP and Microsoft teams I am working with on this issue. Thanks brendan Tuesday, May 27, 2014 9:18 AM Reply | Quote 0 Sign in to vote Hi, You can try to reproduce the problem outside of DPM usingsome external utilities. This can be beneficial to other community members reading the thread.

Erasmus exerted a powerful influence not only through his books, but also through the private letters that he wrote to a great number of humanist scholars in all parts of Western weblink MS=1167 [The device is not connected.] [03/31 13:54:18 1774 2 WD 50 51 7] ASWriteToASLogWithJobID: JobID[51] [6300] [Windows NT SCSI PORT Error] The [WRITE] entries indicate the tape drive was in Reload to refresh your session. The backups to tape spanned across (so far...as they are still running) 2 LOT5 tape cartridges and the tape system experience 6"disconnects" so far (Event ID 15 errors).

I have replaced the LTO-4 drive, GBIC, cable, switch port and switch. I attributed the spanning to the particular LTO5 cartridge needing a "full erase" via DPM (3 hours!). Personal Open source Business Explore Sign up Sign in Pricing Blog Support Search GitHub This repository Watch 772 Star 6,037 Fork 4,887 arduino/Arduino Code Issues 688 Pull requests 122 Projects http://homeshareware.com/cannot-write/cannot-write-to-device-lpt1.html Thanks Brendan Monday, June 02, 2014 7:37 AM Reply | Quote 0 Sign in to vote Brendan, That's good news!

Thanks brendan Proposed as answer by brendan88 Monday, June 09, 2014 2:56 PM Friday, May 23, 2014 4:30 PM Reply | Quote 0 Sign in to vote Hi Joe, Not a I've marked that tape's barcode to perform a full erase on it before it is used for backup again. Thanks in advance, Joe Monday, November 11, 2013 7:17 PM Reply | Quote All replies 0 Sign in to vote Hi, Basically, what is happening is the library / drive is

can be the bootloader structure or the PID.

Thanks in advance, Joe Thursday, June 12, 2014 8:17 PM Reply | Quote 0 Sign in to vote Hi, That is normal - all the mounted volumes used by DPM Possible cleanme signal detection failure. ([1167] The device is not connected. )[Major] From: [email protected] "HP:Ultrium 2-SCSI_1_server10" Time: 5/26/2009 12:52:48 PM[90:161] Cannot write filemark. ([1167] The device is not connected. )[Major] From: I reloaded the OS and, with the Microsoft DPM Team's asistance (thank you, Prosenjit!), was able to restore the backed-up DPM database and get back my Protection Group and Recovery Points. Thanks for the help, Mike!

I hope to hear back from them today at some point. This is due to the rapid rate at which the TAPE.LOG can grow with this option set. Note: the most recent spanning issue listed above was the result of us backing up too much data to fit onto an LTO5 cartridge. http://homeshareware.com/cannot-write/cannot-write-to-device-5-i-o-error.html As I have heard from others that have suffered at the hands of DPM, it's a nightmare, up there with Vista.

GMT+13:00 :: Auckland GMT+13:00 :: Fiji GMT+13:00 :: Nuku'alofa GMT+13:00 :: Tokelau Is. Joe Wednesday, June 25, 2014 5:42 PM Reply | Quote 0 Sign in to vote Well... Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This may be causing DPM to write to the 2nd tape...

The HP Library and Tape Tools (when running a full tape test - 1.5TB) generated an error at about 645GB into the test. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. I have Support tickets open with HP (2nd level) and Microsoft. Friday, May 23, 2014 4:51 PM Reply | Quote Moderator 0 Sign in to vote Hi, If the problem is that prevalent,I would insist that HP support try to duplicate the

I haven't been able to upload any sketches on it (I bought it yesterday) Firstly I get this: avrdude: ser_open(): can't open device "/dev/ttyACM2": Device or resource busy
avrdude: ser_send(): write For a normal Uno, this only causes problems when you upload directly after plugging in, but since a Leonardo resets its USB during upload, this might cause this problem, I believe. My bad...I had cut-n-pasted leaving the wrong TXT file name at the end of the command. He persists in his earlier view, that Luther was right in his spirit but wrong in his language, and chooses not  to make a public judgment against him, saying only that

So I think we can agree that this is definitely a DPM problem. Tuesday, May 27, 2014 9:16 AM Reply | Quote 0 Sign in to vote Hi Joe, We're going to be performing the re-install soon, I'll let you know if it resolves I'll continue to monitor the operation of the autoloader and contact HP in the event the Event IDs persist.

Back to Top