When you create a project in SAS® Visual Data Mining and Machine Learning Model Studio, an error occurs in the /opt/sas/viya/config/var/log/compute/default/sas-compute_YYYY-MM-DD_XX-XX-XX.log file. You see the following error when your time zone is not set to UTC on the server operating system:
2018-09-21 06:25:38.308 INFO 9279 --- [ bootstrap-7] o.h.h.i.QueryTranslatorFactoryInitiator : service [9b0efef772b35bb3] HHH000397: Using ASTQueryTranslatorFactory
2018-09-21 06:25:53.082 INFO 9279 --- [ SASExecutor1] c.s.c.j.s.ComputeExecutionProviderImpl : service [aa22e86d938c85ce] [JOB_STATE] The state of the compute job BF019D41-2974-364E-9FF4-161A8E047993 in session 955527b6-55f4-46d0-8aff-2edb61a58ccf-ses0000 is completed.
2018-09-21 06:25:53.134 INFO 9279 --- [ SASExecutor1] c.s.c.j.s.ComputeExecutionProviderImpl : service [aa22e86d938c85ce] [JOB_CONDITION_CODE] The conditionCode for compute job BF019D41-2974-364E-9FF4-161A8E047993 in session 955527b6-55f4-46d0-8aff-2edb61a58ccf-ses0000 is 0.
2018-09-21 06:25:53.461 ERROR 9279 --- [ SASExecutor1] c.sas.compute.jes.service.RestLinkUtil : service [aa22e86d938c85ce] [EXCEPTION_ACCESSING_RESOURCE] Invoking Request <PATCH /files/files/1c8a2231-f0eb-4008-a50e-9bcfc83a75e5,FileResource [id=1c8a2231-f0eb-4008-a50e-9bcfc83a75e5,
parentUri=/jobExecution/jobs/bbbed53b-2964-40f9-829a-2f1a7002bc24, properties={}, contentDisposition=null, contentType=application/vnd.sas.collection+json, description=null, documentType=null, encoding=UTF-8, name=BF019D41-2974-364E-9FF4-161A8E047993.log, size=4578 expiratioTimeStamp=null
version=2],{If-Unmodified-Since=[Fri Sep 21 06:25:53 JST 2018], Accept=[application/vnd.sas.file+json, application/vnd.sas.error+json], Content-Type=[application/vnd.sas.file+json]}> with expected response type class com.sas.svcs.file.representations.FileResource
resulted in an exception 400 with reason {"errorCode":0,"details":["correlator: ef38cd26-ceb7-46dc-96c6-9edacbf1ba99;a3cbae86-e5df-46d1-8db4-9fee3b1efecf;15812f 56-8226-4ae9-aa88-a05edf97a3a6;660d5b1c-251f-4902-8396-8641d2f1a6c8","traceId: aa22e86d938c85ce","path:
/files/files/1c8a2231-f0eb-4008-a50e-9bcfc83a75e5"],"links":[],"version":2,"http StatusCode":400}.
2018-09-21 06:25:53.461 ERROR 9279 --- [ SASExecutor1] c.s.c.jes.service.FileServiceProxyImpl : service [aa22e86d938c85ce] [CANNOT_PATCH_FILE] Failed to PATCH file resources {"errorCode":0,"details":["correlator: ef38cd26-ceb7-46dc-96c6-9edacbf1ba99;a3cbae86-e5df-46d1-8db4-9fee3b1efecf;15812f
56-8226-4ae9-aa88-a05edf97a3a6;660d5b1c-251f-4902-8396-8641d2f1a6c8","traceId: aa22e86d938c85ce","path: /files/files/1c8a2231-f0eb-4008-a50e-9bcfc83a75e5"],"links":[],"version":2,"http StatusCode":400} due to exception 400 .
2018-09-21 06:25:53.462 WARN 9279 --- [ SASExecutor1] c.s.c.j.s.ComputeExecutionProviderImpl : service [aa22e86d938c85ce] [FILE_NAME_AND_PARENT_NOT_SET] Failed to set file name to BF019D41-2974-364E-9FF4-161A8E047993.log and parent to /jobExecution/jobs/bbbed53b-2964-40f9-829a-2f1a7002bc24.
server.sas.com> server.sas.com>
Even though you receive this error, the project might run successfully.
To work around this issue, set your time zone to UTC.
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Verify That the Update Is Installed
To verify that the fix is installed, run the following rpm command:
rpm -q sas-compute
To complete this process, make sure that the package version that is shown in the rpm output either matches or is newer than the following:
sas-compute-1.0.4-20180911.1536685302731.x86_64.rpm
Additional Assistance
If you need additional assistance, contact SAS Technical Support.
Operating System and Release Information
SAS System | SAS Viya | Microsoft® Windows® for x64 | 3.3 | | | |
Microsoft Windows 8 Enterprise 32-bit | 3.3 | | | |
Microsoft Windows 8 Enterprise x64 | 3.3 | | | |
Microsoft Windows 8 Pro 32-bit | 3.3 | | | |
Microsoft Windows 8 Pro x64 | 3.3 | | | |
Microsoft Windows 8.1 Enterprise 32-bit | 3.3 | | | |
Microsoft Windows 8.1 Enterprise x64 | 3.3 | | | |
Microsoft Windows 8.1 Pro 32-bit | 3.3 | | | |
Microsoft Windows 8.1 Pro x64 | 3.3 | | | |
Microsoft Windows 10 | 3.3 | | | |
Microsoft Windows 95/98 | 3.3 | | | |
Microsoft Windows 2000 Advanced Server | 3.3 | | | |
Microsoft Windows 2000 Datacenter Server | 3.3 | | | |
Microsoft Windows 2000 Server | 3.3 | | | |
Microsoft Windows 2000 Professional | 3.3 | | | |
Microsoft Windows NT Workstation | 3.3 | | | |
Microsoft Windows Server 2003 Datacenter Edition | 3.3 | | | |
Microsoft Windows Server 2003 Enterprise Edition | 3.3 | | | |
Microsoft Windows Server 2003 Standard Edition | 3.3 | | | |
Microsoft Windows Server 2003 for x64 | 3.3 | | | |
Microsoft Windows Server 2008 | 3.3 | | | |
Microsoft Windows Server 2008 R2 | 3.3 | | | |
Microsoft Windows Server 2008 for x64 | 3.3 | | | |
Microsoft Windows Server 2012 Datacenter | 3.3 | | | |
Microsoft Windows Server 2012 R2 Datacenter | 3.3 | | | |
Microsoft Windows Server 2012 R2 Std | 3.3 | | | |
Microsoft Windows Server 2012 Std | 3.3 | | | |
Microsoft Windows Server 2016 | 3.3 | | | |
Microsoft Windows XP Professional | 3.3 | | | |
Windows 7 Enterprise 32 bit | 3.3 | | | |
Windows 7 Enterprise x64 | 3.3 | | | |
Windows 7 Home Premium 32 bit | 3.3 | | | |
Windows 7 Home Premium x64 | 3.3 | | | |
Windows 7 Professional 32 bit | 3.3 | | | |
Windows 7 Professional x64 | 3.3 | | | |
Windows 7 Ultimate 32 bit | 3.3 | | | |
Windows 7 Ultimate x64 | 3.3 | | | |
Windows Millennium Edition (Me) | 3.3 | | | |
Windows Vista | 3.3 | | | |
Windows Vista for x64 | 3.3 | | | |
Linux for x64 | 3.3 | | | |
*
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.