If running Xwall and ESAT on the same machine:

Double-check the path where your messages are stored.  Xwall could be set up so the messages are stored in C:XWalllogshist-in.  ESAT Reporter could be set up so that it is pointing to C:XWallhist-in.  Miss matched directories will not work.

If running via networked machines, check:

What account do you have ESAT operating under? It is highly likely that the account ESATAgent is running under is "Local System". This means that a mapped drive (or even a UNC path) will not work as that account does not have rights to network resources. To continue running in this type configuration, you would need to:
    1) Create a Domain User account (say "ESATAgentServiceAccount")
    2) On the system running ESAT do the following:
        a. Grant "mydomainESATAgentServiceAccount" Full control to the ESAT installation folder.
        b. In Services, change the Log On for the ESATAgent service to the "mydomainESATAgentServiceAccount" user. You should get a             statement that says something about granting this account rights to login as a service - that is needed.
        c. Set the XWallHistoryPath in ESATAdmin to the UNC path to the share that your X: drive had been pointing to. Something like:
            myxwallserverhistorysharelogsHIST-IN

    3) On the XWall server:
        a. Verify/Add the "mydomainESATAgentServiceAccount" has "Access through the network" rights in the Local Security Policy.
        b. Add this user account to the share you created (what X: was mapped to...) with Read rights.
        c. Give this account Read rights to the HIST-IN folder structure.