I just managed to resolve this. I had enabled trace logging on the SASApp Workspace Server as requested by SAS Technical Support in a track on an unrelated issue and looked at the log produced from running this which contained the following.   NOTE: Remote session ID TASK1 will use the grid service _ALL_. NOTE: Remote signon to TASK1 commencing (SAS Release 9.04.01M7P080520). Secure communications error status 807ff01d description "[ip address redacted]: SSL Error: Cannot use private key file; please check your password." SSL Error: Cannot use private key file; please check your password. ERROR: Secure communications error status 807ff01d description "[ip address redacted]: SSL Error: Cannot use private key file; please check your password." ERROR: SSL Error: Cannot use private key file; please check your password. ERROR: PROVIDER(SAS): Unable to get grid information from the master host. ERROR: Cannot initialize the grid provider module. ERROR: A communication subsystem partner link setup request failure has occurred. ERROR: Cannot initialize the grid provider module. NOTE: Subsequent lines will be ignored until ENDRSUBMIT. ERROR: Remote submit to TASK1 canceled. After a bit of research I found the problem: the SSL key file for the SSL certificate used by SAS Workload Orchestrator had 700 permissions (rwx------.) In Prod it was 644 (rw-r--r--.) I changed it to 644 in Dev and rsubmit now works. ... View more