Problem Note 64759: The errors "Grid job failed to run" and "Remote signon...canceled" occur in SAS® Grid Manager after you use the GRDSVC_ENABLE function
 |  |  |  |  |
When you submit the JOBNAME= argument with the GRDSVC_ENABLE function, the connection might fail with an error that is similar to the following:
Submitted code: %let jname="job name";
Result:
NOTE: Remote session ID T1 will use its enabled grid service.
NOTE: Remote signon to T1 commencing (SAS Release 9.04.01M6P082819).
ERROR: The requested operation is invalid for URL
'http://myhost.unx.sas.com:9999/sasgrid/api/jobs'.
ERROR: PROVIDER(SAS): Exception occurred: HTTP Status:400, Error:0x94bfd83a,
Msg:'The server was not able to parse the JSON content.', Details:'<none>'
ERROR: Grid job failed to run.
ERROR: A communication subsystem partner link setup request failure has
occurred.
ERROR: Could not start grid job or grid job failed.
ERROR: Remote signon to T1 canceled.
Result:
NOTE: Remote session ID T1 will use its enabled grid service.
NOTE: Remote signon to T1 commencing (SAS Release 9.04.01M6P082819).
ERROR: The requested operation is invalid for URL
'http://myhost.unx.sas.com:9999/sasgrid/api/jobs'.
ERROR: PROVIDER(SAS): Exception occurred: HTTP Status:400, Error:0x94bfd83a,
Msg:'The server was not able to parse the JSON content.', Details:'<none>'
ERROR: Grid job failed to run.
ERROR: A communication subsystem partner link setup request failure has
occurred.
ERROR: Could not start grid job or grid job failed.
ERROR: Remote signon to T1 canceled.
This issue occurs when quotation marks are included as part of the job name that is listed in the JOBNAME= argument.
As a workaround, ensure that the job name does not include quotation marks.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Grid Manager | Microsoft Windows 8 Pro 32-bit | 9.4_M6 | 9.4 TS1M6 | ||
| Microsoft Windows 8 Enterprise x64 | 9.4_M6 | 9.4 TS1M6 | ||||
| Microsoft Windows 8 Enterprise 32-bit | 9.4_M6 | 9.4 TS1M6 | ||||
| Microsoft® Windows® for x64 | 9.4_M6 | 9.4 TS1M6 | ||||
| Microsoft Windows 8 Pro x64 | 9.4_M6 | 9.4 TS1M6 | ||||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M6 | 9.4 TS1M6 | ||||
| Microsoft Windows 8.1 Enterprise x64 | 9.4_M6 | 9.4 TS1M6 | ||||
| Microsoft Windows 8.1 Pro 32-bit | 9.4_M6 | 9.4 TS1M6 | ||||
| Microsoft Windows 8.1 Pro x64 | 9.4_M6 | 9.4 TS1M6 | ||||
| Microsoft Windows 10 | 9.4_M6 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2012 Datacenter | 9.4_M6 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2012 R2 Datacenter | 9.4_M6 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2012 R2 Std | 9.4_M6 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2012 Std | 9.4_M6 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2016 | 9.4_M6 | 9.4 TS1M6 | ||||
| Microsoft Windows Server 2019 | 9.4_M6 | 9.4 TS1M6 | ||||
| Windows 7 Enterprise 32 bit | 9.4_M6 | 9.4 TS1M6 | ||||
| Windows 7 Enterprise x64 | 9.4_M6 | 9.4 TS1M6 | ||||
| Windows 7 Home Premium 32 bit | 9.4_M6 | 9.4 TS1M6 | ||||
| Windows 7 Home Premium x64 | 9.4_M6 | 9.4 TS1M6 | ||||
| Windows 7 Professional 32 bit | 9.4_M6 | 9.4 TS1M6 | ||||
| Windows 7 Professional x64 | 9.4_M6 | 9.4 TS1M6 | ||||
| Windows 7 Ultimate 32 bit | 9.4_M6 | 9.4 TS1M6 | ||||
| Windows 7 Ultimate x64 | 9.4_M6 | 9.4 TS1M6 | ||||
| 64-bit Enabled AIX | 9.4_M6 | 9.4 TS1M6 | ||||
| 64-bit Enabled Solaris | 9.4_M6 | 9.4 TS1M6 | ||||
| HP-UX IPF | 9.4_M6 | 9.4 TS1M6 | ||||
| Linux for x64 | 9.4_M6 | 9.4 TS1M6 | ||||
| Solaris for x64 | 9.4_M6 | 9.4 TS1M6 | ||||
A fix for this issue for SAS Workload Orchestrator 9.46 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/E3Y.html#64759| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2019-10-23 13:38:31 |
| Date Created: | 2019-09-10 16:11:11 |