Process terminated unexpectedly. Error code: -2139684860

swhaleyswhaley Posts: 5
edited July 19, 2008 5:22PM in SQL Backup Previous Versions
I have received the following error on multiple occasions:

7/10/2008 6:10:22 PM: Thread 0 error:
Process terminated unexpectedly. Error code: -2139684860
7/10/2008 6:10:22 PM: Thread 1 error:
Process terminated unexpectedly. Error code: -2139684860
7/10/2008 6:10:22 PM: Thread 2 error:
Process terminated unexpectedly. Error code: -2139684860
7/10/2008 6:10:22 PM: Thread 3 error: Backup error: Access violation at address 10009801 in module 'zlib1.dll'. Read of address 068F6000
7/10/2008 6:10:22 PM: Thread 4 error:
Process terminated unexpectedly. Error code: -2139684860
7/10/2008 6:10:22 PM: Thread 5 error:
Process terminated unexpectedly. Error code: -2139684860
7/10/2008 6:10:22 PM: Thread 6 error:
Process terminated unexpectedly. Error code: -2139684860
Process terminated unexpectedly. Error code: -2139684860

7/10/2008 6:10:22 PM: Database size : 27.419 GB

SQL error 3013: SQL error 3013: BACKUP DATABASE is terminating abnormally.

Is there a patch for this error or something I can do to avoid this?

Thanks,
Steve Whaley
[email protected]

Comments

  • peteypetey Posts: 2,358 New member
    Are you using SQL Backup 5.3? Thanks.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • I am using ver. 5.2.0.2825.
    Steve Whaley
    [email protected]
  • Brian DonahueBrian Donahue Posts: 6,590 New member
    Hi,

    I'm not sure if this is a coincidence, but if you convert the error code to hex using Windows Calculator, you get FFFFFFFF80770005, and 0x80770005 is defined in SQL Server VDI as a "VDI Security Error". I think it may be a good idea to check the SQL Server's log location for a VDI.Log file, which is usually created when VDI fails. SQL Backup uses VDI to access the SQL database backup stream.

    It may be a simple permissions problem or something like that. A list of all known permissions required to run a SQL Backup can be found here.

    Hopefully this helps!
Sign In or Register to comment.