Problem

• Transfer engine ("Scheduler") could not be started after 30 seconds.
• Scheduler is running as a service.
• Starting the SecureClient application with the same username as the service.
• SecureClient tries to start another Scheduler instance, even though the service is running.

Resolution

Verify that the scheduler service is configured with the same letter case as the account you launch the SecureClient application:

1. Open CMD window and run "whoami" command.
2. Right click on the "Axway Secure Client Scheduler" service and select "Properties".
3. Under the "Log on" tab, rewrite the credentials to match the output of the "whoami" command. They should be the same case.
4. Apply, and restart the "Axway Secure Client Scheduler" service.

NOTE: SecureClient scheduler service user configuration is case sensitive, so it must use the same credentials as the logged user.