SQL Server 7.0 with SQL Server 2005

SQL Server 7.0 with SQL Server 2005

• fpdeguzman78

  The error, -2139684854 = 0x 8077000A
  indicates a memory allocation failure.
  
  Can you please post the EXACT T-SQL backup command that is being sent to SQL 7.0 when this error occurs.
  If Legato does not provide a way to trace this, you could also try the "sql profiler" tool.
  
  Another piece of troubleshooting might help me help you...
  Turn on trace flags 3605, 3213.
  This will ensure that the bufferring configuration being attempted by the backup is traced to the sql errorlog.
  Please also post that info.
  
  
  Thanks,
  -Steve
  
  
  
  

• vskhyd

  The KB article you reference pertains to SQLVDI.DLL.
  Are you using a third-party backup tool (not directly the SQL backup tools).
  
  In general, you want to avoid installing older products after newer products.
  
  I expect that if you start with SQL7, then add a named instance with SQL2005, you should be OK.
  
  Please provide more information about the failure:
  - what tool were you using (GUI, T-SQL, etc)
  - what type of backup
  - exactly what error message was given.  Typically, you'll get a few messages from BACKUP when it fails.  For example, if you reference a disk that doesn't exist you'll get:
  
  Server: Msg 3201, Level 16, State 1, Line 1
  [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device 'k:notthere\bad'. Operating system error 3(The system cannot find the path specified.).
  Server: Msg 3013, Level 16, State 1, Line 1
  [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is terminating abnormally.
  
  You might also look at the nt eventlog and/or sql errorlog.
  
  Thanks,
  -Steve
  
  
  

• Jong8282

  Deepak,
  
  It will help us to know what version of which backup tool you are using.
  That will help us to understand what DLLs it is looking for, and how it is loading them.
  
  Also, what order were the SQL instances installed
  Was the SQL 7.0 installed before the SQL 2005, or the other way around
  
  Have you tried the workaround stated in the KB   If so, what were the results
  
  Kevin Farlee
  
  

• April Adams

  well, Let me reveal it to you then, I am getting the same Error and I am using Legato tool for backing up the server databases. But the jobs are failing with this error.
  
  Does anyone has any idea how to get it resolved
  
  Thanks,
  
  Puneet.
  
  
  

• Tom Hirst

  Hi Kevin,
      I will not able to reveal the name of tool I am using, but i can let u know that it uses VDI for data transfer during backup and recovery.
      And irrespective of the install order backup fails with same error as mentioned in my first post.
      Though the backup from the Enterprise Manager for SQL Server 7.0 succeeds.
  
      Please let me know, if you could reproduce the issue and any resolution.
  
  Regards,
  Deepak
  
  

• André Monteiro

  Hi Steve,
      Yes i am using a thirdparty Backup Tool. I am doing a Full Physical Database Backup.
  
      I see the following error both in SQL Server 7.0 ERRORLOG and OS Event Log for the Instance.
  
  18210 :BackupVirtualDeviceSet::AllocateBuffer: failure on backup device <DEVICENAME>. Operating system error -2139684854(error not found).
  
     Same error is also logged by the Backup Tools as well.
  
     And then the error "Backup or restore operation terminating abnormally."
  
     I feel the reason is same for this as well, and this is because of some dll mismatch as in the case of SQL Server 7.0 and 2000.
  
     Please let me know if there is some other reason for this and is there any solution/workaround for this as well.
  
  Thanks,
  Deepak
  
  

  
  
  

• jiwon

  I have replicated the scenario of having both SQL 7.0 and SQL 2005 (June CTP) installed on the same (Windows 2000 Adv Server) system.
  the VDI DLL registration is working correctly without issues.
  
  Can you give more details on the order of installs
  Did you install SQL 7.0 AFTER SQL 2005   This is known to cause problems.
  
  Any details which you can provide to help us replicate the situation will help us to resolve it.
  
  Thanks,
  Kevin
  
  
• SQL Server 7.0 with SQL Server 2005