Comments
9 comments
-
Can you please post the query that runs sqbutility? Thanks. -
This is the complete SQL batch that executes the SQBUtility.
__________________________
declare @P1 int
set @P1=NULL
declare @P2 nvarchar(4000)
set @P2=NULL
declare @P3 int
set @P3=NULL
exec master..sqbutility @Parameter1 = 1080, @Parameter2 = @P1 output, @Parameter3 = @P2 output, @Parameter4 = @P3 output
select @P1, @P2, @P3
__________________________ -
Could you please check if the SQL Backup Agent service is started on that server? If it is not started, could you please try to start it manually? Thanks.
-
Peter,
The service is started and has been running since installation. Regular backups occur. The only problem is getting the client to work on this server.
Terry -
Could you pls download a debug version of xp_sqlbackup.dll from here (http://www.yohz.com/downloads/xp_sqlbackup.zip)? Replace the existing version in the SQL Server Binn folder. You may need to unload the existing version from SQL Servers' memory space first, using
DBCC xp_sqlbackup(FREE)
Then try connecting to the server using the GUI. Are you able to connect now? -
The debug version of xp_sqlbackup.dll seems to have fixed the problem with the GUI client.
-
As I stated earlier: The debug version does display records now, however the following error appears in the properties section:
Connection Error: SQB Service did not acknowledge receipt of data.(WAIT_TIMEOUT) -
Peter,
I downloaded and installed the debug version of xp_sqlbackup.dll. The client still displays the same error message.
The debug DLL has a version of 5.0.0.964.
The 5.1 DLL has a version of 5.1.0.2781.
Is the debug version correct. Did I download the right file?
Terry -
To astreet,
Could you pls run Profiler and check which of the last few SQL Backup extended stored procedures were ran, and when ran via Query Analyzer/SSMS, results in the same error? Thanks.
To tlbroadbent,
Yes, that is a mistake on my part. The version number should actually be 5.2.0.2806. Rest assured that it is still the latest debug version.
Add comment
Please sign in to leave a comment.
When I start the client on this server and register the local server instance, the following message is displayed.
____________________________________
Server Problem with MyServer
A problem was encountered whilst communicating with the server.
System.InvalidCastException: Object cannot be cast from DBNull to other types.
at System.DBNull.System.IConvertible.ToInt32(IFormatProvider provider)
at System.Convert.ToInt32(Object value)
at _16._1(SqlConnection , _17 , Int32& , String& , Int32& )
at _16._1(SqlConnection , Int32& , String& )
at _16._1(Server , Int32& , String& )
at RedGate.SQLBackup.Engine.Server._10()
at RedGate.SQLBackup.Engine.Server.RefreshServerInformation()
____________________________________
I have registered other SQL Server instances with SQLBackup 4.6 installed and do not get this error. The client displays appropriate information from these other instances.
In this thread http://www.red-gate.com/messageboard/viewtopic.php?p=18668&sid=c72b4d230cad21000bd0e5de1ad0d44b, Eddie Davis indicated that the problem occurs as the client reads MSDB backup history. Another person stated that he had deleted the entries in MSDB and eliminated the problem. I do not wish to delete backup history on my server. I'm looking for another fix.
I ran a profiler trace while starting the SQLBackup client. There were no statements querying MSDB tables directly. Most of the queries check server and database status. There are also queries to check the status of the SQLBackup components. The final query executes SQBUtility. This extended stored procedure returns three values, two of which are integers. When I run the query in Query Analyzer all three values are NULL. Is it possible that SQBUtility is returning the NULL value that causes the client error?
Thank you for your assistance.
Terry Broadbent