install problems

[Anonymous]

Hello,

My company has been using the product a while now with no problems. I recently ugraded my EL from 4.2 to to 4.6.6 (on D7 enterprise) and either at that point, or shortly thereafter EL just stopped working. I didn't notice for about a week though so I'm not sure if this was an immediate effect. The EurekaLog options is no longer in my project menu, and exceptions are not caught by EL, although my code will still compile. The other developer at my company did not have this problem.

I have tried various combinations of uninstalling and reinstalling EL with both 4.2 and 4.6 versions. Can you give any suggestions? We have the enterprise edition of EL. Thanks!

[admin]

Hello,

My company has been using the product a while now with no problems. I recently ugraded my EL from 4.2 to to 4.6.6 (on D7 enterprise) and either at that point, or shortly thereafter EL just stopped working. I didn't notice for about a week though so I'm not sure if this was an immediate effect. The EurekaLog options is no longer in my project menu, and exceptions are not caught by EL, although my code will still compile. The other developer at my company did not have this problem.

I have tried various combinations of uninstalling and reinstalling EL with both 4.2 and 4.6 versions. Can you give any suggestions? We have the enterprise edition of EL. Thanks!

Try to do this:

1)...Close all opened Delphi/CBuilder instances;
2)...Deinstall all installed EurekaLog versions;
3)...Remove all folders containings the ExceptionLog.* or ?ExceptionExpert.* files;
4)...download and install the last EurekaLog version;
5)...restart your PC.

I'm waiting to your feedback as soon as spossible, ok? :)

---
Best regards...

Fabio Dell'Aria.

[davec_ias]

This seems to have fixed it. However, I subsequently had to recompile a package which depended on ExceptionExpert7, and ran into a problem. Basically after I hit compile. delphi brought me to the ExceptionExpert7.dpr file with the message "EMessages.dcu not found" (the first file in the uses clause of ExceptionExpert7). Recompiling and reinstalling a this project, ExceptionExpert7, and another package I depended on seems to have fixed it.

In addition I kept getting messages noting that I had an out of date ExceptionLog.dcu file in my d:\dcu directory (the unit output directory for most of my code) and that I needed to reinstall the ExceptionLog package (this is not the exact text, I can't remember the exact text of the error). The fix to this seemed to be to move d:\dcu down to the bottom of my library path.

I had seen similar problems before. In the past I recall having to set the "$IMPLICITBUILD option to false in the ExceptionExper project to get a this package which depended on ExceptionExpert7 to compile.

Anyway none of these issues are stopping me right now but I hate fuzzy "solutions" to problems that I don't understand. If anyone has any insight into peculiarities that might happen when compiling packages that derive from Eureka that might be helpful.

Dave

[davec_ias]

As it turns out my problem is not fixed as I thought it was. Every time I start delphi after having compiled an application that uses EurekaLog, I get the following sequence of messages:

--
Cannot Activate EurekaLog.
The "D:\dcu" folder containing an old EurekaLog version.
Remove the old package from "Component\Install Packages" menu and deleting it's folder.
---
Can't load package c:\program files\eurekalog 4\delphi7\ExceptionExpert.bpl.
Operation Aborted.
Do you want to attempt to load thie package the next time a project is loaded?
---
This application has failed to start because ExceptionExprt7.bpl was not found. Re-installing the application may fix this problem.
---
Can't load package c:\program files\borland\delphi7\projects\bpl\RRPackage.bpl.
The specified module could not be found.
Do you want to attempt to load thie package the next time a project is loaded?
---

Deleting d:\dcu\ExceptionExpert7.dcu and restarting delphi fixes the problem until of course the next time I start delphi without remembering to delete this file. This problem started after the reinstall. Any ideas how to prevent this from happening?

[admin]

The real problem is that you cannot include any EurekaLog dependence into a package.

Try to do this:

1)...Remove the EurekaLog package dependence;
2)...Deinstall all installed EurekaLog versions;
3)...Remove all folders containings the ExceptionLog.* or ?ExceptionExpert.* files;
4)...download and install the last EurekaLog version;

[davec_ias]

Are you saying I can't create a component that subclasses from the EurekaLog component and then have it installed onto my palette via another package? Such a package would have to depend on Eurekalog correct? This would invalidate step one of the fix (...Remove the EurekaLog package dependence). So in this case it's only really a fix assuming I don't subsequently reinstall my package that depends on EurekaLog.

