SSO Runtime Error Messages |
DEVELOPER |
The following SSO errors messages may be encountered at runtime:
Number |
Error |
Description |
830 |
UNABLE TO CREATE SSO <tagname> |
The current PROIV function is unable to automatically create the specified SSO at the end of function entry. This is typically because the PROIV Virtual Machine cannot find the Java class for the SSO in the directories specified in the pro4v[n].ini file SSO_JARPATH entry. |
831 |
UNABLE TO INITIALISE OR CALL JVM |
The PROIV Virtual Machine is unable to start the Java Virtual Machine. This is typically an installation issue, please contact PROIV Support for assistance. |
832 |
SSO PARAMETER <tagname> IS UNDEFINED |
This error occurs if a PROIV function expects an SSO parameter, which the calling PROIV function failed to supply. Check the PROIV function interface maps. |
833 |
SSO SET PROPERTY <tagname.property> FAILED |
An SSO set property call generated an exception. Examine the Automatic Rollback Alert windows for more information. |
834 |
SSO GET PROPERTY <tagname.property> FAILED |
An SSO get property call generated an exception. Examine the Automatic Rollback Alert windows for more information. |
835 |
SSO METHOD CALL <tagname.property> FAILED |
An SSO method call generated an exception. Examine the Automatic Rollback Alert windows for more information. |
836 |
MISMATCHED SSO PARAMETER COUNT IN FUNCTION CALL |
This error occurs if the SSO parameter count expected by a called PROIV function failed to match the number of SSO parameters supplied by the PROIV calling function. Check the PROIV Function interface maps. |
838 |
SSO_JARPATH CONTENTS ARE INVALID |
This error indicates that the PROIV Virtual Machine has encountered a problem when reading the directories specified by SSO_JARPATH in the pro4v[n].ini file. |
839 |
SSO METHOD CALL <tagname.property> RETURNED UNEXPECTED TYPE |
Examine the rollback details for more information. Typically, a method call is expected to return a numeric value, and could feasibly return a non-numeric value. This occurs if the signature for this method in the SSO Gallery does not match the signature of the method called at runtime, for example, a mismatch between the JAR file versions. |
Topic ID: 500581