Difference between revisions of "Running the Scheduling Service in non-Service mode"

Line 4: Line 4:
 
  C:\Inetpub\wwwroot\XLCubedWeb\Scheduler\XLCubed.Scheduling.Service.exe /RUNPENDING
 
  C:\Inetpub\wwwroot\XLCubedWeb\Scheduler\XLCubed.Scheduling.Service.exe /RUNPENDING
  
Note that as with the standard Scheduling Service, the user running the schedules must have sufficient permissions to all the relevant folders, databases and cubes.
+
Note that as with the standard Scheduling Service, the user running the schedules must have sufficient permissions to all the relevant folders, databases and cubes. See [[SQL Repository#Scheduling]] for details.
  
 
==See Also==
 
==See Also==

Revision as of 09:36, 27 April 2016

The XLCubed Scheduling Service can be run in non-service mode if necessary when using the SQL Repository. This can be helpful when you need to run schedules for multiple websites, or where it better suits your infrastructure. The schedules can be sent manually or timed using Windows Task Scheduler or similar.

After setting up the scheduler in the normal way (see this page for more instructions), you will need to run the executable with a special command-line parameter in order to check for new schedules to run:

C:\Inetpub\wwwroot\XLCubedWeb\Scheduler\XLCubed.Scheduling.Service.exe /RUNPENDING

Note that as with the standard Scheduling Service, the user running the schedules must have sufficient permissions to all the relevant folders, databases and cubes. See SQL Repository#Scheduling for details.

See Also