Forum Discussion

gcgctech's avatar
gcgctech
17 years ago

Error E7B70001

I'm running BESR 7.0 on Server 2003 and have started receiving the following error:
 
Description: Error EC8F17B7: Cannot create recovery points for job: Recovery point of C:\. Error E7B70001: Win32/Win64 API DeviceIoControl(IOCTL_SNAP_VOLUME_EX) failed. Error EBAB03F1: The requested resource is in use.

I tried the fixinstall.bat as suggested from an earlier post, but it still didn't correct the issue.  Anyone had any luck with this?

 

Backup and Recovery
BESR 7.x and Earlier
System Recovery

3 Replies

Sort By
  • Stephen_March_2's avatar
    Stephen_March_2
    Level 3
    17 years ago
    I have the same problem on numerous servers. It happens randomly, I assume its when VSS and BESR and BE11d all fight over the Shadow Copy Service.
     
    I can fix the issue by rebooting, but its not always convenient. I have tried restarting services, running fixinstall.bat, but so far the reboot is my only option.
     
    Any ideas??
  • Michael_Foitzik's avatar
    Michael_Foitzik
    17 years ago

    Same problem on our Exchange Server with the latest BESR 7. Incremental Backup MO-FR (SA Full Backup is OK) is not working. These messages appear :

    Messages Application Event :

    Event Type:       Information
    Event Source:   MSExchangeIS
    Event Category: Exchange VSS Writer
    Event ID:           9604
    Date:                4/22/2008
    Time:                7:15:52 PM
    User:                N/A
    Computer:         SRV02
    Description:

    Exchange VSS Snapshot metadata document has been collected.

    For more information, click http://www.microsoft.com/contentredirect.asp.

     

    Event Type:       Error
    Event Source:   Backup Exec System Recovery
    Event Category: High Priority
    Event ID:           100
    Date:                4/22/2008
    Time:                7:16:08 PM
    User:                N/A
    Computer:         SRV02

    Description:

    Error EC8F17B7: Cannot create recovery points for job: Recovery point of C:\. Error E7B70001: Win32/Win64 API DeviceIoControl(IOCTL_SNAP_VOLUME_EX) failed. Error EBAB03F1: The requested resource is in use.

    Details: 0xE7B70001

    Source: Backup Exec System Recovery


    I changed the schedule of the job, hoping that Exchange and  BESR are not fighting for the VSS, but the error stays.

    Any ideas ???

    Thanks in advance




    Message Edited by Michael Foitzik on 04-24-2008 11:07 AM
  • Carlos_Lamb's avatar
    Carlos_Lamb
    Level 2
    17 years ago
    Try checking the IRPStackSize value in the registry at
     
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
     
    The entry may not be there and if so the default setting of 15 may be too low. Try increasing the value to 25 and reset the server. This should solve the problem.
     
     
    Document ID: 293280
    http://support.veritas.com/docs/293280     E-Mail Colleague IconE-Mail this document to a colleague
    "Error E7D1001E: Unable to read from file error 0000046A: Not enough server storage is available to process this command," occurs when attempting to restore a Recovery Point Image with Backup Exec System Recovery (BESR).
    Exact Error Message
    Error E7D1001E: Unable to read from file error 0000046A: Not enough server storage is available to process this command

    Details:
    Warning:     Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and machine be made prior to making any registry changes.

    -Increase the IRPStackSize in the registry per Microsoft's Recommendation:
    (NOTE: The system must be restarted in order for this change to take effect).

    -Copy the image locally and restore it from a local drive.

    Related Documents:

    293361: Unable to access network shares after installing Backup Exec System Recovery 6.x and 7.x. and Event ID 2011 is recorded in the Windows Event Viewer.
     http://support.veritas.com/docs/293361


    Supplemental Material:

    System: Ref.# Description UMI: V-281-2001-30 E7D1001E: Unable to read from file. Not enough server storage is available to process this command.
    Acknowledgements
    Microsoft KB285089
    Products Applied:
     Backup Exec System Recovery Desktop Edition 6.5, 7.0, 7.01
     Backup Exec System Recovery Server Edition 6.5, 7.0, 7.01, 8.0
     Backup Exec System Recovery Windows Small Business Server Edition 6.5, 7.0, 7.01

    Last Updated: February 11 2008 10:59 PM GMT
    Expires on: 02-10-2009
    Subscribe Via E-Mail IconSubscribe to receive critical updates about this document

    Subjects:
     Backup Exec System Recovery Desktop Edition
       Restore: Restore
    Backup Exec System Recovery Server Edition
       Restore: Restore
    Backup Exec System Recovery Windows Small Business Server Edition
       Restore: Restore
    Windows Server 2003
       Publishing Status: Akami, Eol Notice, Video

    Languages:
     Russian, English (US), French, German, Spanish, Italian, Japanese, Chinese, Korean

    Operating Systems:
    Windows Server 2003

    Enterprise Server, Standard Server

    Symantec World Headquarters:
    20330 Stevens Creek Blvd. Cupertino, CA 95014
    World Wide Web: http://www.symantec.com,
    Tech Support Web: http://entsupport.symantec.com,
    E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
    FTP: ftp://ftp.entsupport.symantec.com or http://ftp.entsupport.symantec.com     

    THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.