Limagito File Mover Software Blog and Filemover News

29 Nov

Q&A 32: Error during sftp file upload with Limagito File Mover

Q: We have installed Limagito version v2020.11.21.0 with the Site+ license on a W2K19 server. When we try to transfer files to an external sftp server it doesn’t work out fine (Error during sftp file upload). The SSH connection seems fine to me , but the files won’t be uploaded. Unfortunately the other side can’t help me out and I can’t find out what is happening and why.

25-11-2020 19:39:31 [SFTP] SFTPUploadFile, CK UploadFileByName Error, ChilkatLog:

[SFTP]   UploadFileByName:
[SFTP]     DllDate: Jul  2 2020
[SFTP]     ChilkatVersion: 9.5.0.83
[SFTP]     UnlockPrefix: CPSFTB.CB1062022
[SFTP]     Architecture: Little Endian; 64-bit
[SFTP]     Language: Delphi DLL
[SFTP]     VerboseLogging: 0
[SFTP]     SshVersion: SSH-2.0-XpertSuite
[SFTP]     SftpVersion: 4
[SFTP]     Component successfully unlocked using purchased unlock code.
[SFTP]     uploadFileByName:
[SFTP]       remoteFilePath: /XX/XX_2020-11-24_08-00-00-werknemers.xml
[SFTP]       localFilePath: \\MyDomain\proces\XX_2020-11-24_08-00-00-werknemers.xml
[SFTP]       localFileSize: 4485
[SFTP]       sftpOpenFile:
[SFTP]         remotePath: /XX/XX_2020-11-24_08-00-00-werknemers.xml
[SFTP]         access: writeOnly
[SFTP]         createDisposition: createTruncate
[SFTP]         v3Flags: 0x1a
[SFTP]         buildLongPath_xFilePath: \\MyDomain\proces\XX_2020-11-24_08-00-00-werknemers.xml
[SFTP]         Sent FXP_OPEN
[SFTP]         StatusResponseFromServer:
[SFTP]           Request: FXP_OPEN
[SFTP]           InformationReceivedFromServer:
[SFTP]             StatusCode: 5
[SFTP]             StatusMessage: Error while parsing request.
[SFTP]           --InformationReceivedFromServer
[SFTP]         --StatusResponseFromServer
[SFTP]       --sftpOpenFile
[SFTP]       Failed to open file.
[SFTP]     --uploadFileByName
[SFTP]     Failed.
[SFTP]   --UploadFileByName
[SFTP] --ChilkatLog

25-11-2020 19:39:31 [SFTPPUT] Copy Error \\MyDomain\proces\XX_2020-11-24_08-00-00-werknemers.xml

A: It’s look like the SFTP server is trying to use SFTP Version v4 but .. not correctly. The solution here is to only allow SFTP Version v3.

FYI: The customer is using our Second SFTP Vendor (CK).

Limagito File Mover SFTP v3 Only

Feedback from customer:

Great !! that did the trick. J J J
Thanks for your support !!!

If you need any help with this ‘Error during sftp file upload’, please let us know.

Best Regards,

Limagito Team

25 Nov
Added SharePoint OAuth2 Authentication in Limagito File Mover
Added SharePoint OAuth2 Authentication
Update 28th September 2023, our advice is to use Oauth v2.0 Authentication instead
In version v2020.22.25.0 we added OAuth2 Authentication as a fourth method for connecting to SharePoint.
Please select ‘Online Authentication using OUath2’ as Authentication Type (Setup Tab). After selection the OAuth2 Tab will be visible.
We received the following information from the customer (thank you Brad):
Client Id
Client Secret
Redirect URI

Update March 2022
We had a user getting the following error when trying to Get the OAuth2 Token: AADSTS70000
He had to change App Domain to: www.localhost.com
and
Redirect URI to the Site url (without the default.aspx at the end) in the SharePoint Application setup AND Limagito OAuth2 setup
We used the information from the customer and added them in the OAuth2 Setup:
Client ID
Client Secret
Scope, we used Web.Manage
Redirect URI
Next, click <GET>
At this moment we’ll start a request for the Realm and Principal ID of the SharePoint Site. A Dialog will appear with information about the next step.
Now you’ll need to click ‘Trust It’ to continue to the next step:

