Log Rescue generating an exception

[kevine323]

When attaching a log file to the application, I get the following exception in the post processing of the log.

RedGate.LogRescue.UI.exe
Application has generatd an exception that could not be handled.

Process id= 0xaec (2796), Treah id=0xe14 (3604)

[Brian Donahue]

Hi Kevin,

Like all of our code that's written in .NET, these types of exceptions are thrown from .NET's mscorlib, so our program hadn't even successfully loaded. I'd recommend perhaps installing or reinstalling Microsoft .NET Framework 1.1 to fix the problem.

Hopefully that'll get it!
_________________
Brian Donahue
Technical Support
Red Gate Software Ltd.
44 (0)870 160 0037 ext 8521
US and CAN 1-866-RED GATE ext 8521

[kevine323]

FYI: Since I am also supporting SQL 2005 (which requires .net 2.0) this could present a problem. I'll give is a shot and let you know what i find out.

[kevine323]

No luck reinstalling .net 1.1. The problem only occurs about 25% of the time though, so I dont know why it would load most of the time but not all.

[Brian Donahue]

Hi Kevin,

What steps do we need to perform to reproduce the problem?
_________________
Brian Donahue
Technical Support
Red Gate Software Ltd.
44 (0)870 160 0037 ext 8521
US and CAN 1-866-RED GATE ext 8521

[kevine323]

Let me tell you about our setup

Server:
SQL 2000 SP3
4GB Memory
4GB DB with Full Recovery Mode

Client:
Freshly loaded Windows 2000 SP4
MDAC 2.8
.Net Framework 1.1

The extended stored procedure is installed on our server. The client machine is running the SQL Log Rescue (SLR). When I create a new project with SLR, I specify the server and database. At the next screen, I include our transaction log backup file (xxxxxx.bak) and proceed to the next screen. Everything runs normal until SLR gets to the post processing portion. That's when the exception is thrown.
_________________
Kevin Eckart
Database Administrator
USA Truck, Inc
Kevin.Eckart@usa-truck.com
http://kevine323.blogspot.com/

[Brian Donahue]

Hi Kevin,

Log Rescue really needs a full database backup file to function properly. You'd mentioned that you'd specified a transaction log backup only. Have you got a full backup file for the database that you can specify?

Thanks!
_________________
Brian Donahue
Technical Support
Red Gate Software Ltd.
44 (0)870 160 0037 ext 8521
US and CAN 1-866-RED GATE ext 8521

[kevine323]

Brian, thank you for your reply, I will try this and get back with you. It's very odd that my method of only specifying the log file that I want to read would work 75% of the time. I'll let you know how the testing goes.
_________________
Kevin Eckart
Database Administrator
USA Truck, Inc
Kevin.Eckart@usa-truck.com
http://kevine323.blogspot.com/

[Brian Donahue]

Hi Kevin,

Log Rescue shouldn't be 'crashing' in any case. The design of the software is supposed to cope with this sort of situation, really, the idea being that 'if it can't get everything back it can get back as much as possible'. But I think it would be a good idea to give the software all of the information it needs to work 100% correctly. There may be some sort of issue there, such as a schema change, that would potentially cause a null-reference problem.
_________________
Brian Donahue
Technical Support
Red Gate Software Ltd.
44 (0)870 160 0037 ext 8521
US and CAN 1-866-RED GATE ext 8521

[kevine323]

Hi Brian, I thought the same thing about maybe there was a schema change and for some reason it couldnt handle it. So I restored the latest DB and a Log from that day and still got the same error. I'll keep looking.
_________________
Kevin Eckart
Database Administrator
USA Truck, Inc
Kevin.Eckart@usa-truck.com
http://kevine323.blogspot.com/