REST Server Error Messages and Resolutions

Another operation on this module is going on.

Wait a while, find out what has changed on the module, and then decide whether it is appropriate to retry your operation. If the problem persists even though you are sure there is not another simultaneous operation on the module, restart the server to refresh its state.

API version 2 is not supported.

The cause is that one or more fields in the module definition object are incorrect or repeated. Correct the errors identified.

Bad Request encountered. Check the format and syntax of the source.

Check the SAS Micro Analytic Service log file for additional details as there can be multiple causes for this error. If the cause is not that an incorrect source was used when updating a module, a restart of the server might be necessary to refresh its state. It might also be necessary to reduce the level of concurrent module update.

Code is missing or assigned the null value.

The cause is that one or more fields in the module definition object is incorrect or repeated. Correct the errors that are identified.

Data type does not match the signature.

Correct the input parameters according to the step's input signature.

Error creating object for HTTP response body.

If you submitted a POST, PUT, or DELETE operation to change the module collection, use the appropriate GET operation to check whether the operation produced the effect that is desired. If the desired effect is not produced, check the SAS Micro Analytic Service log for error messages. (Errors are logged as well as returned through the response body.) If you submitted a POST operation to validate the inputs of a step, execute a step or another GET operation. It is safe to repeat the operation.

Information about the steps in this public module is not available.

The cause of this error is too many simultaneous module creations or updates. Reduce the amount of concurrency.

Information about the steps in this public module is not available because module was compiled successfully before but failed recompilation this time.

The likely cause is that a dependent module is no longer available to recompile a module after the server restarts. Create the dependent module again.

Invalid source code.

The cause is either one or more compilation errors.

Label cannot be used together with start and limit.

Use either the label parameter or start and limit parameters in the GET operation on the modules or steps collections.

Metadata update failure.

Restart the server to go through the metadata correction procedure. Follow this with a GET operation on the module affected to see whether the module was created, updated, or deleted properly.

Module compilation failed with errors.

The cause is one or more compilation errors during re-compilation of a previously compiled module. This might be due to too many simultaneous module creations or updates. Reduce the amount of concurrency. A restart of the server might be necessary to go through the metadata correction procedure.

Module context was not created.

There can be multiple causes. A restart of the server might be necessary to refresh its state.

Module name cannot be changed from a PUT operation.

Use the same module name as the previous revision.

Module name cannot be determined.

If the source is DS2 code, the package does not have a name. Add a name to the package.

Module name XYZ is already taken.

Delete the existing module using that name, or choose a different module name when creating a module. If the error persists, this might be a symptom of incorrect metadata. A restart of the server might be necessary to go through the metadata correction procedure.

Module named XYZ already exists.

Delete the existing module using that name, or choose a different module name when creating a module. If the problem persists, restart the server to clear its state.

Module type XYZ is not valid. Valid value is text/vnd.sas.source.ds2.

The cause is one or more fields in the module definition object are incorrect or repeated. Correct the errors identified.

No module with the module ID XYZ exists.

Verify that the module ID is correct. If the module ID is correct, the module might have been deleted. In that case, create the module again and use the new ID that is assigned to it.

Private module named XYZ was not removed successfully.

This error can be left uncorrected, if XYZ does not pose a problem in the other operations of the server. Otherwise, restart the server to clear its state.

Scope is missing or assigned the null value.

The cause is that one or more fields in the module definition object is incorrect or repeated. Correct the errors identified.

Scope XYZ is not valid. Valid scopes are public and private.

The cause is that one or more fields in the module definition object are incorrect or repeated. Correct the errors identified.

Server encountered an internal error.

There can be multiple causes. Check the SAS Micro Analytic Service log for error messages. If the cause is compilation related, and the errors are on a dependent module, make sure that the dependent module exists. It can also be caused by too many simultaneous module creations or updates. In that case, reduce the amount of simultaneous module creations or updates. For other causes, a restart of the server might be necessary to refresh its state.

Server is not initialized properly.

There can be multiple causes. Check the SAS Micro Analytic Service log for more information. Correct the component that prevents the service from initializing properly.

Step ID XYZ failed to execute.

See SAS Micro Analytic Service Return Codes for the meaning of the result code. Also, verify that the module ID is correct and verify the existence of the module by doing a GET operation on the module.

Step ID XYZ is not visible.

The step is a member of a private module and its information is hidden from you. Furthermore, you cannot execute this step. If you need to see the signature of this step, you can get the source of the module as an alternative.

The XYZ member is repeated.

The cause is that one or more fields in the module definition object are incorrect or repeated. Correct the errors identified.

The XYZ property expects a string value but TYPE value is provided.

The value of a property should be a string. Change the value to a string by quoting the value in double quotation marks.

The XYZ property is not supported.

The only property that is allowed in the API is connectionString. Remove the property definition from the array.

There is more than one DS2 package in the code.

Provide only one DS2 package in a module definition.

This node is out of sync with the rest of the cluster.

The likely cause is network delay in replicating data from one node to its cluster peers. Another operation on the module on the node that has the up-to-date metadata might cause a correction of the module on the peer nodes. If that does not work, restart the cluster node to go through the metadata correction procedure.

Total number of input parameters (number) does not match the number of parameters required by input signature (number).

Correct the input parameters according to the step's input signature.

Type is missing or assigned the null value.

The cause is that one or more fields in the module definition object is incorrect or repeated. Correct the errors identified.

User context was not created.

There can be multiple causes. A restart of the server might be necessary to refresh its state.

Version is missing or assigned the null value.

The cause is that one or more fields in the module definition object are incorrect or repeated. Correct the errors identified.