Limagito File Mover Software Blog and Filemover News

18 Dec
Azure azcopy %1 is not a valid Win32 application
azcopy %1 is not a valid Win32 application. System Error, Code: 193.
We received feedback from a customer who was trying to use the Microsoft tool AzCopy v10.16.2 in our Azure as Destination, but couldn’t get it to work. He always received this ‘%1 is not a valid Win32 application’ error when trying. In our Azure as Destination we added the possibility to use AzCopy to do the actual transfer where we use the command line tool in the background to achieve this. The reason he got this error was because an empty file named ‘azcopy’ existed next to the actual command line tool ‘azcopy.exe’. So when we tried to use the command ‘azcopy copy …’ it tried to execute this empty file. In version v2023.0.12.18 we changed ‘azcopy copy …’ to ‘azcopy.exe copy …’ as command to eliminate this.
This customer was also using a # in his filenames because of: “the # characters are contained in the file name as it’s a documented standard file format ( NEM12 national energy market format)”.
So we made another change in version v2023.0.12.18 which encodes the filenames in the AzCopy command since it seems AzCopy is not doing this automatically.
#FileTransfer #azure #azcopy
If you need any info about this ‘azcopy %1 is not a valid Win32 application’ error, please let us know.
Best regards,
Limagito Team
By Limagito-Team Azure %1
20 Nov
Limagito File Mover as image converter to many different formats
Image converter to many different formats using Limagito File Mover Version v2023.0.11.20.
Do you know that our File Mover tool is able to convert a loaded image file to another format. The setup of such an automated task is really easy.
Search for an image file using one of our Source options
Add IMG (Image) as Destination
Add Output Action within this IMG Destination
Enable ‘Change File Extension’ and add the format file extension you need. For example: .png
Done
Some file types we currently support as export: Jpeg, Jpeg2000, PNG, TIFF, BMP, WBMP, PS, PDF, PCX, DCX, TGA, PXM, ICO, HDP, GIF, DICOM, …
Regarding IMG (Image) as destination, we are always open to new ideas so please let us know.
On our roadmap currently we have:
Parameters (Compression, Quality, ..)
EXIF Metadata
Some screenshots to get you started:
Please add WIN as source to scan a Windows folder for images (can be any other Source too):
In this example we only want to convert .jpg files, so add a File Name Include filter:
Add ‘IMG’ (Image) as Destination:
In this destination:
Select ‘Output to File’ as new Action and click the <Add> button
In the Image Actions listbox (on the left) select the newly added ‘Output to File’ action
An extra tab ‘Output’ will appear in the top menu, select this tab
Enable ‘Change File Extension’ and add the format extension you want to convert to ( .png, .bmp, .tiff, …):
Enable the Rule and wait on the scan event or trigger manually:
RunTime Log Result:
Image properties of the converted image:
#FileTransfer #image #imageconverter
If you need any info about this new ‘image converter’ option, please let us know.
Best regards,
Limagito Team
By Limagito-Team Image converter, image converter
07 Nov
POP, IMAP and SMPT with OAuth2 (Microsoft Office 365 services)
POP, IMAP and SMPT with OAuth2 (Microsoft Office 365 services)
Microsoft is disabling basic authentication for Microsoft Office 365 services on October 2022.
The simplest solution that will not require any major changes to your setup is to have your Outlook/Exchange users turn on 2-step verification in their accounts and then generate application-specific passwords. Otherwise, you will have to update your settings to use OAuth2 when connected to Outlook/Exchange. In this case the username stays the samen but you’ll get a new application-specific password.
The second solution is using OAuth2 as described in the following example: link
#FileTransfer
Best Regards,
Limagito Team
By Limagito-Team 365 IMAP4 365