The scheduler service on [machinename] is running, but the Scheduler failed to initialize

When starting a Scheduler service, it is possible to receive the following:

"The scheduler service on [machinename] is running, but the Scheduler failed to initialize. Please check the Windows Event Log for details."

This message can occur when:

• You have recently switched databases but have not cycled the Scheduler service. If you change a database, you must restart the Software Pursuits Scheduler for SureSync service for the Scheduler to initialize on the new database. As a first step, restart the service and see if that resolves the issue.
• There is a permissions issue with the SureSync database security and the Scheduler is unable to read from the database.

If you’re encountering a permissions issue there are a number of potential areas to investigate. Databases have both their own security and SureSync has a layer of database security implemented within the program to control who has access to what items within SureSync.

Access Database

With an Access database, confirm the following:

• The user account the Scheduler is running under has Full Control NTFS file permissions to the .mdb file.
• The user account the Scheduler is running under has Full Control in SureSync’s database security. This can be checked by launching the SureSync user interface, clicking on each Group Folder and clicking on the Security tab. If the account the Scheduler is running is not listed there or does not have Full Control, grant the appropriate permissions and cycle the Scheduler service again. The default Group Folder name is Job Definitions. It’s possible to define multiple Group Folders so you should check each one if multiple Group Folders are defined.

SQL Database

With a SQL database, confirm the following:

• The user account the Scheduler is running under must have db_owner rights to the SureSync database. This can be confirmed in SQL Server Management Studio by expanding Security, expanding Logins and then right clicking on the user in question and selecting Properties. On the Window that is displayed, go to User Mapping. The SureSync database should have a check next to it. Click on the SureSync database and look at the "Database role membership for: [databasename]." The account should have db_owner checked.
• The user account the Scheduler is running under has Full Control in SureSync’s database security. This can be checked by launching the SureSync user interface, clicking on each Group Folder and clicking on the Security tab. If the account the Scheduler is running is not listed there or does not have Full Control, grant the appropriate permissions and cycle the Scheduler service again. The default Group Folder name is Job Definitions. It’s possible to define multiple Group Folders so you should check each one if multiple Group Folders are defined.

If the permissions appear appropriate and the error continues after cycling the Software Pursuits Scheduler for SureSync service then you should consult the Application Event Viewer for clues about what the issue might be and contact Software Pursuits technical support for assistance.