SAS Job Flow Scheduler generates a "Premature end of file" error and stops processing all scheduled jobs. SAS® Management Console also becomes unresponsive when the Schedule Manager plug-in is accessed while SAS Job Flow Scheduler is in this state.
In the Schedule Manager in SAS Management Console, the following pop-up error message appears:
Schedule Flow
Scheduling of "job-name" failed ('The interface to the scheduling server is not available. Contact SAS Technical Support.').
In the Trigger service log, messages that are similar to the following occur:
2019-10-25 14:55:39,821 [main] ERROR com.sas.scheduler.api.servers.sasjfs.utilities.JFSClient - connect: Address is invalid on local machine, or port is not valid on remote machine
In the SAS Workflow Orchestrator log, messages that are similar to the following occur:
2019-10-25 13:30:36,157 [main] ERROR com.sas.scheduler.api.servers.sasjfs.utilities.JFSClient - Connection refused: connect
2019-10-25 13:30:36,158 [main] DEBUG com.sas.scheduler.api.servers.sasjfs.utilities.JFSClient - Sending request to TCP Server
2019-10-25 13:30:36,164 [main] ERROR com.sas.scheduler.api.servers.sasjfs.utilities.JFSClient -
2019-10-25 13:30:36,184 [main] DEBUG com.sas.scheduler.api.servers.sasjfs.floworchestration.FlowOrchestrator - Flow xml for flowDefId:[INVALID USER]@[Domain]_AMS_Check_New:
2019-10-25 13:30:36,209 [main] DEBUG com.sas.scheduler.api.servers.sasjfs.floworchestration.FlowOrchestrator - SchedulerException, retrieving FlowInfo from DAV and initializing to FlowInfo obj: Premature end of file.
2019-10-25 13:30:36,234 [main] ERROR com.sas.scheduler.api.servers.sasjfs.floworchestration.FlowOrchestrator - SchedulerException: Premature end of file.
2019-10-25 13:30:36,234 [main] ERROR com.sas.scheduler.api.servers.sasjfs.floworchestration.FlowOrchestrator - com.sas.scheduler.model.SchedulerException: Premature end of file.
2019-10-25 13:30:36,276 [main] DEBUG com.sas.scheduler.api.servers.sasjfs.floworchestration.FlowOrchestrator - Running flow as user: Domain\[VALID SERVICE ACCOUNT]
This problem occurs after a scheduled job runs, and that job is owned by a user who was previously deleted from the system.
This issue does not occur immediately after the user access is disabled, but it does occur after the SAS Job Flow Scheduler server reboots.
A workaround is either to unschedule all scheduled jobs that are owned by the invalid user or to delete the jobs that are owned by that user from the Task Scheduler on the operating system. Then reboot the server and re-initialize servers.
As a best practice, anytime that you need to remove a user from the system, ensure that you first delete any scheduled flows that are owned by that user.
Operating System and Release Information
SAS System | SAS Job Flow Scheduler | Microsoft® Windows® for x64 | 9.46 | 9.46 | 9.4 TS1M6 | 9.4 TS1M6 |
Linux for x64 | 9.46 | 9.46 | 9.4 TS1M6 | 9.4 TS1M6 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.