Scheduler error messages
The following errors are reported in the Scheduler log if problems with the configuration of connections or errors in tasks or triggers occur. Each error is explained together with possible corrective action.
Many of the errors are caused by inadequate permissions on files, folders or within SQL Server. For details of the minimum permissions that are required for access to all the files and folders that are required by the Scheduler Service, see Setting up a Domain Account for the Scheduler Service.
Service errors
Could not start the iBase Scheduler Service on Local Computer.Error 1053: The service did not respond to the start control request in a timely fashion.
This error message is displayed after a short interval when an attempt is made to manually start the Scheduler service by using the Windows Services application.
Refer to the next error message if this message is displayed immediately after an attempt is made to start the service. However, when there is a delay of thirty seconds or more between attempting to start the service and the error message appearing then the possible causes for the error are as follows:
| Configuration | Possible Cause | Solution |
| N/A | The database file has the 'Read Only' attribute enabled. | Disable the 'Read Only' attribute on the database file. |
| The Scheduler database is on either the local machine or a remote machine and is accessed through a folder share by using a UNC path. The file system in use is either NTFS or FAT. | The folder share permissions are set to 'Read' for the Scheduler Service account. | Alter the folder share permissions to grant the Scheduler service account at least 'Change' permissions on the folders and files available through the share. |
| The Scheduler database resides on the local machine or a remote machine. The file system in use is NTFS. | The folder or file security permissions prevent write access to the database. | Alter the folder and file security permissions to grant the Scheduler service account at least the minimum permissions required for the Scheduler database. |
| The Scheduler service is configured to execute under the context of the local system account. The database is on a remote machine. | The local system account uses the 'Anonymous' login when is accesses files on remote machines. |
Change the Scheduler service account context to a domain account with the required permissions on the database folder and file. Or Grant the 'Everyone' group the required permissions on the database folder and file. |
| The Scheduler service is configured to run under the context of a local machine account. The database is on the local machine and is accessed with a local path. The file system in use is NTFS. | The local machine account must have permission to access the database file. | Grant the local machine account the required permissions to the database folder and file. |
| The Scheduler service is configured to run under the context of a local machine account and the database is on a remote machine. The file system in use is NTFS or FAT. | A local machine account is unable to access files across the network. | Configure the Scheduler service account to run under the context of either the Local System account, or a domain account. |
| The Scheduler service is configured to run under the context of the local system account and the database is on the local machine. | The local system account is a member of the Administrators local group. The Administrators local group does not have permission to access the database file. | Grant the Administrators local group the required permissions on the database folder and file. |
Could not start the iBase Scheduler Service on Local Computer.
Error 1053: The service did not respond to the start control request in a timely fashion.
This error message is displayed immediately after an attempt is made to manually start the Scheduler service by using the Windows Services application.
Refer to the previous error message if this error message is displayed thirty seconds or more after an attempt is made to start the service. However, when the error message is displayed immediately after an attempt to start the service the possible causes for this error are as follows:
| Configuration | Possible Cause | Solution |
| N/A | The Scheduler database is moved. | Open the Scheduler Configuration dialog and choose the new location of the Scheduler database when prompted. After the location of the database is verified and the Scheduler Configuration utility starts, try starting the service again from the Services control pane. |
| The Scheduler service is configured to run under the context of a local machine account. The database is on the local machine and is accessed by a local path. The file system in use is NTFS. | The local machine account must have permission to access the database file. | Grant the local machine account the required permissions to the database directory and file. |
| The Scheduler service is configured to run under the context of a local machine account and the database is on a remote machine. The file system in use is NTFS or FAT. | A local machine account is unable to access files across the network. | Configure the Scheduler service account to execute under the context of either the Local System account, or a domain account. |
| The Scheduler service is configured to run under the context of the local system account and the database is on the local machine. | The local system account is a member of the Administrators local group. The Administrators local group does not have permission to access the database file. | Grant the Administrators local group the required permissions on the database directory and file. |
Scheduler Configuration utility errors
The Microsoft Jet database engine cannot open the file '< scheduler_database_file >.' It is already opened exclusively by another user, or you need permission to view its data.This error is displayed when the configuration application is started.
| Configuration | Possible Cause | Solution |
| The Scheduler database is on either the local machine or a remote machine. The file system in use is NTFS. | The user that is attempting to access the database does not have sufficient permissions to the Scheduler database folder or file. | Grant the user the required permissions to the Scheduler database folder and file. |
Unable to write to the database – you may not have permission.
This error is displayed when an attempt is made to save or edit a connection, task, or trigger.
| Configuration | Possible Cause | Solution |
| The Scheduler database is on the local machine or a remote machine and is accessed through a folder share by using a UNC path. The file system in use is either NTFS or FAT. | The user that is attempting to access the Scheduler database has sufficient rights to read from the database, but not to modify its contents. The folder share permissions for the user are set to ‘Read’ for the user. | Alter the folder share permissions to grant the user ‘Change’ permissions on the folders and files available through the share. |
| The Scheduler database is on the local machine or a remote machine. The type of file system in use is NTFS. | The user that is attempting to access the Scheduler database has sufficient rights to read from the database, but not to modify its contents. The folder or file security permissions prevent write access to the database for the user. | Alter the folder and file security permissions to grant the user at least the minimum permissions required for the Scheduler database. |
Unable to delete the connection/task/trigger – you may not have permission.
This error is displayed when an attempt is made to delete a connection, task, or trigger. Refer to the previous error for possible solutions.
Could not connect to the iBase database for the ‘< connection_name >’ connection.
The databaseis moved or deleted, or your connection details are incorrect.
This error message is displayed when either the Scheduler Configuration dialog is started, or an entry is selected from the list of connections.
| Configuration | Possible Cause | Solution |
| The iBase connection and security files is on the local machine or a remote machine and are accessed through a folder share by using a UNC path. The file system in use is either NTFS or FAT. | The user that is attempting to access the iBase database does not have permission to access this share, or they do not have permission to change the files and folders available through the share. | Ensure the user that is accessing the iBase database has at least ‘Change’ permission on the folder share. |
| The iBase connection and security files reside on a local machine or remote machine. The file system in use is NTFS. | The folder or file security permissions are
preventing write access to the iBase security file for this user. |
Alter the folder and file security permissions to grant the user at least the minimum permissions required for the iBase database and security file. |
| The iBase security file has the ‘Read Only’ attribute enabled. | Disable the ‘Read Only’ attribute on the iBase security file. | |
| N/A | The iBase security file has the ‘Read Only’ attribute enabled. | Disable the ‘Read Only’ attribute on the iBase security file. |
| The iBase security file is on a remote machine and is accessed through a folder share by using a UNC path. The file system in use is NTFS or FAT. | The folder share permissions prevent write access to the security file for the Scheduler service account. | Alter the folder share permissions to grant the Scheduler service account ‘Change’ permissions on the folders and files available through the share. |
| The iBase security file is on the local machine or a remote machine. The file system in use is NTFS. | The folder or file security permissions prevent write access to the security file for the Scheduler service account. | Alter the folder and file security permissions to grant the Scheduler service account at least the minimum permissions required for the iBase security file. |
Log errors
The file < file_name> does not exist or there are insufficient permissions on directory to read the file.The user successfully created a file trigger through the Scheduler Configuration dialog, but the service immediately logs the error in the Scheduler log.
| Configuration | Possible Cause | Solution |
| The trigger file is on the
same machine as the Scheduler Configuration utility and is accessed through a local path. The file
system in use is either NTFS or FAT. The Scheduler service is on a remote machine. |
The Scheduler service is looking for the file on the machine that the service is running on. This file does not exist on this machine. | Create a folder share on the Scheduler Configuration utility machine and reference the trigger file through this share. |
| The trigger file is on either the local machine or
a remote machine and is accessed through a folder share by using a UNC path. The file system in use
is either NTFS or FAT. The Scheduler service is on either the local machine or the remote machine. |
The Scheduler service account does not have permission to view the trigger file. | Ensure that the Scheduler service account has at least the minimum folder and file security permissions required for the trigger file. |
| The Scheduler service account does not have access to the folder share. | Add the Scheduler service account to the list of authorized users on the folder share. The account must have a minimum of 'Read' permissions on the files and folders available through the share. |
Login failed for user '< windows_user_name>'
The Scheduler service creates an entry in the log when a batch import or export specification is run.
| Configuration | Possible Cause | Solution |
| SQL Server is hosting an
iBase SQL Server database. The Scheduler service is running under the context of a domain account. The iBase database connection file is configured to access the SQL Server machine by using Windows security. |
The Scheduler service account does not have a corresponding login, which uses the Windows authentication security model, on the SQL Server machine. | Create an SQL Server login
that uses the Windows authentication model and uses the
domain account in use by the Scheduler service. Grant the SQL Server login rights to access the iBase database on the SQL Server machine. |
Login failed for user ‘NT AUTHORITY\SYSTEM'
The Scheduler service creates an entry in the log when a batch import specification is run.
| Configuration | Possible Cause | Solution |
SQL Server is hosting an
iBase SQL Server database. The BUILTIN\Administrators group has been removed from
the SQL Server security configuration.The Scheduler service is on the same machine as the SQL Server instance that is hosting the iBase database and is running under the context of the local system account. |
The local system account
does not have rights to access the iBase database. The local system account is a special account with administrative rights on the local machine and is a member of the Administrators group at the operating system level. Removing theBUILTIN\Administrators account from SQL
Server has revoked rights to the database for the local system account. |
Create a security login
within SQL Server with the name NT AUTHORITY\SYSTEM that uses the Windows authentication model.Add this new login to the
|
| Or Configure the Scheduler service to run under the context of a domain account that has rights within SQL Server to access the iBase SQL Server database. |
Login failed for user ‘< domain_name >\< computer_name >$’.
The Scheduler service creates an entry in the log when a batch import specification is run.
| Configuration | Possible Cause | Solution |
| SQL Server is hosting an
iBase database that is on a different machine to the machine on which the Scheduler Service is
running. The Scheduler service is running under the context of the local system account. The iBase database connection file is configured to access the SQL Server using Windows security. |
The local system account can only access iBase databases that are hosted on the same machine as that running the service. | Change the Scheduler
service configuration to run under the context of a domain account. Create an SQL Server login that uses the Windows authentication model and uses the domain account in use by the Scheduler service. Grant the SQL Server login rights to access the iBase database on the SQL Server machine. |
Logon failed for user ‘(null)’. Reason: Not associated with a trusted SQL server connection.
The Scheduler service creates an entry in the log when a batch import specification is run.
| Configuration | Possible Cause | Solution |
| The Scheduler service is
running under the context of a local machine account. SQL Server is hosting an iBase SQL Server database on a different machine to that running the Scheduler service. The iBase database connection file is on the same machine as the Scheduler service, and is configured to access the SQL Server by using Windows security. |
It is not possible to grant a local Windows account on one machine access to an SQL server instance on another machine. | Change the Scheduler
service configuration to run under the context of a domain account. Create an SQL Server login that uses the Windows authentication model and uses the domain account in use by the Scheduler service. Grant the SQL Server login rights to access the iBase database on the SQL Server machine. |
Cannot open database requested in login ‘< database_name >’. Login fails.
The Scheduler service creates an entry in the log when a batch import specification is run.
| Configuration | Possible Cause | Solution |
| The Scheduler service is
running under the context of a domain account. SQL Server is hosting an iBase SQL Server database. The iBase connection is configured to access the SQL Server by using Windows security. |
The Scheduler service account does not have sufficient rights within SQL Server to access the iBase database. | Grant the SQL Server login for the Scheduler service domain account rights to access the iBase database on the SQL Server machine. |
Invalid procedure call or argument.
The Scheduler service creates this entry in the log when a task action is run.
| Configuration | Possible Cause | Solution |
| The task that is run has a Program Action that is to be run. | The Program Action is
defined to run an operating system batch file. The batch file has no content. |
Remove the batch file from the list of actions for the task. |
| Or Ensure that the batch file is not zero bytes by entering a carriage return into the file. |
Permission Denied file path: < path >.
The Scheduler service creates this entry in the log when a batch import specification is run and an attempt is made to read an import file.
| Configuration | Possible Cause | Solution |
| The Scheduler service is running on the same machine as the import file location. | The Scheduler service has insufficient permissions to open the import file. | Grant the Scheduler service account the required permissions to the import files. |
| The Scheduler service is operating under the context of the Local System account. The import files is on a remote machine. | The Scheduler service has insufficient permissions to open the import file. | Change the Scheduler service account to a domain account with the required permissions on the import files. |
| Or Grant the 'Everyone' group the required permissions on the import files. |
Path/File access error.
The Scheduler service creates this entry in the log when a batch export specification is run and an attempt is made to create or overwrite an export file.
| Configuration | Possible Cause | Solution |
| The Scheduler service is running on the same machine as the export file location. | The Scheduler service has insufficient permissions to create an export file in the folder specified. | Grant the Scheduler service account the required permissions to the folder in which the export file is to be created. |
| The Scheduler service is operating under the context of the Local System account. The export file folder is on a remote machine. | The Scheduler service has insufficient permissions to create an export file in the folder specified. | Change the Scheduler service account to a domain account with the required permissions on the folder intended for export files. |
Miscellaneous problems
A task that is set up to execute on the change of a trigger file executes more than once, or does not execute when expected.| Configuration | Possible Cause | Solution |
| The Scheduler service and the trigger files are on two separate machines. | The machine on which the Scheduler service is executing has a different date, time, or both to the machine on which the trigger file is. | Ensure that the Windows Time service is running on each machine. This automatically synchronizes the times on the two machines with the domain controller. |
| Or Manually synchronize the times on the two machines by using the NET TIME command. |
The Scheduler database lock file ( Scheduler.ldb) persists in the directory after both the service and configuration applications have been shut down.
The .ldb file is a Microsoft™ Jet locking file that is removed if the applications are shut down cleanly.
| Configuration | Possible Cause | Solution |
| N/A | The last application to use the Scheduler database stopped abnormally. | The file will be removed the next time an application that uses the Scheduler database is stopped cleanly and it is the last application that is accessing the database. |
| The database is accessed through a folder share. The file system in use is NTFS or FAT. | The folder share permissions are preventing users from deleting files available through the share. | Alter the folder share permissions to allow users that access the Scheduler database with the Scheduler Configuration utility permissions to delete the Jet locking file. |
| The database is accessed through a folder share. The file system in use is NTFS. | The folder and file security permissions are preventing users from deleting the Jet locking file. | Alter the folder and file security permissions to grant the users that use the Scheduler Configuration utility at least the minimum permissions required for the Scheduler database. |