Quickload Functionality (Started via ECI From an Interface) With WebStart Java Client Leads To Error: '... FileServer Client not found or no access'
(Doc ID 2033223.1)
Last updated on JUNE 21, 2018
Oracle Agile Engineering Data Management - Version 220.127.116.11 and later Information in this document applies to any platform.
On Oracle Agile e6.1.3 with the Webstart Java Client Find that when one loads files from (for example) the CATIA interface with the quick load functionality (eci_loa_cax and eci_cko_fil_lst), the files are not checked out to the mentioned directory. An error message like this is written in that case to the Java Client message window: -- [7:47 AM] "Lade Process ist gestarted ..." [7:47 AM] "Z0762142.CATProduct wird gelesen ..." [7:47 AM] axalant_root ist nicht gesetzt! [7:47 AM] axalant_root ist nicht gesetzt! [7:47 AM] Datei "Z0066472.CATPart" konnte nicht kopiert werden! [7:47 AM] Server-Meldung: FMS-Interface: FileServer Client not found or no access:
The fms_cli_vc10.exe is located locally in the interface folder and the local environment variable FMS_CLIENT points to it correctly.
Expected Behavior: ============ No error message should appear and the files should be checked out correctly.
What is Working: ============= If the Fileserver Client was started before by any other action and the FMS_TIMEOUT is not yet over, the checkout works correctly as the Fileserver Client is still running. Furthermore if the local Java Client is used instead of the Webstart Java Client the issue does not happen either. Checkout with the standard check out functionality works fine as well.
The issue can be reproduced at will with the following steps: ==================================== 1. Start Webstart Java Client 2. Start eci_test_vc10.exe and connect to the started Webstart Java Client 3. Execute following function to gather the files to download in T_CAX_FIL_TMP: eci_loa_cax EDB-DOCUMENT DRAWING EDB-DOC-DRW-TLI off list bat off off T_DOC_DAT.DOCUMENT_ID . DOCUMENT-001 . . . off on . NORMAL Y DFM_LOCAL N .
3. Now try to download the files gathered in T_CAX_FIL_TMP by passing the correct Structure_ID returned from eci_loa_cax (example: Structure_ID=19) eci_cko_fil_lst 19 C C:\temp
Result are the following error messages in the Java Client message window (files are not checked out): axalant_root isn't set! axalant_root isn't set! File "file name.ext" could not be copied! Server Message: FMS-Interface: FileServer Client not found or no access:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!