Problem upgrading to 4.2.0.425

satterw

Clustered Windows 2000 servers running SQL 2000 SP4. Have been running 4.1.0.207 fine for a few weeks. I copied SQBServerSetup.exe to the active cluster node, and it hangs during "Extracting files..." . I've failed the cluster over and it occurs on the other node also. I'm logged in as the local administrator, so permissions should not be a problem. I've also rebooted each node to no avail. I ran "SQBServerSetup.exe /log" and the logfile shows the following:

2006-05-21 22:10:08 Log opened.
2006-05-21 22:10:08 Setup version: Inno Setup version 5.1.6
2006-05-21 22:10:08 Original Setup EXE: L:\SQBServerSetup.exe
2006-05-21 22:10:08 Setup command line: /SL4 $3016E "L:\SQBServerSetup.exe" 1186588 52224 /log
2006-05-21 22:10:08 Windows version: 5.00.2195 SP4 (NT platform: Yes)
2006-05-21 22:10:08 64-bit Windows: No
2006-05-21 22:10:08 Processor architecture: x86
2006-05-21 22:10:08 User privileges: Administrative
2006-05-21 22:10:08 64-bit install mode: No
2006-05-21 22:10:08 Created temporary directory: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\is-8BF57.tmp
2006-05-21 22:10:11 Starting the installation process.
2006-05-21 22:10:11 Directory for uninstall files: C:\Program Files\Red Gate\SQL Backup\(LOCAL)
2006-05-21 22:10:11 -- File entry --
2006-05-21 22:10:11 Dest filename: C:\Program Files\Red Gate\SQL Backup\(LOCAL)\unins000.exe
2006-05-21 22:10:11 Time stamp of our file: 2006-05-21 22:10:08.445
2006-05-21 22:10:11 Dest file exists.
2006-05-21 22:10:11 Time stamp of existing file: 2006-04-24 21:02:08.608
2006-05-21 22:10:11 Version of our file: 51.42.0.0
2006-05-21 22:10:11 Version of existing file: 51.42.0.0
2006-05-21 22:10:11 Installing the file.
2006-05-21 22:10:11 Leaving temporary file in place for now.

Any suggestions?

petey

Could you pls try with the SQBServerSetup file in this post (http://www.red-gate.com/messageboard/viewtopic.php?t=2387)?

satterw

Nope, same problem with that EXE also. I have a log file from SysInternals FileMon of the filesystem activity if that would help. No virus software on this server that might be locking files.

I do get a System Event Log message when I run the setup: "Cluster resource 'SQL Backup Agent' failed." The service is running when I check it after the fact, but it sounds like it is stopping and being restarted. I have tried running the setup with the service running and stopped.

Brian Donahue

The error sounds to me as if you already have the SQL Backup Agent Service configured as a cluster resource, and I'd imagine that this would keep you from reinstalling it. You may need to open MS Cluster Administrator, delete the SQL Backup Agent Service as a resource, and then do the install or upgrade on the loacl node. By the way, the node doesn't need to be active to install SQL Backup. You can install the software whether the node is currently active or not.

satterw

That worked, thanks. My console on my PC is still showing the server version at 4.1.0.207, even though I've verified all the EXEs and DLLs on the server are 4.2.0.205. I also used Process Explorer to verify that the running SQBCoreService.exe is 4.2.0.205. It looks like master..sqbutility is still returning 4.1.0.207.

Looks like there is an old version of xp_sqlbackup.dll in C:\Program Files\Microsoft SQL Server\MSSQL\Binn that it must be reading this info from, even though the service starts from C:\Program Files\Red Gate\SQL Backup\(LOCAL).

I can try renaming the one in C:\Program Files\Microsoft SQL Server\MSSQL\Binn if needed, just seems a little weird.

petey

The DLL that SQL Server uses is the one in the Binn folder. Try running

DBCC xp_sqlbackup(FREE)

and then try replacing the 4.1 DLL with the 4.2 one.

satterw

Doesn't seem to work - I still get the old version even after replacing it with the new DLL in the BINN directory. Guess it is still loaded in memory. I can fail the cluster over after hours - bringing SQL down and back up again should take care of it, unless you want me to try something else.

petey

Yes, it's probably still loaded in memory. Most of the core 4.2 engines should still work with the 4.1 extended stored procedure.

satterw

Failed the cluster over and upgraded the passive nodes - I'm showing the correct new version now. Thanks Brian and Petey.