| 207 | 5737 | The request was successful, but there were non-critical errors handling the log, listing, or results. |
| 400 | 5001 | The request was invalid. The server is in an invalid state and cannot process the request. |
| 400 | 5006 | The request was invalid. The server is unable to process the request that was submitted. |
| 400 | 5009 | The request was invalid. The payload for this request is missing. |
| 400 | 5010 | The request was invalid. The payload for this request could not be processed. |
| 400 | 5014 | The request was invalid. No token is available for the server to communicate with other services. |
| 400 | 5023 | The request was invalid. The specified Accept-language header cannot be used by the server. |
| 400 | 5024 | The request was invalid. The specified filter function is not supported by the server. |
| 400 | 5025 | The request was invalid. The specified filter function contains invalid arguments. |
| 400 | 5026 | The request was invalid. The specified filter function is not formatted correctly. |
| 400 | 5027 | The request was invalid. The requested endpoint does not support filtering. |
| 400 | 5028 | The request was invalid. The specified sortBy option is not supported by the server. |
| 400 | 5029 | The request was invalid. The specified sortBy option contains invalid arguments. |
| 400 | 5030 | The request was invalid. The specified sortBy option references an invalid or non-existent key. |
| 400 | 5031 | The request was invalid. The specified sortBy option references a value that is not sortable. |
| 400 | 5032 | The request was invalid. The specified endpoint does not support sorting. |
| 400 | 5106 | The request was invalid. A resource that you requested is invalid. |
| 400 | 5107 | The request was invalid. A resource that you requested is of an unknown type. |
| 400 | 5202 | The request was invalid. There was no SAS code submitted in this job request. |
| 400 | 5203 | The request was invalid. The SAS code submitted in this job request is invalid. |
| 400 | 5205 | The request was invalid. The job request contains an invalid variable. |
| 400 | 5206 | The request was invalid. The job request contains an invalid option. |
| 400 | 5207 | The request was invalid. The specified query parameter for the log or listing endpoint is not valid. |
| 400 | 5209 | The request was invalid. The body of the request for streaming log or listing output to the Files Service was missing or did not conform to the schema. |
| 400 | 5210 | The request was invalid. Job log or listing output cannot be streamed while the job is still running. |
| 400 | 5211 | The request was invalid. There is no log or listing output available to stream. |
| 400 | 5305 | The request was invalid. The request exceeded the number of rows in the table. |
| 400 | 5306 | The request was invalid. The selection of columns in the table has failed. |
| 400 | 5307 | The request was invalid. The request has exceeded the number of columns in the table. |
| 400 | 5315 | The request was invalid. A password is required to access the table. |
| 400 | 5316 | The request was invalid. The specified table could not be opened. |
| 400 | 5318 | The request was invalid. There is a problem with the WHERE clause in the request. |
| 400 | 5320 | The request was invalid. The specified table cannot be renamed. |
| 400 | 5326 | The request was invalid. The request to update the column failed. |
| 400 | 5327 | The request was invalid. The request to update the column failed due to a naming conflict. |
| 400 | 5334 | The request was invalid. The library name that was included in the path contains too many characters. |
| 400 | 5335 | The request was invalid. The library assignment request is missing the required parameter name. |
| 400 | 5336 | The request was invalid. The specified format is not compatible with the column. |
| 400 | 5337 | The request was invalid. The specified value of the fileProtectionEncoding field is not supported by the server. |
| 400 | 5338 | The request was invalid. One or more of the values of the fileProtection field could not be decoded by the server. |
| 400 | 5339 | The request was invalid. The format or informat name is invalid. |
| 400 | 5340 | The request was invalid. The format or informat length value is invalid. |
| 400 | 5341 | The request was invalid. The format or informat decimal value is invalid. |
| 400 | 5342 | The request was invalid. One or more table formats could not be loaded. |
| 400 | 5343 | The request was invalid. The property 'sortBy' in the 'rowSet' request is not supported. |
| 400 | 5400 | The request was invalid. The requested fileref could not be found. |
| 400 | 5401 | The request was invalid. The requested access method for the fileref is not supported by this server. |
| 400 | 5402 | The request was invalid. The fileref requested already exists. |
| 400 | 5403 | The request was invalid. The options in the fileref request cannot be processed. |
| 400 | 5404 | The request was invalid. The assignment of the fileref in the request has failed. |
| 400 | 5405 | The request was invalid. The requested fileref name cannot be longer than 8 characters. |
| 400 | 5406 | The request was invalid. The name of the fileref access method cannot be longer than 8 characters. |
| 400 | 5408 | The request was invalid. The requested fileref cannot be deassigned. |
| 400 | 5410 | The request was invalid. The deletion of the physical file that is associated with the fileref has failed. |
| 400 | 5411 | The request was invalid. The response for the fileref resource could not be generated. |
| 400 | 5412 | The request was invalid. The physical file that is associated with the fileref already exists. |
| 400 | 5413 | The request was invalid. The fileref name is missing. |
| 400 | 5414 | The request was invalid. The directory that is associated with the fileref could not be opened. |
| 400 | 5415 | The request was invalid. The directory that is associated with the fileref could not be closed. |
| 400 | 5416 | The request was invalid. The server was unable to determine the members of the directory that is associated with the fileref. |
| 400 | 5418 | The request was invalid. The specified entry does not exist in the directory-based fileref. |
| 400 | 5419 | The request was invalid. The physical file that is associated with the fileref could not be opened. |
| 400 | 5420 | The request was invalid. The physical file that is associated with the fileref could not be closed. |
| 400 | 5421 | The request was invalid. Reading from the physical file that is associated with the fileref has failed. |
| 400 | 5422 | The request was invalid. Writing to the physical file that is associated with the fileref has failed. |
| 400 | 5424 | The request was invalid. A mix of files and directories in the path for the requested fileref is not supported. |
| 400 | 5426 | The request was invalid. The subdirectory of the directory that is associated with the fileref could not be opened. |
| 400 | 5427 | The request was invalid. The member of the directory that is associated with the fileref could not be closed. |
| 400 | 5428 | The request was invalid. The subdirectory of the directory that is associated with the fileref could not be closed. |
| 400 | 5429 | The request was invalid. Reading from the member of the directory that is associated with the fileref has failed. |
| 400 | 5430 | The request was invalid. Writing to the member of the directory that is associated with the fileref has failed. |
| 400 | 5431 | The request was invalid. The member of the fileref is a subdirectory and cannot be updated directly. |
| 400 | 5432 | The request was invalid. The fileref request is missing a quotation mark in the path name. |
| 400 | 5434 | The request was invalid. The requested file access method is invalid. |
| 400 | 5436 | The request was invalid. The requested path is too long. |
| 400 | 5437 | The request was invalid. The requested file or directory information is not available. |
| 400 | 5444 | The request was invalid. The request could not be fulfilled because the disk quota has been exceeded. |
| 400 | 5445 | The request was invalid. The requested path is invalid. |
| 400 | 5452 | The request was invalid. Provide a name in the request body. |
| 400 | 5455 | The request was invalid. The host returned an error message during the processing of the path. |
| 400 | 5456 | The request was invalid. There is a missing parenthesis in the concatenated pathname for the fileref. |
| 400 | 5457 | The request was invalid. The requested path contains directory traversal that is disallowed by this compute session. |
| 400 | 5500 | The request was invalid. The value that is given for the specified option cannot be set. |
| 400 | 5501 | The request was invalid. The request is missing the option name. |
| 400 | 5502 | The request was invalid. The specified option cannot be obtained. |
| 400 | 5503 | The request was invalid. The value that was provided for the specified option is invalid. |
| 400 | 5504 | The request was invalid. The requested variable is invalid. |
| 400 | 5700 | The request was invalid. The jobRequest field is not provided. |
| 400 | 5701 | The request was invalid. The jobDefinition field is not provided. |
| 400 | 5718 | The request was invalid. An invalid URI has been returned in the job results link. |
| 400 | 5719 | The request was invalid. The jobDefinition field is not provided. More details are available. |
| 400 | 5720 | The request was invalid. A specific link that is required from the job was missing. |
| 400 | 5734 | The request was invalid. The context name or session identifier is missing. |
| 400 | 5735 | The request was invalid. The job request contains an invalid argument. |
| 400 | 5738 | The request was invalid. The log or listing for the job was too large. |
| 400 | 5739 | The request was invalid. The job request cannot contain both a context identifier and a context name or session identifier. |
| 400 | 5761 | The request was invalid. The format of the table identifier is invalid. |
| 400 | 5762 | The request was invalid. The specified query parameter for paging is invalid. |
| 400 | 5803 | The request was invalid. The ID of the object in the URL does not match the context that is supplied in the request body. |
| 400 | 5815 | The request was invalid. The launch type that you specified is unsupported. |
| 400 | 5826 | The request was invalid. A launch via the Launcher service requires a launcher context name or identifier. |
| 400 | 5828 | The request was invalid. The launcher context that is associated with this request is not found. |
| 400 | 5829 | The request was invalid. The Compute service was unable to format the SAS Compute Server command. |
| 400 | 5841 | The request was invalid. A context with the specified name already exists. |
| 400 | 5845 | The request was invalid. The Compute context name must not be null. |
| 400 | 5846 | The request was invalid. The value of the Accept-Item header that is provided to the GET request to /compute/contexts is not valid. |
| 400 | 5847 | The request was invalid. The value of the Accept-Item header that is provided to the GET request to /compute/sessions is not valid. |
| 400 | 5850 | The request was invalid. The resource name for the Compute context must not be null. |
| 400 | 5851 | The request was invalid. Each resource name within a Compute context must be unique. |
| 400 | 5852 | The request was invalid. The resource type for the Compute context must not be null. |
| 400 | 5853 | The request was invalid. The resource URI for the Compute context must not be null. |
| 400 | 5854 | The request was invalid. The attempt to launch a SAS Compute Server using the service account failed, because a service account credential is not available. |
| 400 | 5855 | The request was invalid. The value of the runServerAs attribute must not be empty or blank. |
| 400 | 5857 | The request was invalid. Run reusable processes on the SAS Compute Server by specifying a shared service account. The Compute context includes a reuseServerProcesses attribute but not the required runServerAs attribute. |
| 400 | 5858 | The request was invalid. The value for the serverReuseLimit attribute must be a nonnegative integer. |
| 400 | 5859 | The request was invalid. The value for the serverInactiveTimeout attribute must be a nonnegative integer. |
| 400 | 5860 | The request was invalid. The Compute context name must not be over 100 characters long. |
| 400 | 5861 | The request was invalid. The Compute context description must not be over 1000 characters long. |
| 400 | 5862 | The request was invalid. The resource name for the Compute context must not be over 40 character long. |
| 400 | 5863 | The request was invalid. The resource type for the Compute context must not be over 100 character long. |
| 400 | 5864 | The request was invalid. The resource URI for the Compute context must not be over 500 character long. |
| 400 | 5865 | The request was invalid. The Context context could not be deleted because it is in use by one or more Compute servers. |
| 400 | 5866 | The request was invalid. The value for the serverMinAvailable attribute must be a nonnegative integer. |
| 400 | 5867 | The request was invalid. The Compute context workload queue name must not be over 250 characters long. |
| 400 | 5869 | The request was invalid. The value for the reuseServerProcesses attribute must be true or false. |
| 401 | 5022 | The user was not authenticated. |
| 403 | 5103 | The user did not have the necessary permissions. |
| 403 | 5321 | The user did not have the necessary permissions. The request to rename the table is invalid. |
| 403 | 5322 | The user did not have the necessary permissions. The table cannot be renamed because it is read only. |
| 403 | 5323 | The user did not have the necessary permissions. The label that is given for the table update is invalid. |
| 403 | 5324 | The user did not have the necessary permissions. The label that is given for the table could not be updated. |
| 403 | 5325 | The user did not have the necessary permissions. The column in the requested table cannot be updated, because the table is read only. |
| 403 | 5328 | The user did not have the necessary permissions. The table cannot be updated because it is read only. |
| 403 | 5423 | The user did not have the necessary permissions to access to the physical file that is associated with the fileref. |
| 403 | 5443 | The user did not have the necessary permissions to create the specified directory. |
| 403 | 5856 | The user did not have the necessary permissions to get the launcher contexts. |
| 403 | 5813 | The user did not have the necessary permissions to launch a process. |
| 403 | 5848 | The Compute service does not have the necessary permissions to create authorization rules. |
| 403 | 5849 | The Compute service does not have the necessary permissions to delete all of the existing authorization rules that are related to a Compute context. |
| 403 | 5329 | The user did not have the necessary permissions. The deletion of system libraries is not allowed. |
| 403 | 5330 | The user did not have the necessary permissions. The library cannot be accessed. |
| 403 | 5331 | The user did not have the necessary permissions to rename the specified table in the library. |
| 403 | 5332 | The user did not have the necessary permissions to alter a table in the specified library. |
| 403 | 5450 | The request was invalid. Provide a file path instead of a directory path. |
| 403 | 5454 | The user did not have the necessary permissions. The file or directory is in use and is locked. |
| 404 | 5007 | No endpoint exists at the requested path. |
| 404 | 5008 | No API or endpoint exists at the requested path. The server is unable to route the request. |
| 404 | 5105 | No session exists at the requested path. |
| 404 | 5108 | No engine exists at the requested path. |
| 404 | 5204 | No job exists at the requested path. |
| 404 | 5300 | No library exists at the requested path. |
| 404 | 5301 | No library exists at the requested path. |
| 404 | 5314 | No table exists at the requested path. |
| 404 | 5317 | No column exists at the requested path. |
| 404 | 5319 | No table exists at the requested path. |
| 404 | 5407 | No fileref exists at the requested path. |
| 404 | 5409 | No physical file exists that is associated with the requested fileref. |
| 404 | 5417 | No parent exists for the requested fileref. |
| 404 | 5425 | The request is invalid. The member of the directory that is associated with the fileref could not be opened. |
| 404 | 5433 | No physical files exist in the concatenated list that is associated with the requested fileref. |
| 404 | 5435 | No file or directory exists at the requested path. |
| 404 | 5448 | No file exists at the requested path. |
| 404 | 5449 | No file exists at the requested path. |
| 404 | 5505 | No variable exists at the requested path. |
| 404 | 5756 | No session exists at the requested path. |
| 404 | 5758 | No resource exists at the requested path. |
| 404 | 5759 | No resource exists at the requested path, and an error was returned. |
| 404 | 5760 | No resource exists at the requested path. |
| 404 | 5836 | No server exists at the requested path. The identifier was invalid. |
| 404 | 5837 | No session exists at the requested path. The identifier was invalid. |
| 404 | 5842 | No context exists at the requested path. The identifier was invalid. |
| 404 | 5844 | No context exists at the requested path. |
| 405 | 5019 | The request was invalid. The specified method is invalid for this request. |
| 406 | 5016 | The request was invalid. An invalid header was provided to the server. |
| 406 | 5020 | The request was invalid. The specified Accept header is not supported. |
| 406 | 5021 | The request was invalid. The specified Content-type header is not supported. |
| 409 | 5453 | The request was invalid. The file or directory already exists. |
| 409 | 5868 | The request was invalid. The updated Compute context is not based on the most recently saved Compute context. |
| 412 | 5034 | The request was invalid. The requested update requires that a precondition be met, but the precondition failed. |
| 428 | 5033 | The request was invalid. The specified update requires that a precondition be met before it can be processed. |
| 500 | 5000 | The request could not be fulfilled because of an unexpected server error. |
| 500 | 5002 | The request could not be fulfilled because of an unexpected server error. The server is unable to load a module that is required by the server. |
| 500 | 5003 | The request could not be fulfilled because of an unexpected server error. The server is unable to create endpoints that are needed to service requests. |
| 500 | 5004 | The request could not be fulfilled because of an unexpected server error. The server is unable to send a response for this request. |
| 500 | 5005 | The request could not be fulfilled because of an unexpected server error. The server is unable to communicate with the client or another service. |
| 500 | 5011 | The request could not be fulfilled because of an unexpected server error. The server has failed to initialize. |
| 500 | 5012 | The request could not be fulfilled because of an unexpected server error. The server was unable to obtain a port from which to listen for HTTP requests. |
| 500 | 5013 | The request could not be fulfilled because of an unexpected server error. The specified port for monitoring HTTP requests is invalid. |
| 500 | 5015 | The request could not be fulfilled because of an unexpected server error. The server cannot register itself with the Launcher API. |
| 500 | 5017 | The request could not be fulfilled because of an unexpected server error. The server was unable to build a response. |
| 500 | 5018 | The request could not be fulfilled because of an unexpected server error. The server is unable to process incoming authorization tokens. |
| 500 | 5100 | The request could not be fulfilled because of an unexpected server error. The session the request could not be processed. |
| 500 | 5101 | The request could not be fulfilled because of an unexpected server error. The session that you requested could not be created. |
| 500 | 5102 | The request could not be fulfilled because of an unexpected server error. The delete request for the session could not be processed. |
| 500 | 5104 | The request could not be fulfilled because of an unexpected server error. The context that is referenced does not exist. |
| 500 | 5110 | The request could not be fulfilled because of an unexpected server error. The server is unable to determine the list of available engines. |
| 500 | 5111 | The request could not be fulfilled because of an unexpected server error. The listing is not available for retrieval from the session. |
| 500 | 5112 | The request could not be fulfilled because of an unexpected server error. The log is not available for retrieval from the session. |
| 500 | 5113 | The request could not be fulfilled because of an unexpected server error. The session is in a stopped or failed state and cannot respond. |
| 500 | 5114 | The request could not be fulfilled because of an unexpected server error. A time-out occurred while trying to cancel the session or job. |
| 500 | 5200 | The request could not be fulfilled because of an unexpected server error. The server was unable to process the job request. |
| 500 | 5201 | The request could not be fulfilled because of an unexpected server error. The server was unable to delete the requested job. |
| 500 | 5208 | The request could not be fulfilled because of an unexpected server error. The server was unable to submit an upload request to the Files service or the Files service failed to process the request. |
| 500 | 5302 | The request could not be fulfilled because of an unexpected server error. The members of the requested library could not be listed. |
| 500 | 5303 | The request could not be fulfilled because of an unexpected server error. The end of data was reached before the request was completed. |
| 500 | 5304 | The request could not be fulfilled because of an unexpected server error. A data error was encountered while processing the request. |
| 500 | 5308 | The request could not be fulfilled because of an unexpected server error. An error occurred when attempting to assign the library. |
| 500 | 5309 | The request could not be fulfilled because of an unexpected server error. An error occurred when attempting to list the libraries that are available to this session. |
| 500 | 5310 | The request could not be fulfilled because of an unexpected server error. The requested order for this table could not be set. |
| 500 | 5311 | The request could not be fulfilled because of an unexpected server error. An index is required in order to provide the requested ordering of the table. |
| 500 | 5312 | The request could not be fulfilled because of an unexpected server error. The requested ordering of the table resulted in a partial match. |
| 500 | 5313 | The request could not be fulfilled because of an unexpected server error. The requested library could not be deassigned. |
| 500 | 5333 | The request could not be fulfilled because of an unexpected server error. The user who made the request did not have permissions to open the file. |
| 500 | 5438 | The request could not be fulfilled because of an unexpected server error. The response items cannot be generated. |
| 500 | 5439 | The request could not be fulfilled because of an unexpected server error. The response links cannot be generated. |
| 500 | 5451 | The request could not be fulfilled because of an unexpected server error. The request failed to write the file. |
| 500 | 5702 | The request could not be fulfilled because of an unexpected server error. The job request has no associated SAS code. |
| 500 | 5703 | The request could not be fulfilled because of an unexpected server error. The SAS code that is associated with the job request is invalid. |
| 500 | 5704 | The request could not be fulfilled because of an unexpected server error. An error occurred while running the job. |
| 500 | 5705 | The request could not be fulfilled because of an unexpected server error. An error occurred when the job was submitted to the Compute service. |
| 500 | 5706 | The request could not be fulfilled because of an unexpected server error. There was no job condition code returned when the job completed. |
| 500 | 5707 | The request could not be fulfilled because of an unexpected server error. The job was canceled by the user with a RUN CANCEL statement. |
| 500 | 5708 | The request could not be fulfilled because of an unexpected server error. The job was canceled by a user with an ATTN or BREAK command. |
| 500 | 5709 | The request could not be fulfilled because of an unexpected server error. An error in the code has caused the session to enter syntax-check mode. |
| 500 | 5710 | The request could not be fulfilled because of an unexpected server error. The job has completed, but there are warning messages. |
| 500 | 5711 | The request could not be fulfilled because of an unexpected server error. The job was canceled by the user with an ABORT CANCEL statement. |
| 500 | 5712 | The request could not be fulfilled because of an unexpected server error. The job was canceled by the user with an ABORT CANCEL FILE statement. |
| 500 | 5713 | The request could not be fulfilled because of an unexpected server error. The SAS code that was submitted contained an error. |
| 500 | 5714 | The request could not be fulfilled because of an unexpected server error. An error occurred when polling the job state. |
| 500 | 5715 | The request could not be fulfilled because of an unexpected server error. There is no update link available from the job. |
| 500 | 5716 | The request could not be fulfilled because of an unexpected server error. The update link that is provided has not returned an updated job. |
| 500 | 5717 | The request could not be fulfilled because of an unexpected server error. No links were returned from the job. |
| 500 | 5721 | The request could not be fulfilled because of an unexpected server error. The Compute session has not returned any links. |
| 500 | 5722 | The request could not be fulfilled because of an unexpected server error. A specific link that is required from the session is missing. |
| 500 | 5723 | The request could not be fulfilled because of an unexpected server error. The Compute session returned incorrect variable information. |
| 500 | 5724 | The request could not be fulfilled because of an unexpected server error. The response that was returned from the Compute service could not be processed. |
| 500 | 5725 | The request could not be fulfilled because of an unexpected server error. The state link is missing from the job. |
| 500 | 5726 | The request could not be fulfilled because of an unexpected server error. The update link is missing from the job. |
| 500 | 5727 | The request could not be fulfilled because of an unexpected server error. The log link is missing from the job. |
| 500 | 5729 | The request could not be fulfilled because of an unexpected server error. The job link is missing from the session. |
| 500 | 5730 | The request could not be fulfilled because of an unexpected server error. The log link is missing from the job. |
| 500 | 5732 | The request could not be fulfilled because of an unexpected server error. Resources that are associated with the Files service could not be found. |
| 500 | 5733 | The request could not be fulfilled because of an unexpected server error. The content link for the Files service is missing. |
| 500 | 5736 | The request could not be fulfilled because of an unexpected server error. The createSession link is missing from the session. |
| 500 | 5740 | The request could not be fulfilled because of an unexpected server error. The job could not be completed because the Compute service terminated unexpectedly. |
| 500 | 5750 | The request could not be fulfilled because of an unexpected server error. The data provider was unable to find the requested libraries. |
| 500 | 5751 | The request could not be fulfilled because of an unexpected server error. The data provider was unable to find the requested data table. |
| 500 | 5752 | The request could not be fulfilled because of an unexpected server error. The data provider was unable to create a session. |
| 500 | 5753 | The request could not be fulfilled because of an unexpected server error. The data provider was unable to process the response from the service. |
| 500 | 5754 | The request could not be fulfilled because of an unexpected server error. The data provider was unable to process the collection response from the service. |
| 500 | 5755 | The request could not be fulfilled because of an unexpected server error. A session could not be created for the given resource. |
| 500 | 5757 | The request could not be fulfilled because of an unexpected server error. An error occurred when attempting to communicate with the session. |
| 500 | 5800 | The request could not be fulfilled because of an unexpected server error. The Compute service failed when communicating with another service or server. |
| 500 | 5801 | The request could not be fulfilled because of an unexpected server error. Specify a context value to update an object. |
| 500 | 5802 | The request could not be fulfilled because of an unexpected server error. Specify a context value to create an object. |
| 500 | 5806 | The request could not be fulfilled because of an unexpected server error. The service is unable to convert the property value to JSON. |
| 500 | 5807 | The request could not be fulfilled because of an unexpected server error. The service is unable to convert the property representation to JSON. |
| 500 | 5808 | The request could not be fulfilled because of an unexpected server error. The service is unable to deserialize the JSON value for a property. |
| 500 | 5809 | The request could not be fulfilled because of an unexpected server error. The service is unable to convert JSON to a property representation. |
| 500 | 5810 | The request could not be fulfilled because of an unexpected server error. Provide a context identifier for this GET request. |
| 500 | 5811 | The request could not be fulfilled because of an unexpected server error. Provide a context identifier for this DELETE request. |
| 500 | 5812 | The request could not be fulfilled because of an unexpected server error. Provide a context identifier for this UPDATE request. |
| 500 | 5814 | The request could not be fulfilled because of an unexpected server error. The access token for the user could not be obtained. Either the current thread is not executing in the context of a request, or the token has expired and could not be renewed. |
| 500 | 5816 | The request could not be fulfilled because of an unexpected server error. The launch type that you specified is unknown. |
| 500 | 5818 | The request could not be fulfilled because of an unexpected server error. There is no launcher context identifier in the launch properties. |
| 500 | 5819 | The request could not be fulfilled because of an unexpected server error. There is no launcher process identifier in the launch properties. |
| 500 | 5820 | The request could not be fulfilled because of an unexpected server error. There is no delete process link in the launch properties. |
| 500 | 5821 | The request could not be fulfilled because of an unexpected server error. The specified launch type is invalid. |
| 500 | 5822 | The request could not be fulfilled because of an unexpected server error. The service is unable to convert JSON to the required type. |
| 500 | 5823 | The request could not be fulfilled because of an unexpected server error. The service is unable to convert a value to JSON. |
| 500 | 5824 | The request could not be fulfilled because of an unexpected server error. The launch type that is associated with this launch is invalid. |
| 500 | 5825 | The request could not be fulfilled because of an unexpected server error. The launch type that is associated with the destruction of this launch is invalid. |
| 500 | 5827 | The request could not be fulfilled because of an unexpected server error. The context is missing the launcher context name or identifier. |
| 500 | 5830 | The request could not be fulfilled because of an unexpected server error. The SAS Compute Server process did not initialize in the time allowed. |
| 500 | 5831 | The request could not be fulfilled because of an unexpected server error. The service was interrupted while waiting for a process to start. |
| 500 | 5832 | The request could not be fulfilled because of an unexpected server error. The SAS Compute Server process terminated unexpectedly. |
| 500 | 5833 | The request could not be fulfilled because of an unexpected server error. The Launcher service was unable to launch the SAS Compute Server. |
| 500 | 5834 | The request could not be fulfilled because of an unexpected server error. The SAS Compute Server process is in an invalid state. |
| 500 | 5835 | The request could not be fulfilled because of an unexpected server error. A command is required for a service-based launch. |
| 500 | 5838 | The request could not be fulfilled because of an unexpected server error. Provide a non-null value for responseType or responseTypeRef. |
| 500 | 5840 | The request could not be fulfilled because of an unexpected server error. Provide a context request value. |
| 500 | 5843 | The request could not be fulfilled because of an unexpected server error. Specify a context name. |
| 501 | 5109 | The request could not be fulfilled because of an unexpected server error. The specified engine exists, but it does not support returning options. |
| 501 | 5763 | The request could not be fulfilled because of an unexpected server error. The given query parameter for paging is not supported. |