| See also |
The table below lists the error codes that can be generated by the methods of the cNISRbRscLink class.
| Error Name | Value | Description |
|---|---|---|
| eDdaOpenLink | 1000 | An attempt to connect to the Remote Basic Server failed. This could be due to incorrect connection details (system, database, user-id, or account), a valid user-id may not be enabled for server connections, or there might be network problems. |
| eDdaCloseLink | 1001 | An attempt to close the server connection failed. This error normally only occurs if the PC's network subsystem fails. |
| eDdaLinkNotOpen | 1005 | The CallSubroutine method was called without first connecting with the OpenLink method. |
| eRscParamNo | 1015 | The value of the CallSubroutine numParams parameter is invalid (less than 0 or greater than 20). |
| eRscCallSubroutine | 1016 | The CallSubroutine method failed. This might be due to network problems or in the execution of the Databasic subroutine. |
| eInitialize | 1090 | Failed to initialise the cNISRbRscLink object. |
Note: Other error codes are provided that are not used in the current implementation.
If an error occurs, the properties of the Err object are set to the following:
Number property An error number composed of a base error number, vbObjectError, plus the actual error value; vbObjectError is equal to -2147221504 (&H80040000). You can obtain the actual error value as follows:
rbErrorNumber = Err.Number - vbObjectError
For example, if an eDdaLinkNotOpen error occurs, the number property of the Err object will be set to -2147220499. The actual error number is therefore -2147220499 - vbObjectError = 1005 (eDdaLinkNotOpen).
Source property Always set to "NISRbDataLink.cNISRbRscLink".
Description property
Depends on the problem see Likely Errors below.
In VB.NET, you can use unstructured error handling as in Visual Basic 6 (described above), or structured error handling using the Try...Catch...Finally statement. In the latter case, an cNISRbRscLink error is available in a Runtime.InteropServices.COMException object. The ErrorCode property of this object contains the error number and the Message property the error description. The VB.NET example illustrates this.
| Error Name | Description property of Err object | Cause |
|---|---|---|
| eDdaOpenLink | Error in OpenLink [ 11001] Authoritative Answer: Host not found |
Invalid system name. |
| eDdaOpenLink | Error in OpenLink [ 11103] Transport Error : Receive Failure |
Invalid user-id, password, account or account password. |
| eDdaLinkNotOpen | Link not open | There is no connection to the Reality database. |
| eRscParamNo | "CallSubroutine 'name', error - invalid number of parameters" | The value of the CallSubroutine numParams parameter is invalid (less than 0 or greater than 20). |
| eRscCallSubroutine | CallSubroutine 'subroutineName' error External Basic interface error. Out of range parameter number num received by External Basic, allowed range is num1 to num2. |
The value of the CallSubroutine numParams parameter is greater than the number of parameters expected by the DataBasic subroutine. |
| eRscCallSubroutine | CallSubroutine 'subroutineName' error External Basic run time error... |
The number of parameters supplied is less than the number of parameters required by the DataBasic subroutine. or The value of the CallSubroutine numParams parameter is less than the number of parameters required by the DataBasic subroutine. or An error has occurred in the DataBasic subroutine. |
Note: If a network error occurs, the Description property of Err object will contain a string with the format
errorDescription [ lowerLevelErrorNumber] lowerLevelErrorText
lowerLevelErrorText will be one of the errors listed in the Error Messages section of PCi Standard Network Interface. For example:
Error in OpenLink [ 11103] Transport Error : Receive Failure