Hi, all.

We have a client who wants to use FX to allow his management people to check their budget balances & other reports using FX but for some reason the FX data gets stale even though it is supposed to refresh nightly.

The main Adagio GL data is stored on a Linux based file server. Task Scheduler runs on a Windows 7 system with the file shares from the Linux server mapped to drive letters. Task Scheduler runs a batch file that runs FX.exe repeatedly for a bunch of data sets with the command line options for user, password, database path, etc. and each FX target path has an AFWININI.dat file with the appropriate options for each retrieval. The batch file makes sure that the file shares are indeed mapped to the drive letter before starting the FX jobs. If the batch file is just run by double clicking it the sequence of retrieves goes off without any errors, it just churns one at a time through Admin, Education, Social, etc. The batch file contains lines like echo "Admin start" >> fxretr.txt and echo "Admin end" >> fxretr.txt so I can see how it progressed and it appears to get through all the data sets.

The Task Scheduler window shows that the batch file ran from midnight to 12:35 and had an exit status of 0x0 but the FX data is many days out of sync with the GL. eg: on Friday Jan 6th the FX numbers and the GL numbers matched exactly. By Jan 10th the FX numbers were still the same as they were on the 6th and the GL was different because two days of new work had been done to it.

The client also has a trial version of Adagio Console set to enforce a maintenance window from 11:30pm to 4am every night so that if some employee leaves GL open they will get kicked off so the FX retrieve can run.

Does Adagio Console need to be running on one of the Windows clients to actually enforce that maintenance window?

Is there anything else I should know about getting a Task Scheduler job to keep the FX data current?

Thanks for any tips.

Hi icbm,

Do you know if anything changed on Jan 6th? What version/release of FX?

I've come across a couple of reported errors with the Auto-retrieve process in FX 9.2A that have yet to be fixed. The specific details were somewhat confusing as I read them, but was related to using the ReplaceDepartment=1 line in the auto-retreive settings.

If the auto-retrieval is being done with the edits to AFWININI and launching FX with the /r parameter, then this has nothing to do with Adagio Console.

If the batch file runs fine when run manually under a logged-in user, test the scheduled task by seeing if turning the option to only run when the associated user is logged in on changes anything. Log in as that user and force it to start, see what happens.

Mapped drive references may not work without a logged in user, so if you find that the scheduled task launches with that option changed you have two choices:
- try and purge all mapped drive references from any part of the system that will be in use during FX retrievals, replacing them with UNC references
- keep the user logged in to run the task

Hi,

We have a number of sites running the FX auto retrieve. You are probably using a sample batch file that we originally created and shared, to enable this very cool reporting function in FX that Softrak (Michael), Dakota (Bob), and myself collaborated on to create.

We do not have any sites running in the exact configuration you have described, with data on a Linux box and with a client windows scheduler running the task scheduler. I can't tell but it sounds like you have peer to peer server (Windows 7), running the Adagio programs with data on a server Linux box.

All of our sites are running the unattended processing on the file server where the data and programs reside (together). This is a best practice if you have the choice or option.

We did have some issues that we discovered with various task schedulers where the mapping got lost during running of the batch files. Not sure if this is an issue here. I am not familiar with the 0x0 exit status, but I would start to troubleshoot with running the batch file by manually launching from within the scheduler to see whether the batch file will execute and update properly. That is your starting point.

Warren and I have tested out the mapped driver references so again his notes above would suffice.

Also check to see that you do not have any overlapped batch files (in the scheduler) that start before the other batch file is completed. Even though FX is read only, you can get into record locking that drops out of the batch file without doing updates.

Most recently, we have determined and tested our premise being that using UNC path mappings on the RDP server is not the fastest way to use Adagio. By using SUBST command on the RDP server and removing all references to UNC paths, we can cut the runtimes of the scripts by at least 60%. (and we are now testing on other Adagio modules for performance benchmarks).

If you are still have a problem, please give us a call.

Best,
Brian