How can I troubleshoot my Donor Central Upload if I am a Self-Hosted Customer?

My Donor Central upload process is not taking place, how can I figure out why it is not working?
There are two ways to upload data into Donor Central from FIMS; Run the process manually from FIMS or Set up a scheduled task on the server to run daily. The steps below are for self-hosted customers. If you are hosted by Blackbaud you can reach out to support who will contact our hosting department on your behalf.

In order to find out why the data is not synching, we will need to find out which piece is not working or if both are not working.

1. Check to see if your upload ran successfully by logging into Donor Central and checking the status and the last date and time when data was uploaded from FIMS into Donor Central.
  • In DC NXT this is located in Control Panel > Monitoring. Note, in DC NXT you will not get an email as to whether or not the upload was successful.
  • In older versions of Donor Central this is located in the Admin Portal.
If you find that the DC upload process did not take place when the scheduled task ran on the server the last time it was supposed to run, you can do the following manual task to get the data uploaded to Donor Central until you resolve the issue with the scheduled task. Note that the manual upload does not use the 'eAdv-export.bat' file like the scheduled task on the server does.

2. How to run a manual sync from FIMS to Donor Central. Before proceeding make sure that the FIMS user has the DC download directory set in User Preferences\DonorCentral_Download_Directory. It should be N:\found\eadvisor:
  • Run a manual upload by going to Tools\System Utilities\Donor Central\Donor Central Export
  • Check the boxes for Export Data and Upload to Donor Central:
  • After the process completes, check Donor Central per the instructions above in step 1 to see if the upload took place, if it did not check the following locations on the server to see if there is data:
           npo\found\eAdvisor\History-(f you have DCNXT there may be an additional folder to look in, for example, \npo\found\eadvisor\history\DCnxt)  This is the first part of the upload process. These files are the actual data that is exported out of FIMS, these should have the time and date stamp from when you ran the process. If they do not, that means that the data export out of FIMS never took place.

           npo\found\eAdvisor\FTP- This is the 2nd part of the upload processThis is the FTP log that will document whether or not the files were actually uploaded into Donor Central. Look for the latest log file and open it to see
           the results. It will be named in this format: DC_Transfer_2010_11_29.log where the date is the date where the FTP process ran. If the task was successful it will say DC Transfer Complete at the end of the log and there
           should be no errors. Note that it usually takes about 90 minutes for data to be seen on the Donor Central site.

3. To resolve the issue with the scheduled task not uploading to Donor Central, do the following in Task Scheduler on the server: Note that the Windows task is NOT setup from within FIMS:
  • Check the Windows account that is being used to run the scheduled task. Did the password change? Does the Windows account have the proper permissions to run the task? What happens if you try another Windows account?
  • Check the history of the scheduled task on the server and see if it ran successfully or if there were errors when it ran. You can also run the scheduled task on demand and see if it produces results as noted above in the History and FTP folders.
  • Edit the bat file located in \npo\found\eAdvisor named 'eAdv-export.bat' (which is what the scheduled Donor Central Upload task uses) and make sure that there is no back slash before gui. It should be -p gui, not -p \gui as below:
           %dlc%\bin\prowin32.exe -ininame %FIMSini% -p gui\eadvisor\Export.p -assemblies ..\assemblies
  • Check the found.lg file located in \found\dbfiles\found.lg to see if it connected to the database or if it did connect but no user logged in then it disconnected.
  • Look at System Users Report under Tools | System Utilities | System Reports. See if the password for FIMSInternal has changed. You can reset the password for the FIMSInternal user by doing the following:
            From Tools | System Utilities | Run Procedure,  run gui\system\XAddCall.p

            After doing this try running the .bat file again and check the found.lg file to see if the userid is FIMSInternal.
  • Try running the .bat file from the command prompt to see if it will run
4. . If the manual sync from Donor Central will not work, then this is indicative of system settings beings wrong. Review the following to be sure correct and also reach out to support and create a case if you cannot manually sync or sync via the Windows scheduled task on the server and this article does not resolve the issue:
  • Verify that you are using the most current version of FIMS.
  • See if there are any custom files in custom\gui\eadvisor files



Was this article helpful?

Thanks for your feedback! Did this solve your issue?

Comments (optional):

Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):

Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.