SQL Backup Error

SamCSamC Posts: 28
edited July 12, 2005 5:10AM in SQL Backup Previous Versions
Twice now, I've seen pop-up dialogues on my sever stating:
SQL Backup console interface encountered an error and needed to close.
szAppName : sqlbackupc.exe szAppVer : 3.1.0.1 szModName : sqlbackupc.exe
szModVer : 3.1.0.1 offset : 00004890
It occurs exactly at one of the quarter-hour times that the transaction logs are backed up.

Comments

  • Brian DonahueBrian Donahue Posts: 6,590 New member
    Hello Sam,

    Is this the result of doing a backup from a DOS Prompt or Windows Scheduler, or from a SQL job on the server? I was just wondering because as far as I know both of them rely on SQLBackupc.exe.
  • It's a schedule job from SQL Agent.
  • peteypetey Posts: 2,358 New member
    Could you pls check the vdi.log log file (in SQL Server log folder) to see if there were any errors reported there during the time of failure? Thanks.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • I'm having the same problem when running my backup as a scheduled job from the agent. I've included my vdi.log file contents.
    ----------------------------------------------
    2005/05/29 02:00:05 pid(5412) tid(4104)
    Error on Global\SQLBACKUP_50073565
    Error at CVDS::Create: Create Memory Status Code: 5, x5
    Explanation: Access is denied.
    
    ----------------------------------------------
    2005/05/30 02:00:06 pid(4604) tid(3112)
    Error on Global\SQLBACKUP_46399453
    Error at CVDS::Create: Create Memory Status Code: 5, x5
    Explanation: Access is denied.
    
    ----------------------------------------------
    2005/05/30 02:00:08 pid(4604) tid(3112)
    Error on Global\SQLBACKUP_46399453
    Error at CVDS::Create: Create Memory Status Code: 5, x5
    Explanation: Access is denied.
    
    ----------------------------------------------
    2005/05/31 02:00:07 pid(5604) tid(5208)
    Error on Global\SQLBACKUP_46460893
    Error at CVDS::Create: Create Memory Status Code: 5, x5
    Explanation: Access is denied.
    
    ----------------------------------------------
    2005/05/31 02:00:09 pid(5604) tid(5208)
    Error on Global\SQLBACKUP_46460893
    Error at CVDS::Create: Create Memory Status Code: 5, x5
    Explanation: Access is denied.
    
    ----------------------------------------------
    2005/06/01 02:00:09 pid(4776) tid(5208)
    Error on Global\SQLBACKUP_159698029
    Error at CVDS::Create: Create Memory Status Code: 5, x5
    Explanation: Access is denied.
    
    ----------------------------------------------
    2005/06/04 01:00:12 pid(4460) tid(5988)
    Error on Global\SQLBACKUP_159394925
    Error at CVDS::Create: Create Memory Status Code: 5, x5
    Explanation: Access is denied.
    
    ----------------------------------------------
    2005/06/04 02:00:10 pid(4664) tid(6140)
    Error on Global\SQLBACKUP_159407213
    Error at CVDS::Create: Create Memory Status Code: 5, x5
    Explanation: Access is denied.
    
    ----------------------------------------------
    2005/06/06 02:00:47 pid(3048) tid(4108)
    Error on Global\SQLBACKUP_160296045
    Error at CVDS::Create: Create Memory Status Code: 5, x5
    Explanation: Access is denied.
    
    ---------------------------------------------
    2005/06/07 01:00:32 pid(5016) tid(4408)
    Error on Global\SQLBACKUP_160377965
    Error at CVDS::Create: Create Memory Status Code: 5, x5
    Explanation: Access is denied.
    
    ----------------------------------------------
    2005/06/07 02:00:14 pid(3256) tid(5032)
    Error on Global\SQLBACKUP_160242797
    Error at CVDS::Create: Create Memory Status Code: 5, x5
    Explanation: Access is denied.
    
    ----------------------------------------------
    2005/06/07 02:00:16 pid(3256) tid(5032)
    Error on Global\SQLBACKUP_160242797
    Error at CVDS::Create: Create Memory Status Code: 5, x5
    Explanation: Access is denied.
    
    

    Thanks,

    Scott
  • I haven't seen this problem since my last post. I'm also running the most recent update.

    Try: HELP, Check for Updates
  • Hi Scott

    Can you send us over the information to [email protected] so we can try and replicate it here?

    Regards
    Dan
    Daniel Handley
    Red Gate Software Ltd
  • I've sent this to support.


    Thanks,

    Scott
  • I'm getting the same response in my vdi.log when the VDI 1000 error is thrown during a backup.

    From the error email...

    6/14/2005 2:37:00 PM: BACKUP DATABASE [master] TO DISK = '\\<server_name>\sqlbackups4\dwdev01\dwdev01_master_FULL.sqb' WITH NAME = '', DESCRIPTION = '', INIT, VERIFY, ERASEFILES_ATSTART = 2, COMPRESSION = 2 6/14/2005 2:37:00 PM:
    6/14/2005 2:37:04 PM: VDI error 1000: Failed to create virtual device. Check that the SQL Server instance you are trying to connect to is running. Error code: -2147024891 () 6/14/2005 2:37:04 PM: Access is denied

    From the VDI.LOG...

    2005/06/14 14:37:02 pid(6140) tid(5708)
    Error on Global\SQLBACKUP_199704205
    Error at CVDS::Create: Create Memory Status Code: 5, x5
    Explanation: Access is denied.

    2005/06/14 14:37:04 pid(6140) tid(5708)
    Error on Global\SQLBACKUP_199704205
    Error at CVDS::Create: Create Memory Status Code: 5, x5
    Explanation: Access is denied.

    What's causing this error?

    Thanks,

    - Bern
  • I am still having the errors outlined in this post. Has there been any success in finding a solution? I have sent this to support but haven't recieved a response as of yet.

    Please let me know.

    Thanks,

    Scott
  • peteypetey Posts: 2,358 New member
    Does this error happen as part of a script that makes multiple backups?
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Yes, I'm backing up multiple db's with a single script using the script in the help document.

    Thanks for your response.
  • Brian DonahueBrian Donahue Posts: 6,590 New member
    Hello everybody,

    Red Gate has fixed this problem by changing the code that generated the virtual device names for the backup. The problem seems to be that trying to run many (hundreds) of backups simultaneously may cause an access denied error in VDI because SQL Backup is generating a device name that's already in use.

    Please contact us at [email protected] if you are having the problem and we will send the fix for sqlbackupc.exe.
This discussion has been closed.