SASDrive search service not working HTTP-500 The search query could not be processed. Contact Admin

[paterd2]

In sas viya 4 we get an error as the following.

022-01-25 13:26:59.829100 {"message":"Resource: POST /search/content\nHTTP-status: 500 error\nFout: 10012 The search query could not be processed. Contact your system administrator.\n","jqXHR":{"readyState":4,"responseText":"{\"errorCode\":10012,\"message\":\"The search query could not be processed. Contact your system administrator.\",\"details\":[\"traceId: 94440968d63980ef\",\"path: /search/content\"],\"links\":[],\"version\":2,\"httpStatusCode\":500}","responseJSON":{"errorCode":10012,"message":"The search query could not be processed. Contact your system administrator.","details":["traceId: 94440968d63980ef","path: /search/content"],"links":[],"version":2,"httpStatusCode":500},"status":500,"statusText":"error"},"status":"error"} - sas.drive.driveproviders.SearchDrive
u @ sap-ui-custom.js:110

[gwootton]

This error appears to be saying that a call being made to the /search endpoint is failing with an HTTP 500 response, so the logs for the sas-search pod are where you will need to look to determine the cause.

[paterd2]

Thank you mr.Gwooton.

We now have the following error in our pod : 

{"version":1,"timeStamp":"2021-12-22T10:57:27.607Z","level":"error","source":"sas-search","message":"[EXCEPTION_WHILE_SEARCHING] An error occurred while searching. Details: com.sas.cas.CASException:  Invalid language is specified in TKLing. (severity=2 reason=6 statusCode=3401853)\n5 ERROR:  Invalid language is specified in TKLing.\n5 ERROR: The action stopped due to errors.\ndebug=0x8abfe73d:CASIDX_INVALID_LANG_CODE","properties":{"logger":"com.sas.svcs.search.dao.CASSearchQueryDao","thread":"https-jsse-nio-0.0.0.0-8081-exec-4","traceId":"24e6a752b5bae2cb","spanId":"24e6a752b5bae2cb","spanExportable":"true","__session":"003c8930-fdac-4dc0-bfbb-a2c4011dd8cd","application":"search","username":"NOMENNESCIO"},"messageKey":"com.sas.svcs.search.LogMessages.EXCEPTION_WHILE_SEARCHING","messageParameters":{"0":"com.sas.cas.CASException:  Invalid language is specified in TKLing. (severity=2 reason=6 statusCode=3401853)\n\t5 ERROR:  Invalid language is specified in TKLing.\n\t5 ERROR: The action stopped due to errors.\n\tdebug=0x8abfe73d:CASIDX_INVALID_LANG_CODE"}}

{"version":1,"timeStamp":"2021-12-22T10:57:27.625Z","level":"error","source":"sas-search","message":"com.sas.commons.rest.exceptions.ResourceException: The search query could not be processed. Contact your system administrator.","properties":{"logger":"com.sas.commons.rest.ExceptionLog","thread":"https-jsse-nio-0.0.0.0-8081-exec-4","traceId":"24e6a752b5bae2cb","spanId":"24e6a752b5bae2cb","spanExportable":"true","__session":"003c8930-fdac-4dc0-bfbb-a2c4011dd8cd","application":"search","username":"NOMENNESCIO"},"messageParameters":{"0":"com.sas.commons.rest.exceptions.ResourceException","1":"The search query could not be processed. Contact your system administrator."}}

[gwootton]

In the past we've seen this behavior as a result of the sas-commonfiles job failing to complete successfully because of a read-only ".snapshot" directory being created in the PVC by the storage provider. Not using snapshot would be one way to workaround the issue.

You may want to engage SAS Technical Support on this one.

[paterd2]

Mr. Gwooton
That is exactly what we see, sas-commonfiles job failing to complete.
I will look where to disable the snapshot.
Thank you.