Error Reported 16410
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > The device reported an error on a request to MS_UpdateNtmsOmidInfo Want to Advertise Here? Solved The device reported an error on a request to MS_UpdateNtmsOmidInfo Posted on 2011-06-09 SBS Storage Software Disaster Recovery 1 Verified Solution 3 Comments 2,110 Views Last Modified: 2012-05-11 Hi all I have a Windows SBS Server 2003 I use the backup utility in server manager to backup this system This backup has run with no issues for years Over the past few days every night the backup has failed The backup report has the following Backup Status Operation: Backup Active backup destination: 4mm DDS Media name: "Media created 09/06/2011 at 01:47" The device reported an error on a request to MS_UpdateNtmsOmidInfo. Error reported: 16410. There may be a hardware or media problem. Please check the system event log for relevant failures. An inconsistency was encountered on the media in 4mm DDS. Do not append to this media. The operation was ended. Backup completed on 09/06/2011 at 01:48. Directories: 0 Files: 0 Bytes: 0 Time: 1 second Error: C: is not a valid drive, or you do not have access. The operation was ended. Backup completed on 09/06/2011 at 01:48. Directories: 0 Files: 0 Bytes: 0 Time: 1 second ---------------------- The operation did not successfully complete. I have watched this backup run and it does the following Ntbackup starts and mounts the media After about 3 or 4 minutes it rewinds the tape After the tape rewinds the backup fa
got an HP Proliant server here with SBS2003 on it and an HP Storageworks DAT72 tape drive in it. When I run NTbackup with a new tape in there I get the error: "The device reported an error on a request to MS_UpdateNTmsOmidInfo. Error Reported: 11 There may be a hardware or media problem. Please check the system event log for relevent information. ----and---- "An inconsitency was encountered on the mdeda in 4Mm DDS. Do not append to this media. --------------- I don't see any relevant errors in the event long. Any ideas? The tape drive seems to be working fine every night with Veritas backup Exec. I wanted to get a state backup with https://www.experts-exchange.com/questions/27089135/The-device-reported-an-error-on-a-request-to-MS-UpdateNtmsOmidInfo.html NTbackup seeing that everything was running so well right now. Thanks for any suggestions. Bryce. Bryce, Jul 20, 2005 #1 Advertisements cjobes Guest Did you import and prepare the media before trying the backup? "Bryce" <> wrote in message news:... > Hi. > > I've got an HP Proliant server here with SBS2003 on it and an HP > Storageworks DAT72 tape drive in it. > > When I run NTbackup with a new tape in there http://www.winvistatips.com/threads/ntbackup-problem-with-hp-dat-72.616404/ I get the error: > > "The device reported an error on a request to MS_UpdateNTmsOmidInfo. > Error Reported: 11 > There may be a hardware or media problem. > Please check the system event log for relevent information. > > ----and---- > > "An inconsitency was encountered on the mdeda in 4Mm DDS. Do not append to > this media. > > --------------- > > I don't see any relevant errors in the event long. > > Any ideas? > > The tape drive seems to be working fine every night with Veritas backup > Exec. > > I wanted to get a state backup with NTbackup seeing that everything was > running so well right now. > > > Thanks for any suggestions. > > Bryce. > > cjobes, Jul 20, 2005 #2 Advertisements Bryce Guest O boy. It asked me if I wanted to "make it ready" or something along those lines. I clicked "yes". Is there a special process I need to follow? Any notes to be found on this? Thanks. Bryce. "cjobes" <> wrote in message news:... > Did you import and prepare the media before trying the backup? > > > "Bryce" <> wrote in message > news:... >> Hi. >> >> I've got an HP Proliant server here with SBS2003 on it and an HP >> Storageworks DAT72 tape drive in it. >> >> W
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: hyper-v error 15020 and 16410 Windows Server > https://social.technet.microsoft.com/Forums/windows/en-US/9b6e12ba-d432-4707-9a4e-a976120a5657/hyperv-error-15020-and-16410?forum=winserverhyperv Hyper-V Question 0 Sign in to vote Hiall, This morning I had a really weird problem on my infrastructure with Hyper-V. I implemented in three production machines with Windows Server 2012, two nodes and a virtualization storage node. The problem occurred when I tried to configure a VM on which I was installing Exchange Server 2010, configured as DAG. The vm error reported was not included in the cluster, and then in the CSV (configuration not supported by DAG), but it has been installed on the local disk of one of the nodes. The disk is 1TB RAID-1 configured via software. When I rebooted the vm after installing the updates, the vm is turned off by Hyper-V and there was no way to restart it. error reported 16410 Every time I felt I obtained an error like this: Microsoft-Windows-Hyper-V-VMMS event id 16410 MSVM_VMMS_CONFIGURATION_DISCONNECTED_STOPPED_VM The configuration of the virtual machine '% 1' is no longer accessible:% 3 (% 4). (Virtual machine ID% 2) As if I tried to remove it I obtained this error: Microsoft-Windows-Hyper-V-VMMS event id 15020 MSVM_VMMS_DESTROY_VM_ERROR '% 1' failed to delete. (Virtual machine ID% 2) What's even more strange, however, was when I tried to reboot the host to see if this way could to solve, something that has not happened since the physical machine has crashed and I had to reset it to KVM. To succeed in rooting out and driving the vm, I had to import the same in a new itinerary of the disk of the node, reboot the physical host by first deleting the old folder the vm and then I was able to delete the vm from Hyper-V . Now my question is, what may have been the problem that caused all this? Thanks in advance for any replies, Luca P.S. I also obtain this error when i try to delete the vm: