Contents x
    DonorCentral Upload Scheduled Task is not Producing Results when Run
    • 19 Apr 2023
    • Contributors
    • Print
    • Dark
      Light
    • PDF
    Contents

    DonorCentral Upload Scheduled Task is not Producing Results when Run

    • Updated on 19 Apr 2023
    • Contributors
    • Print
    • Dark
      Light
    • PDF
    Article summary

    When the DC Upload scheduled task runs, nothing happens, no files are exported out to the eAdvisor\History folder and no file is created in the eAdvisor\FTP folder. No error occurs on the scheduled task however, it runs and then finishes but does not actually do anything.

    Answer:
    To resolve complete the following:

    1. Make sure that the setup for Donor Central Uploads located in Tools\System Utilities\Donor Central\Setup Donor Central Upload contains the full paths to all files, not just a file or folder name. Note that your NPO folder may be on another drive other than C on the server.

    You will need to log into FIMS on the FIMS database server to do these steps.

    2. Check the bat file used for the scheduled task and be sure configured correctly:

    How do I set up the DonorCentral Upload as a Scheduled Task on my FIMS Database Server?

    3. Be sure that the system directory for DonorCentral in Tools > System Utilities > Donor Central > DonorCentral Options > System > Download_Directory has not been changed.
    • It should be typically set as c:\npo\found\eadvisor, changing the drive letter to what the drive and path is on your server.
    • The system setting is what the server uses for the scheduled DC upload task and should never be changed after it is set correctly unless you have a server move and the new server has a different path. 
    4. Check the fimsnt.ini file and be sure that the - S parameter port is configured correctly for the eAdvisor line, it needs to be the same as the port # for the live database. (see support for assistance with this setting).

    5. Find out if the FIMS internal password has been changed
    • The FIMS internal password is what the task uses to run and it does take a FIMS license
    • To find out if the password for that account was changed run the System Users Report in Tools > System Utilities > System Reports.
    • If the password was changed, you will need to reset it to be what it should be. Contact support to get those steps as needed.
    Was this article helpful?
    What's Next