Summary

When the Arcana Scheduler passes environment variables to scheduled programs, variables that contain a reference to the UserProfile variable are expanded using the path to the Default User profile path, rather than the profile of the user under whose account the program is being run.

For example, the TEMP environment variable is often defined (in the Windows environment variable editor) as:

%USERPROFILE%\Local Settings\Temp

When a program is run, "%USERPROFILE%" should be replaced by the path of the user's profile. For example, if the program is run under Claire's account, the TEMP environment variable would be:

c:\documents and settings\claire\Local Settings\Temp

However, the Arcana Scheduler expands the USERPROFILE variable incorrectly, so that the TEMP environment variable ends up set to:

c:\documents and settings\Default User\Local Settings\Temp

This can cause problems with scheduled programs, especially when the variable ends up pointing to a non-existent path.

Status

This problem was resolved in 2.3.2 of the Arcana Scheduler. Please see the download page to download the current version of the software.