Logging

  • 27 Jan

    LimagitoX File Mover goes mad(Except)

    Dear Users,

    Regarding version 2018.1.27.0

    We don’t write bugs .. I mean not on purpose. We’ve decided to add an exception handler from an external company called madExcept (madshi.net). This will help us locating bugs if they do occur. In case of an unhandled exception, our application or service wil log this in a ‘.mbr’ file ([m]adExcept [b]ug [r]eport). These mbr files will be written to the log subdirectory of our file mover settings directory.

    Possible files, we hope you won’t find any 🙂

    – LimagitoXA.mbr (Application)
    – LimagitoXC.mbr (Config Tool)
    – LimagitoXR.mbr (Remote Tool)
    – LimagitoXS.mbr (Service)
    – LimagitoXW.mbr (Web Remote Tool)

    Would be really helpful if you could send them to us.

    Regards,
    Limagito Team

    By Limagito-Team Logging ,
  • 13 Dec

    Event Log Monitoring

    Event Log Monitoring

    A while ago we received the following questions  from one of our users:

    My name is .. from the .. GmbH in Germany. I have two questions about your program (LimagitoX):

    1. Is it possible to Change the Event-ID at the Event Viewer? We want to monitor this Event with our Monitoring System. Our Idea is when an Event comes in with “On Success” it should be have another Event-ID as “On Error”.

    2. Our Second question / problem we get following Event Description:

    The description for Event ID 0 from source LimagitoX.exe cannot be found. Either the component that raises this event is not installed on your
    local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another
    computer, the display information had to be saved with the event.

    Is it possible to change this description or is this an mistake from your program? (the red labeled text)

    Thanks for your help!

    So we did what he asked and the result is available starting from version v11.12.12.0.

    EventLog

    We’ve added the following Id’s and Categories to make it much more suited when using external monitoring tools.

    Event Id’s:

    • IdDoNotUse = 0;
    • IdWINGET = 1;
    • IdWINPUT = 2;
    • IdWINBAK = 3;
    • IdFTPGET = 6;
    • IdFTPPUT = 7;
    • IdSFTPGET = 11;
    • IdSFTPPUT = 12;
    • IdPOP3GET = 16;
    • IdHTTPGET = 21;
    • IdIMAP4GET = 26;
    • IdAWSS3GET = 31;
    • IdAWSS3PUT = 32;
    • IdSMTPPUT = 37;
    • IdPSCPUT = 42;
    • IdZIPPUT = 47;
    • IdDELETE = 55;
    • IdOnCommand = 94;
    • IdOnDestination = 95;
    • IdOnDestinations = 96;
    • IdSRCTHREAD = 98;
    • IdDSTTHREAD = 99;

    Event Categories:

    • CatDoNotUse = 0;
    • CatOnSuccess = 1;
    • CatOnError = 2;
    • CatOnBkpSuccess = 3;
    • CatOnBkpError = 4;
    • CatOnVrfSuccess = 5;
    • CatOnVrfError = 6;
    • CatOnFileInUse = 7;
    • CatOnNoFile = 8;
    • CatOnRuleBegin = 9;
    • CatOnRuleEnd = 10;
    • CatOnPscSuccess = 11;
    • CatOnPscError = 12;

    We also had to add an extra dll and a registry entry to get rid of the red labeled text. The installer will handle this for you.

    Best Regards,

    Limagito Team

    By Limagito-Team Logging ,
  • 10 Apr

    Central Database Logging (MSSQL) option (v10.4.10.0)

    Centralize your logging into a MSSQL database. Just add your MSSQL server name, database name, username and password. LimagitoX will automatically create a logging table. You can find this option in the Moving Rule menu. Select Logging  and check the Datbase Log Tab.

SEARCH