Skip to main content

Frequently Asked Questions

Top FAQs

Below we list our most frequently asked questions. Please contact our Customer Support Department for further assistance beyond what is explained in these answers.

In Scheduler, I have saved the repository selection file to the proper installation path. Why am I still prompted for this file when I log in?

In Windows 7 and Windows 10, you must have the proper access to save the repositoryselection.xml file to the install path. If you do not have the proper authority to do this, you can do one of the following:

  1. Run Scheduler as an Administrator in order to be able to select and save the repositoryselection.xml file in the Hubble install path. (You can log on as an administrator from the Start Menu shortcut by right-clicking on Scheduler and choosing ‘Run as administrator’. You can also do this by navigating to the install path, right-clicking on the SchedulerAdministration Application File and choosing ‘Run as administrator’.)

  2. Run Windows Explorer as an administrator and copy and paste the repositoryselection.xml file from your own documents to the Hubble install path. (You can log on as an administrator from the Start Menu shortcut by right-clicking on Windows Explorer and choosing ‘Run as administrator’.)

    Why am I getting a Windows error saying that access is denied when I try to save the repository selection file in the Hubble installation path?

If you are in Windows 7 and Windows 10 and User Account Control (UAC) is enabled for Hubble, the RepositorySelection.xml file displaying in the Hubble install path is only a pointer and acts as a shortcut. This shortcut file will only work for you, not other users on the PC, since it is not the actual file. If you want to overwrite it, you can follow these instructions:

  1. In the Task Bar, click on the button for Compatibility Files. (This takes you to where the actual file is stored.)

  2. Overwrite the file here and it will automatically update the pointer file in the install path.

If you are installing on a shared server, such as a Citrix server, you need to ‘Run as administrator’ for Administrator so that the repository selection.xml file is saved in the directory and available for all users logging in. (To run Administrator as an administrator, navigate to the install path, right-click on the Administration Application File, and choose ‘Run as administrator’.)

Please contact our Customer Support Department for more assistance with this if needed.

I am trying to save the output of a scheduled report in a folder on a shared drive but it is not working. Is there some requirement that I am missing? I need to know whether you require a UNC path, drive, URL, etc.

There is a requirement that the user who is starting the Scheduler service (this is the “Log on as user”) has write permissions to that network path.

The results on my report are not what I expect. How can I verify what they should be?

Verify the following information that is defined in the scheduled task:

In the Inquiry Settings tab:

  • Inquiry

  • Profile

    In the Run As tab:

  • Run As User

  • Run As Role

Next log into Hubble as this user, using the same role and profile, and run the inquiry. The results in the automatically-generated report should be the same as these results since the ERP credentials of the user/role/profile combination are used. There may be a difference in the inquiry results based on the date/time that the report was automatically generated as the data in the ERP system may have changed.

Can I send output from a Scheduled Task to an email distribution group?

Yes. All that is needed is to key in the Distribution Group Name and email address in the Manage Recipient Users dialog:


If a recipient of a Scheduled Task is listed in more than one distribution group or listed individually as well as a member of an email distribution group – Microsoft Exchange may strip out the extra emails to the recipient therefore allowing only one email per Scheduled Task to be received.

Does a user have to be a true Hubble Administrator (in the Administrator group in the Administrator Application) in order to be a Scheduler Administrator?

A Scheduler Administrator does not need to be a true Hubble Administrator. In order to do all the setup and tasks required in Scheduler, the Scheduler Administrator must have the Administration Capability for Users and Groups (in order to manage Recipient Users) as well as be assigned the SCH license. The only other permission that may need to be set is that for a Recipient User that was added to the Recipient Users group by a true Hubble Administrator. In that scenario, the Scheduler Administrator would need to be granted Update permission to the Recipient User that was already established if any changes need to be made, such as an email address of the Recipient User.

We will be installing Scheduler on a server as well as on multiple client PCs so that those users can individually create and manage the scheduled tasks, but the tasks will actually run on the server. What does the installation look like to achieve this?

Installation on the server:

  1. Hubble must be installed prior to installing Scheduler.

  2. Install Scheduler in the same install path as Hubble.

  3. Activate the Scheduler Service in Windows Services by either restarting the server or by activating the service with the standard right-click method.

