Error on Upgrade: DLL version is 5.3.0.178, and 5.4.0.55 was

meklembl

I attempted to run the upgrade on three different times the failure occurs in the same spot each time.

Do I have to uninstall and reinstall or is there a quicker fix?

Text from upgrade box:

Dev-DB: Server Component Installation - Failed
==============================================

Copy SQBServerSetup.exe to server - Successful

---

This operation completed successfully.

Run setup on server - Successful

---

This operation completed successfully.

Start SQL Backup Agent service - Successful

---

This operation completed successfully.

Check installed versions - Failed

---

The SQL Backup extended stored procedure DLL version is 5.3.0.178, and 5.4.0.55 was expected.

Check SQLBackup extended stored procedures - Successful

---

This operation completed successfully.

Delete setup file from server - Successful

---

This operation completed successfully.

Updating SQL Server information - Successful

---

This operation completed successfully.

Matthew Flatt

Hi,

Unfortunately when upgrading the SQL Backup Server Components, occasionally SQL Server will not correctly release our sqlbackup dll from memory preventing the file from being overwritten with the new version.

In these cases a reboot or restart of the SQL Server/Service will allow you to successfully upgrade, obviously this is not always feasible with production systems etc so a workaround is available.

To use the workaround please follow these steps :

First confirm this is the case by running the following command DBCC xp_sqlbackup(FREE) in SSMS or Query Analyzer and try to delete the file xp_sqlbackup.dll from the following location :

SQL Server 2000 x86 : %:\Program Files (x86)\Microsoft SQL Server\MSSQL\Binn

SQL Server 2000 x64 : %:\Program Files\Microsoft SQL Server\MSSQL\Binn

SQL Server 2005 x86 : %:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Binn

SQL Server 2005 x64 : %:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn

If you can delete this file please run the Server Components installer again, if you cannot follow these steps :

Locate the new version of xp_sqlbackup.dll from the Server Components installation folder, by default this is :

%:\Program Files\Red Gate\SQL Backup\<instance name>\Win32 (x86 Windows, x86 SQL Server)

%:\Program Files (x86)\Red Gate\SQL Backup\<instance name>\Win32 (x64 Windows, x86 SQL Server)

%:\Program Files (x86)\Red Gate\SQL Backup\<instance name>\Win64 (x64 Windows, x64 SQL Server)

Make a copy of the file and rename it to xp_sqlbackup_new.dll, now place the renamed file into your SQL Server Instances' Binn folder.

Unregister the extended stored procedures using the following commands in SSMS or Query Analyzer :

EXEC master..sp_dropextendedproc sqlbackup
EXEC master..sp_dropextendedproc sqbstatus
EXEC master..sp_dropextendedproc sqbmemory
EXEC master..sp_dropextendedproc sqbdir
EXEC master..sp_dropextendedproc sqbutility
EXEC master..sp_dropextendedproc sqbdata
EXEC master..sp_dropextendedproc sqbtest
EXEC master..sp_dropextendedproc sqbteststatus
EXEC master..sp_dropextendedproc sqbtestcancel

Register the extended stored procedures using the renamed file with the following :

EXEC master..sp_addextendedproc sqlbackup, 'xp_sqlbackup_new.dll'
EXEC master..sp_addextendedproc sqbstatus, 'xp_sqlbackup_new.dll'
EXEC master..sp_addextendedproc sqbmemory, 'xp_sqlbackup_new.dll'
EXEC master..sp_addextendedproc sqbdir, 'xp_sqlbackup_new.dll'
EXEC master..sp_addextendedproc sqbutility, 'xp_sqlbackup_new.dll'
EXEC master..sp_addextendedproc sqbdata, 'xp_sqlbackup_new.dll'
EXEC master..sp_addextendedproc sqbtest, 'xp_sqlbackup_new.dll'
EXEC master..sp_addextendedproc sqbteststatus, 'xp_sqlbackup_new.dll'
EXEC master..sp_addextendedproc sqbtestcancel, 'xp_sqlbackup_new.dll'

The Server Components should now function correctly, when using this workaround please replace the xp_sqlbackup.dll in the Binn folder after your next reboot.

Please let us know if this does the trick.

meklembl

Thanks. I restarted the sql server. Ran the DBCC and copied the dll unto the server and that seems to have done it.
Larry