Category: InterSystems Cache & Ensemble

InterSystems Cache & Ensemble Error 5943 – SCRIPT LANGUAGE=SQL tag cannot have both NAME and CURSOR att

In this blog post, let’s learn about the error message “5943 SCRIPT LANGUAGE=SQL tag cannot have both NAME and CURSOR att” in InterSystems Cache & Ensemble and the description of the error message. Error Message 5943 – SCRIPT LANGUAGE=SQL tag cannot have both NAME and CURSOR att Error Details SCRIPT LANGUAGE=SQL tag cannot have both NAME and CURSOR attribute on line %1.

InterSystems Cache & Ensemble Error 6089 – CONNECT command to proxy ‘%1’ failed with response ‘%2’.

In this blog post, let’s learn about the error message “6089 CONNECT command to proxy ‘%1’ failed with response ‘%2’.” in InterSystems Cache & Ensemble and the description of the error message. Error Message 6089 – CONNECT command to proxy ‘%1’ failed with response ‘%2’. Error Details CONNECT command to proxy ‘%1’ failed with response ‘%2’.

InterSystems Cache & Ensemble Error 6322 – Unsupported value of IncompleteSequenceBehavior in CreateSeq

In this blog post, let’s learn about the error message “6322 Unsupported value of IncompleteSequenceBehavior in CreateSeq” in InterSystems Cache & Ensemble and the description of the error message. Error Message 6322 – Unsupported value of IncompleteSequenceBehavior in CreateSeq Error Details Unsupported value of IncompleteSequenceBehavior in CreateSequenceResponse message: %1.

InterSystems Cache & Ensemble Error 6649 – Cannot generate code for class %1 because depends on class %

In this blog post, let’s learn about the error message “6649 Cannot generate code for class %1 because depends on class %” in InterSystems Cache & Ensemble and the description of the error message. Error Message 6649 – Cannot generate code for class %1 because depends on class % Error Details Cannot generate code for class %1 because depends on class %2 which cannot be…

InterSystems Cache & Ensemble Error 6290 – Dataset schema must be in XML input if %XML.Dataset is not t

In this blog post, let’s learn about the error message “6290 Dataset schema must be in XML input if %XML.Dataset is not t” in InterSystems Cache & Ensemble and the description of the error message. Error Message 6290 – Dataset schema must be in XML input if %XML.Dataset is not t Error Details Dataset schema must be in XML input if %XML.Dataset is not typed.

InterSystems Cache & Ensemble Error 7316 – Unable to create directory for storing the log file: %1

In this blog post, let’s learn about the error message “7316 Unable to create directory for storing the log file: %1” in InterSystems Cache & Ensemble and the description of the error message. Error Message 7316 – Unable to create directory for storing the log file: %1 Error Details Unable to create directory for storing the log file: %1

InterSystems Cache & Ensemble Error 1027 – Cluster shadowing request denied: database server %1 is not

In this blog post, let’s learn about the error message “1027 Cluster shadowing request denied: database server %1 is not “ in InterSystems Cache & Ensemble and the description of the error message. Error Message 1027 – Cluster shadowing request denied: database server %1 is not Error Details Cluster shadowing request denied: database server %1 is not part of a cluster

InterSystems Cache & Ensemble Error 168 – That doesn’t match the next pointer node in the pointer bloc

In this blog post, let’s learn about the error message “168 That doesn’t match the next pointer node in the pointer bloc” in InterSystems Cache & Ensemble and the description of the error message. Error Message 168 – That doesn’t match the next pointer node in the pointer bloc Error Details That doesn’t match the next pointer node in the pointer block, which is %1.

InterSystems Cache & Ensemble Error 256 – Block #%1 changed during integrity check, might be OK, check

In this blog post, let’s learn about the error message “256 Block #%1 changed during integrity check, might be OK, check” in InterSystems Cache & Ensemble and the description of the error message. Error Message 256 – Block #%1 changed during integrity check, might be OK, check Error Details Block #%1 changed during integrity check, might be OK, check should be rerun for this global