Installation on the client PC:

  1. Hubble must be installed prior to installing Scheduler.

  2. Install Scheduler in the same install path as Hubble.

  3. Deactivate the service component on the client PC since it is already active on the server and only 1 Scheduler service should be active per Object Repository:

    1. Go to Windows Services.

    2. Right-click on Hubble Scheduler.

    3. Choose Properties.

    4. Change the Startup Type to Disabled.

      What date and time will my scheduled task use - my local date and time or the date and time where the Service is running on the server?

      The date and time should be defined in the local time zone - no adjustment should be made to shift the time to 'server time'. The stored date and time will make the adjustment to store the time in Universal Time and the service will make an adjustment to the server time, if required. While the stored date and time is in Universal Time (Greenwich Mean Time), the displayed date and time for the scheduled tasks is always in the local time zone.

      What date and time format is used on a report that is output to Microsoft Excel?

      Scheduler takes its date and number format from the machine it is running on, and more specifically, from the Windows account that the Scheduler Service runs under. By default, this the “Local System” account, respecting the regional settings set in Windows.

      In Scheduled Tasks under the Email Notification Tab, are the tags for Run Date and Run Time coming from the server the Service is installed on?

      Yes, since it is the service that resides on the server that picks up the Scheduled Task, the Run Date and Run Time are going to display as the Server Run Date and Time.

My scheduled report is not running. Where can I go to troubleshoot why this is happening?

  1. Verify that you have set the SMTP Settings in Scheduler.

  2. Verify that you have started Scheduler in Windows Services. For more information, see page 10.

  3. Verify that the RepositorySelection.xml file is located in the install location path and viewable for the administrator starting the Windows Services. For more information, see page 10.

  4. Verify the schedule information in the Scheduled Task (First Run, Recurrence and End Date, all of which are set in the Schedule Tab). If you are not using military time, be sure the AM/PM is set appropriately.

  5. Go to Windows Event Viewer on page 24 to see any errors that may have been generated.

    Will the output PDF and Excel documents from the Scheduled task be saved anywhere?

For each scheduled task, you can designate that the output be saved to a designated folder if desired. Within the Inquiry Settings (when creating or editing a scheduled task), you must designate that you want to save the output to a folder and then designate the folder path.

Under the Administrators Group there is a user, “SchedulerService”. What is this user used for?

The SchedulerService user is used by the Scheduler Service to log into the repository when looking for a scheduled task. It is created automatically by the Scheduler Service the first time it connects to the repository. Its purpose is for the Scheduler Services’ activities in the repository to be logged against a distinct user name. No user can log in as SchedulerService – it is an internal account like ‘System’. This user cannot be deleted, renamed or moved. You can edit it, but its properties, including the password, are irrelevant and not used.

Can Scheduler be deployed using Click Once Technology?

You cannot deploy Scheduler using Click Once Technology. The Scheduler Service must be installed on the server of choice and the Scheduler Application must be installed as a fat client for users who intend to schedule tasks.

Can reports created in Designer Express (DX) be scheduled using Scheduler?

Yes, reports that are created in Designer Express can be run automatically using Scheduler.

  • Scheduler Admin/User: The person creating the task in Scheduler needs an SCH license but does not need any other license unless they are going to be set as the Run As user.

  • Run As User: If this user is a Power user, then they would need a DX license as well as the appropriate module license in order to run the report. If this user is an Viewer user, then they would only need a CON license and can be set up as a Run-As user.

Is there a way to determine which machine my Scheduler Service is running on?

As long as the Scheduler service has been running jobs, then it will also have been writing entries in the Hubble log.

Query the log using View History in Administrator, filter on User = “SchedulerService”, run the query and look in the ‘Machine’ column. That should tell you the name of the computer running the Scheduler service.

Can I use report bursting functionality in the output from Scheduler?

Report bursting, which is the ability to create separate documents based on filter criteria, is honored when outputting a report using Scheduler. It is important to note that when breaking into multiple files either in Excel or PDF, the File Name Pattern as set in Scheduler takes precedence over the settings in Excel Options or PDF Options.

The File Name Pattern as set for the scheduled task is what is used for the produced files:

In Excel Options, you set the option to Break into worksheets. The Worksheet Name Pattern at the bottom of this dialog will not be used because the File Name Pattern that is set in the scheduled task is used:

If printing to PDF, in PDF Options, you can set the option to Break into files. The File Name Pattern at the bottom of this dialog will not be used because the File Name Pattern that is set in the scheduled task is used:

Can I run multiple instances of Scheduler?

There can only be one instance of Scheduler Service set up per repository. If you have multiple repositories, say for example if one is pointing to a production environment and the other to a development environment, then you can set up separate Scheduler Services. You must ensure prior to setting up multiple services that there is a separate repository set up for the new service instance.

Great caution, however, must be taken when using multiple instances of Scheduler. Because it can create confusion when duplicate copies of scheduled reports are being run, we recommend – other than the case of testing a new version – that you only use a single instance of Scheduler.

I have multiple repositories and multiple Scheduler Services set up, however it is not working. What should I check?

Verify that the repositories are not using the same RepositorySelection.xml file.