LANDP MSR/E Device Service exceptions

The LANDP(R) MSR/E Device Service throws the following exceptions, all of them subclasses of LandpException:
Table 1. LANDP MSR/E Device Service exceptions
Exception Reasons/Actions
DeviceErrException An error occurred while the device was being accessed. This includes hardware failures, transmission errors, etc.

Action: Run a diagnostic program for the device. Examine the src (server return code) field of the exception object, and refer to the LANDP problem determination documentation.
InternalErrException The service received an unexpected return code from the LANDP server. This exception should never be thrown since the service supports all the documented return codes.

Action: Check that you are using the correct LANDP server.
IntervReqException User intervention is required. The device might be off-line, the cable might be disconnected, etc.

Action: Examine the src (server return code) field of the exception object, and refer to the LANDP problem determination documentation.
NoLandpException LANDP has not been loaded: a session with the supervisor could not be initiated. This exception is thrown from the constructor of the service.

Action: Initialize the LANDP environment.
ProgrammingErrException The length of the data to be read or written is not valid.

Action: Set the length of the data to be read or written between the limits supported by the device.
RouterErrException The LANDP server could not be reached.

Action: Check that the LANDP is correctly started, and check that your LANDP configuration contains the server you are trying to access. Examine the rrc (router return code) field of the exception object, and refer to the LANDP problem determination documentation.