problem running SQL Log Rescue

Undo for SQL Server.

Moderator: eddie davis

problem running SQL Log Rescue

Postby tony_h » Mon Apr 30, 2007 7:16 pm

First time user and first install.

Installed SQL Log Rescue 1.2 today and when I run it and go through the create new recovery project, I get stuck.

After LR reads the backups and analyzes them, I click Next. I get the following database error message:

Cannot load the DLL xp_LogRecue.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.).

Anyone see this before and can tell me what I am doing wrong?

Thanks
tony_h
 
Posts: 9
Joined: Mon Apr 30, 2007 7:06 pm

Postby eddie davis » Fri May 04, 2007 10:58 am

Hi Tony

Sorry that you are getting this error.

I suspect that the Log Rescue Extended Stored Procedure has not installed correctly or not installed at all on the SQL Server you are trying to analyse.

From the Tools Menu -> Select Install Extended Stored Procedure and follow the instructions that appear on screen.

The xp_LogRescue.dll file should get installed into your SQL Server's BINN folder:

C:\\Program Files\\Microsoft SQL Server\\MSSQL\\Binn

or

C:\\Program Files\\Microsoft SQL Server\\MSSQL$<instance_name>\\Binn
where <instance_name> is the name of your SQL Server Instance.

Eddie Davis
Red Gate Software Ltd
Technical Support
eddie davis
 
Posts: 943
Joined: Wed Jun 14, 2006 3:47 pm
Location: Red Gate Software

Postby tony_h » Wed May 23, 2007 8:53 pm

The file is there and looks as though it has been there since the initial install.

xp_LogRescue.dll exists at C:\\Program Files\\Microsoft SQL Server\\MSSQL\\Binn.

The server has been restarted and I am still getting this same error. Any other ideas.
tony_h
 
Posts: 9
Joined: Mon Apr 30, 2007 7:06 pm

Postby Brian Donahue » Sat May 26, 2007 11:50 pm

Hi Tony,

Can you please try performing a manual installation of xp_logrescue on the server?

The instructions are here:

http://www.red-gate.com/help/sqllogresc ... rvers.html

Scroll to the bottom and you will see the manual installation procedure.

Thanks!
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am

Postby tony_h » Tue May 29, 2007 3:15 pm

Maybe I am supposed to know this already, but when I log in to the database server using Remote Desktop (the server is behind a locked door, to which, I don't have the key), launch query analyzer and write the line below:

exec sp_addextendproc 'xp_LogRescue', 'C:\\Program Files\\Microsoft SQL Server\\MSSQL\\Binn\\xp_LogRescue.dll'

I get the following message:

Server: Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'sp_addextendproc'.

I didn't perform the install of SQL Server. Was there something not installed or am I missing something?
tony_h
 
Posts: 9
Joined: Mon Apr 30, 2007 7:06 pm

Postby Brian Donahue » Tue May 29, 2007 3:24 pm

Thanks for pointing this out and I'm sorry that the help file has a typo. It should read sp_addextendedproc.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am

Postby tony_h » Tue May 29, 2007 7:26 pm

Sorry I didn't notice that.

When I run the corrected name I get the following error:

Server: Msg 2714, Level 16, State 7, Procedure sp_addextendedproc, Line 26
There is already an object named 'xp_LogRescue' in the database.

Looks like it is already installed. Anything else to try?
tony_h
 
Posts: 9
Joined: Mon Apr 30, 2007 7:06 pm

Postby Brian Donahue » Tue May 29, 2007 10:18 pm

Hi Tony,

Can you try this query and see if xp_logrescue works from Query Analyzer?
Code: Select all
DECLARE @logfilename nchar(261)
DECLARE @challange int
set @challange = 12345
DECLARE @minFileID int
set @minFileID = 0
SET @logfilename  = (select top 1 filename from
<name of database>..sysfiles1  where (status & 0x40) !=0)
SET @logfilename  = RTRIM(@logfilename) + '*'
exec master..xp_LogRescue @challange, @logfilename , @minFileID


Remember to replace <name of database> with the name of a database that you want to analyze. This should return one small row of information if it works properly.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am

Postby tony_h » Tue May 29, 2007 11:04 pm

When I put this in Query Analyzer:

DECLARE @logfilename nchar(261)
DECLARE @challange int
set @challange = 12345
DECLARE @minFileID int
set @minFileID = 0
SET @logfilename = (select top 1 filename from
CR_PPM..sysfiles1 where (status & 0x40) !=0)
SET @logfilename = RTRIM(@logfilename) + '*'
exec master..xp_LogRescue @challange, @logfilename , @minFileID

I get this result:
ODBC: Msg 0, Level 16, State 1
Cannot load the DLL xp_LogRescue.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.).

I double-checked the file location and found the dll (xp_LogRescue.dll) here:
C:\\Program Files\\Microsoft SQL Server\\MSSQL\\Binn

I really appreciate all of your help.
tony_h
 
Posts: 9
Joined: Mon Apr 30, 2007 7:06 pm

Postby tony_h » Tue May 29, 2007 11:09 pm

I don't know if this makes a difference or not, but I thought I should mention it. I installed the software remotely using Remote Desktop Connection. I was not logged in using the \\console switch.

Would this affect anything?
tony_h
 
Posts: 9
Joined: Mon Apr 30, 2007 7:06 pm

Postby Brian Donahue » Wed May 30, 2007 11:09 am

It shouldn't make any difference; installing the extended stored procedure is a thing that is specific to the SQL Server, you wouldn't need to worry that the application is available to all terminal services users.

What happens when you

exec sp_helpextendedproc 'xp_logrescue'
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am

Postby tony_h » Wed May 30, 2007 3:21 pm

Switching to text output so I can paste here...

name dll
--------------------- ------------------------------
xp_LogRescue xp_LogRescue.dll
tony_h
 
Posts: 9
Joined: Mon Apr 30, 2007 7:06 pm

Postby Brian Donahue » Wed May 30, 2007 5:46 pm

You're not using a 64-bit version of SQL Server, are you? xp_logrescue.dll is 32-bit code and isn't going to work on a 64-bit edition of SQL Server.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am

Postby tony_h » Wed May 30, 2007 6:38 pm

I don't think so. I think the 64-bit version of 2000 requires specific hardware (Intel Itanium - maybe, don't remember exactly).

I don't know if this clarifies but when I run the following statement in QA:

Code: Select all
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY
('productlevel'), SERVERPROPERTY ('edition')

I get these results

8.00.760 SP3 Standard Edition


Database administration is performed by 2 people. One configures the hardware and software, and I manage the data (also a developer).
tony_h
 
Posts: 9
Joined: Mon Apr 30, 2007 7:06 pm

Postby Brian Donahue » Thu May 31, 2007 9:49 am

How about this:

exec sp_dropextendedproc 'xp_LogRescue'
DBCC xp_LogRescue (FREE)
*copy your xp_LogRescue.dll to the SQL Server's BINN directory (C:\\program files\\microsoft sql server\\mssql\\Binn)
exec sp_addextendedproc 'xp_LogRescue', 'xp_LogRescue.dll'
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am

Next

Return to SQL Log Rescue

Who is online

Users browsing this forum: No registered users and 1 guest