The Authorization Code will appear in the address bar of your browser.
Please COPY / PASTE this complete URL (https://…) in the ‘Auth Code’ field of the OAth2 Setup screen. We’ll strip the part we need and trigger a request for a Refresh and Access token. The response will be added to the ‘Refresh Token’ and ‘Access Token’ field of the OAuth2 setup.
Please click <Save> to save these Tokens which we’ll need to connect.
If you need any help with our ‘SharePoint OAuth2 Authentication’ option, please let us know.
Best Regards,
Limagito Team
By Limagito-Team SharePoint AADSTS70000, OAuth2, SharePoint
22 Nov
Submit a Base64-encoded order HL7 message with Limagito File Mover
A while ago we received the following question from William: “Is it possible to submit a Base64-encoded order HL7 message”. Since we already had HTTP as Destination, we decided to add this as an extra feature. Available in version v2020.11.21.0
We recieved the following information from the user:
submitOrder
The submitOrder method allows you to submit a Base64-encoded order HL7 message to the Data Exchange. The order can be either a Basic Lab Order or a Patient Service Center (PSC) Hold Order.
Endpoint
You must use the HTTP POST method to submit orders to the endpoint shown below, where domain specifies the Data Exchange environment.
POST https://domain/rest/orders/v1/submission
Request: The Base64-encoded order HL7 message as text/plain format
{“TVNIfF5+XCZ8Q1RGV3w5NzUwMjg0MHx8TkVMfDIwMT…”}
Response: The Base64-encoded order acknowledgment (ACK) HL7 message as text/plain format
As Source we’ll have HL7 order file (not encoded yet) which looks like (it’s just an example):
MSH|^~\&|INSTPROG|50203311|1111|MET|19980630080040||ORM^O01|MSG00001|P|2.3| PID|1||28514753||Joan^Howard^J||196303241225|F SAC|991912376^EXTLAB|01039421^THISLAB|092321A^LAS|092321^LAS||SER|19980620080037|R^PROCESS COMPLETED ORC|RE|5212498721A|||||^^^^^R OBR|1|5212498721A||2951-2^SODIUM^LN|||199807240826||||||||SER OBX|1|NM|2951-2^SODIUM^LN||24.3|ug/g||N
What this new ‘Content File as HL7 order’ option will do is:
Strip the Message Control ID from the source HL7 file which is MSH.10 (i.e. MSG00001)
Base64-Encode the complete content of the file
Place the Base64-Encoded content between JSON quotes like {“Base64-encoded content”}
i.e. {“TVNIfF5+XCZ8Q1RGV3w5NzUwMjg0MHx8TkVMfDIwMT…”}
Post the result as text/plain format to the domain
Check the Response, Result Code = 200 => OK
Base64-Decode the content of the Response and check MSH and MSA
22/11/2020 9:16:14 Check Result Code: 200, True 22/11/2020 9:16:14 PostHTTP, ContentFileAsHL7order Response Data Decoded as HL7 MSH: MSH|^~\&|1111|MET|INSTPROG|50203311|20201122081613||OOR^O02|MSG00001|P|2.3||||| 22/11/2020 9:16:14 PostHTTP, ContentFileAsHL7order Response Data Decoded as HL7 MSA: MSA|AA|MSG00001|2916c40402e141b9b07d701671c5019d||
Compare the Message Control ID from the Request with the Message Control ID from the Response
Both should be the same => OK
When different: Error
Check the Acknowledgment Code MAS.01
AA: Application Acknowledgment: Accept => OK
AE: Application Acknowledgment: Error
Interesting link
Some screenshot to get you started:
In our example we have a WIN as Source. The source file will be a HL7 order file (Example1.hl7).
As Destination we selected HTTP:
HTTP Setup:
Set Request to POST
Set Content Selecton to: Content File as HL7 order
Set %SFP%SFN as Content File
%SFP: Source File Path (i.e. C:\Test\IN_HL7\)
%SFN: Source File Name (i.e. Example1.hl7)
Leave Content-Type empty (default = text/plain)
Content of the Example1.hl7 file:
RunTime Log Result:
If you need any help with our ‘submit Base64-encoded order HL7 message’ option, please let us know. Also, other HL7 related feature requests are welcome.
Best Regards,
Limagito Team
By Limagito-Team HL7 HTTP REST Base64, HL7, submitorder