Interoperability Testing
Interpreting FTAM Errors
Interpreting FTAM Errors
Table
1.Check the field labeled “Diagnostic”.
If this field is present, look for a text string labeled “further details” for the cause.
2.Look at the line after “FAILED”. The operation that failed is listed.
Table | FTAM Call Errors |
| ||
|
|
|
|
|
|
| FTAM Call | Reason | Corrective Action |
|
|
|
| |
| ft_aeactivation() | FTAM not correctly | Run swverify on the FTAM | |
|
|
| installed. | fileset to verify that all |
|
|
|
| components are installed. |
|
|
|
|
|
|
|
| OTS stack not up. | Run the Status operation |
|
|
|
| under Session or Transport to |
|
|
|
| verify. |
|
|
|
| |
| ft_connect() | Incorrect address | Recheck the value of the | |
|
|
| specified. | Presentation address specified |
|
|
|
| and the value configured for |
|
|
|
| the remote. |
|
|
|
|
|
|
|
| Incorrect User ID. | Check user name and |
|
|
|
| password, usually corresponds |
|
|
|
| to the remote. |
|
|
|
|
|
|
|
| Remote stack not up. | Recheck stack. |
|
|
|
|
|
|
|
| Responder not running. | Repeat the verification |
|
|
|
| described in the |
|
|
|
| section. |
|
|
|
|
|
|
|
| Lower Layer Problem. | Go back to the step you were |
|
|
|
| on and continue. |
|
|
|
| |
| ft_select() | Incorrect source file | Check the source file name | |
|
|
| name. | and correct. |
|
|
|
|
|
16 | Chapter 1 |