Here's my situation. All I want is the ability to globally intercept an exception and handle it how I would like to, and be able to get the stack trace. I need to do this in a bunch of applications and I don't want to (or have any other developers here) write the error handling code themselves or have to implement any handlers or change settings or whatever. The standard dialog and customizable html and the like that you provide is nice and all but not what I need or care to do. So I wrote a component that subclasses TEurekaLog, has a default implementation of OnExceptionNotify that does what I want (basically displays a dialog I created), and still allows the programmer to override OnExceptionNotify if they wish. ***So all I (or another developer here who has EL and my package installed) have to do is drop this component onto their form and the error handling is what it should be***. Can this be done or not with EurekaLog?

I actually had this setup working for a long time like this (with another dependant package) on both delphi 6 and delphi 7- it wasn't until I upgraded versions of EL recently that I ran into these more severe problems (I noted that in the past I had some similar problems that went away after some fiddling). In addition my setup works now assuming I delete this other copy of EurekaLog.dcu.

[admin]

[...]
So I wrote a component that subclasses TEurekaLog, has a default implementation of OnExceptionNotify that does what I want (basically displays a dialog I created), and still allows the programmer to override OnExceptionNotify if they wish. ***So all I (or another developer here who has EL and my package installed) have to do is drop this component onto their form and the error handling is what it should be***. Can this be done or not with EurekaLog?


EurekaLog it isn't created to can included its units into other installed Design-Time packages, but if you have found a mode to can do this then it's all ok! :)

PS: can you explain to me how you have proceeded?


[...]
In addition my setup works now assuming I delete this other copy of EurekaLog.dcu.

Perfect! :-)

[davec_ias]

Here, the following might have "fixed" it. I simply renamed the ExceptionLog.pas to ExceptionLog.pas.sav, which prevents an application which has ExceptionLog in the uses clause from recompiling to a new dcu and instead forces it to use the precompiled one provided by the installer in c:\program files\eurekalog 4 \delphi\7. Since a new dcu is now never created, Delphi doesn't find the newly versioned dcu during it's startup sequence and doesn't complain. I tried both removing ExceptionLog from the uses clause (for some reason the IDE puts it back in whenever I save or recompile so this didn't work) and adding the IMPLICITBUILD OFF option to the source of ExceptionLog.pas (but that didn't work either, a new dcu was still built anyway).

With regards to how I have proceeded, I simply have a package that installs a number of components including the one subclasses off EurekaLog. I have ExceptionExpert7.dcp in the requires portion of this package. Usually when I build and install this package there is no problem. Sometimes funny things happer per this thread. As far as the sub component itself, here is the source (modified to hide stuff):

type
TMyEurekaLog = class(TEurekaLog)
private
{ Private declarations }
protected
FAdditionalExceptionNotify: TExceptionNotify;
procedure EurekaLogExceptionNotify(
EurekaExceptionRecord: TEurekaExceptionRecord; var Handled: Boolean);
function GetValue(strings : TStringList; key : string) : string;
public
constructor Create(AOwner: TComponent); override;

//I hide the parent class's OnExceptionNotify with an OnExceptionNotify
//of my own. This allows client app to handle this event without
//overriding the behavior I have put into the parent class's
//OnExceptionNotify below
published
property OnExceptionNotify: TExceptionNotify
read FAdditionalExceptionNotify write FAdditionalExceptionNotify;
end;


procedure Register;

implementation

uses MyErrorDialogUnit;

constructor TMyEurekaLog.Create(AOwner: TComponent);
begin
inherited Create(aOwner);
inherited OnExceptionNotify := EurekaLogExceptionNotify;
end;


procedure TMyEurekaLog.EurekaLogExceptionNotify(
EurekaExceptionRecord: TEurekaExceptionRecord; var Handled: Boolean);
var
ErrorDialog: TErrorDialog;
begin
handled := false;

//I usually use this in my client applications to provide a way for the
//application, modeled as a state machine, to set it's state to "error"
//it usually just leaves handled := false and lets the default handling
//below occur
if (Assigned(FAdditionalExceptionNotify)) then begin
FAdditionalExceptionNotify(EurekaExceptionRecord, Handled);
if (handled) then exit;
end;

ErrorDialog := TErrorDialog.Create(self);
try
//you get the point...
//I go on to show this custom dialog and use the
//EurekaExceptionRecord
//to get the stack and debug info I want. My dialog provides display and
//buttons and such as I like it
finally
FreeAndNil(ErrorDialog);
end;
end;

[admin]

Thank you very much.
I'll study it in the next fews day! :-)