12289 Unexpected Error Deviceiocontrol
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: VSS issue, event ID 22, 12289, 12293, error 0x8004230f vss 12289 unexpected error deviceiocontrol Failed to retrieve volumes that are eligible for shadow copies Windows Server
Volume Shadow Copy Service Error Unexpected Error Deviceiocontrol 12289
> Backup – Windows and Windows Server Question 0 Sign in to vote I have a new
Volume Shadow Copy Service Error: Unexpected Error Deviceiocontrol(\\?\fdc#generic_floppy_drive
Dell R710 that I have 2008 Server R2 64-bit installed. It's role is file server. I first noticed there were VSS initialization issues in BackupExec and that the system
Event Id 12289 Unexpected Error Deviceiocontrol
state wasn't getting backed up. Then I would run "vssadmin list writers" from CMD and system writer would be timing out.... Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {18370018-3454-46cf-a352-db13b2536aa6} State: [7] Failed Last error: Timed out I would also get Event ID 12289 Volume Shadow Copy Service error: volume shadow copy service error unexpected error deviceiocontrol volume Unexpected error DeviceIoControl( Also I can't configure shadow copies due to error 0x8004230f "Failed to retrieve volumes that are eligible for shadow copies. PLEASE HELP! Friday, May 11, 2012 3:21 PM Reply | Quote All replies 0 Sign in to vote 1. As the first action, please restart your server and see if the mentioned error messages and conditions occur again. 2. Run chkdsk /f C: on the server, reboot the server and see if the mentioned error messages and conditions occur again. 3. Do you have installed Service Pack 1 on the problematic server? 4. Pleas run the vssadmin list writers command and post the output completely. 5. Run diskpart, then run list volume and then report back the result. 6. Run vssadmin list providers and report back the result. 7. I also suggest you to modify the registry as follows: Click Start, click Run, type regedit, and then click OK.Locate and then click the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VolSnapOn the Edit menu, point to New, and then click D
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community vss_e_writer_status_not_available MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About volume shadow copy service error unexpected error deviceiocontrol the parameter is incorrect Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English kb2460907 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Unable to do Snapshots with error: Event ID: 12289 https://social.technet.microsoft.com/Forums/office/en-US/1b926c85-b866-464b-9590-70506ba9d8ce/vss-issue-event-id-22-12289-12293-error-0x8004230f-failed-to-retrieve-volumes-that-are-eligible?forum=windowsbackup and setup.api.dev log reports Error 2: The system cannot find the file specified - SourceFile - vxio.sys Article:000015094 Publish: Article URL:http://www.veritas.com/docs/000015094 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 https://www.veritas.com/support/en_US/article.000015094 in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem 1. Snap shots errors with Event ID: 12289 2. Microsoft Shadow Copies errors out with Error 0x80042306 3. Storage Foundation for Windows 5.1/6.x component shows up as unknown or is missing in system devices in device manager Error Message System Application Logs: Log Name: ApplicationSource: VSSEvent ID: 12289Task Category: NoneLevel: ErrorKeywords: ClassicDescription:Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{5f698f4d-35eb-4d74-b4b9-8587dd732649} - 0000000000000198,0x0053c008,00000000005BED40,0,00000000014BA080,4096,[0]). hr = 0x80070079, The semaphore timeout period has expired. The following issue occurs when trying to do a shadow copy. Setup.api.logs: flq: SourcePath - [c:\windows\inf] flq: SourceFile - [vxio.sys] flq: Error 2: The system cannot find the file specified. [Exit status: FAILURE(0x00000002)] Device manager shows the follo
NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware vCenter™ > VMware vCenter™ Server > Discussions Please enter a title. You can not post a blank message. Please type your message and try https://communities.vmware.com/thread/309844?start=15&tstart=0 again. 1 2 3 4 Previous Next 57 Replies Latest reply: Aug 22, 2016 2:29 AM by Thorian93 Go to original post Branched to a new discussion. This content has been marked as final. Show 57 replies 15. Re: Problem with quiesced snapshot on Server 2008 R2 with ESXi unexpected error 4.1 U1 mulio May 4, 2011 12:53 AM (in response to riki78) Hey Folks I´ve got some news about our snapshot problems.1) The DeviceIoControl ErrorVolume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} - 0000000000000418,0x00560000,0000000000000000,0,000000000027CDB0,4096,[0]). hr = 0x80070001, Incorrect function.I solved this issue by disabling the floppy device @ the "Device unexpected error deviceiocontrol Manager".After this --> The error is gone away!2) Some NTFS Errors - EventID 57 / EventID 137Log Name: SystemSource: NtfsDate: 11.04.2011 22:20:57Event ID: 137Task Category: (2)Level: ErrorKeywords: ClassicUser: N/ADescription:The default transaction resource manager on volume \\?\Volume{d533451f-6478-11e0-94e8-005056ae007a} encountered a non-retryable error and could not start. The data contains the error code.For these error i haven´t found yet a possible solution - but maybe a explanation for this.@ http://technet.microsoft.com/de-de/library/ee923636(WS.10).aspx i found some interesting thingSource: http://technet.microsoft.com/de-de/library/ee923636(WS.10).aspx If the shadow copy is successfully created, the Volume Shadow Copy Service returns the location information for the shadow copy to the requester. In some cases, the shadow copy can be temporarily made available as a read-write volume so that VSS and one or more applications can alter the contents of the shadow copy before the shadow copy is finished. After VSS and the applications make their alterations, the shadow copy is made read-only