In Telligent Evolution, tasks are queued in order to improve performance and scalability by reducing the load that could be caused by several initiating at the same time.
Telligent Community has a set of tasks that periodically run in the background and perform tasks that are not suited for running on every Web request. These tasks are configurable and are defined in two places. The tasks that should be run on every Web server are located in the tasks.config file of your Web folder. (See below.) The tasks that should be run on only one node are in the tasks.config file of your Tasks folder.
Installing Job Scheduler
In the Telligent Evolution package are several folders, including one named Tasks. The Tasks folder contains all the Job Scheduler files needed. This folder can be copied to any location desired, even to a separate server if the community size warrants.
Installing is as easy as running the install.bat file located in the folder. (Note: If you had Job Scheduler installed from a previous version of Telligent Evolution, you will need to uninstall it before installing this.)
Once installed, several files will need to be updated. These include connectionstrings.config, communityserver_override.config if you’re site uses one, and any other customizations made in the site’s Web folder. As a rule of thumb, any changes made to the Web folder should also be made in the Job Scheduler folder to ensure consistent operation.
Finally, the Job Scheduler must be started. Refer to this page for more information on starting and stopping the service. If any configuration files are changed while the service is running, the Job Scheduler will need to be restarted for the changes to take effect.
Installing multiple Job Schedulers
By default, the service name is “Telligent Job Scheduler Service.” Windows requires that service names be unique on the system. If multiple Job Schedulers are needed on one machine, the name will have to be changed for other Job Schedulers:
- Copy the Tasks folder to a second location. Give the copied folder a name that makes it easy to identify.
- Update the configuration files as necessary.
- Open install.bat file in Notepad.
- Add /name=”Name For Second Service” after --install.
- The contents will look similar to this: Telligent.JobScheduler.Service.exe --install /name="Name For Second Service" %*
- Do the same for uninstall.bat, except instead of --install it will have --uninstall:
- Telligent.JobScheduler.Service.exe --uninstall /name="Name For Second Service" %*
- Run install.bat to install the second service.
This can be done multiple times to add any number of Job Schedulers.
Troubleshooting Job Scheduler
Following are some problem scenarios and their solutions.
Error: Windows could not start the Telligent Job Scheduler service on Local Computer. Error 1067: The process terminated unexpectedly.
In the Tasks folder, there should be a file named errors.log. All errors are logged to this file. Open it and find the last error that occurred (it will be at the bottom).
Exception:  ERROR Telligent.JobScheduler.JobsManager [(null)] - System.Configuration.ConfigurationErrorsException: There was an error creating the cron scheduler. Ensure configuration values are set correctly. Check the inner exception for more details. ---> Telligent.Evolution.Components.CSException: Unable to open connection to data provider. ---> System.Data.SqlClient.SqlException: Cannot open database "TelligentCommunity" requested by the login. The login failed.
Cause: The service was unable to connect to the database.
Solution: Check your connectionstrings.config file.
Error: The Telligent Job Scheduler service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.
Cause: This is most commonly caused by the Telligent Community zip you received being blocked. This is done by some browsers as a protective measure against viruses.
- To unblock the files, locate the zip of Telligent Community you received.
- Right-click it and go to Properties.
- At the bottom right of the Properties window should be an Unblock button.
- Click that and then click OK.
- Follow the install steps again.
- When the service is started, it should no longer immediately stop.