The DataNow service does not start when Environment Manager is disabled

Version 1

    Verified Product Versions

    Environment Manager 10.0Environment Manager 8.6File Director 3.6File Director 3.5File Director 3.0File Director 2.0File Director 4.0File Director 4.1


    On a machine where Environment Manager 8.6 or later is installed alongside DataNow, you may notice that if the "AppSense User Virtualization Service" has a startup type of "disabled", then DataNow may fail to start with the following error:

    "There was a problem starting the DataNow application
    The DataNow service is not running. (1722)"


    Environment Manager 8.6 saw the introduction of a number of DataNow actions which are applicable to the 'computer startup' node. For these actions to be successful, they must complete before the DataNow service has started.

    To ensure these actions are successful, if both the Environment Manager 8.6 agent and DataNow are installed on the same endpoint, the DataNow service will be set to a startup type of 'manual', and will be started by Environment Manager once the computer startup trigger has completed.

    If you require the "AppSense User Virtualization Service" to be disabled, but want DataNow to continue functioning, you can simply change the startup type of the "AppSense DataNow" service to "automatic".