I am using FireDac Monitor which stops after a short while with a message "EOF found".

-
I am using FireDac Monitor which stops after a short while with a message "EOF found".
Has anyone encountered that before and maybe solved that problem?

Comments

  1. Lars FosdalJanuary 13, 2015 at 10:00 AM

    I've briefly tried to get it to work myself, but never actually got it working at all. Never did have time to delve deep.  Any pointers, tricks and tips would be very welcome.

    ReplyDelete
  2. Oliver FunckeJanuary 14, 2015 at 3:35 AM

    The principle is simple: You just need to create a TFDMoniRemoteClientLink and set its Tracing property to True. Then, start FDMonitor.exe before starting your app.

    ReplyDelete
  3. Lars FosdalJanuary 14, 2015 at 4:38 AM

    Which is basically what I've tried. Never got anything after setting Tracing to true, which yields a single line in the Monitor app.

    *** Client [P: \.exe] activated

    I can run queries and stored procedures - but nothing shows up in the monitor.

    ReplyDelete
  4. Lars FosdalJanuary 14, 2015 at 4:39 AM

    Can it be related to instantiating everything at runtime and not having the various FireDAC components available in design mode?

    ReplyDelete
  5. Lars FosdalJanuary 14, 2015 at 5:24 AM

    Doh... I just found out that I had completely misread the documentation on Monitoring.

    Doc says "Add the MonitorBy=Xxx connection definition parameter. "

    So I did
    FConnection.Params.Values['MonitoryBy'] := 'mbRemote';

    While you should do
    FConnection.Params.MonitorBy := mbRemote;
    which I think is equal to
    FConnection.Params.Values['MonitoryBy'] := 'Remote';

    ReplyDelete

Post a Comment