Impact: This advisory afffects all ISIS enabled applications.

The following bulletin was posted on the isisdev-l list on 9/12/2006.

Hi all,

We have been receiving reports that applications are seeing increased number of 700001 errors.

In almost every case, this error is triggered because applications sends us a zero length ticket string.

In ISIS 4, depending on the condition, ISIS either returned 700001 or 604010 for this missing ticket case. Because the reporting behavior of 604010 error has changed (we no longer produce a fatal error when the user’s IP’s did not match.), all zero length string cases have been moved to 700001.

You can very easily avoid this error in almost all cases by perform a simple ticket string length check before submitting it to ISIS.
Submitting a zero length is meaningless since it will never yield a valid session response.

Another case where 70001 error occurs is when you do not supply a SOAP header at all in your soap call. In ISIS 4, the SOAP 1.0 parser required a SOAP header. If you did not supply a header, a SOAP exception was thrown before the ISIS code ran. In ISIS 5, the SOAP 1.1 parser does not check for the presence of a header, so if your call was missing the SOAP header, we returned a 700001 error. Yup. Basically, 700001 is a null reference, or missing expected data error.

So if you are receiving excessive number of 700001 errors, please double check your application for these conditions.