TIBCO Managed File Transfer Platform Server for Windows 8.0.0 hotfix-005 is now available
book
Article ID: KB0101706
calendar_today
Updated On:
Products
Versions
TIBCO Managed File Transfer Platform Server for Windows
8.0.0
Description
Hotfix TIB_mftps-win_8.0.0_HF-005 can be downloaded from TIBCO Support Portal (https://support.tibco.com).
You will need to provide your TIBCO Support Portal credentials. Once logged in you can download the hotfix by selecting the “Downloads” -> “Hotfixes” option. Then go to “/AvailableDownloads/MFT/ PlatformServer/Windows/8.0.0/hotfix-05” to download the hotfix.
The .zip file has the Readme file inside. Please unzip the file and review the Readme file for instructions on how to apply the hotfix.
Introduction
Hotfixes are cumulative. This is the fifth hotfix for TIBCO Managed File Transfer Platform Server for Windows 8.0.0.
================================================================================ Closed Issues in 8.0.0_HF-005 (This Release)
PSW-805 When a directory send transfer failed, the audit record was incorrectly written with "TemporaryError=Yes".
PSW-801 Transfers initiated by Platform Server for IBMi that used DES, 3DES, Blowfish or BlowfishLong encryption caused a corrupt file.
PSW-763 User Profile and Responder Profile passwords earlier used a proprietary encryption algorithm; now the passwords use AES encryption. Note: This issue was resolved in hotfix 8.0.0_HF-001 but was not included in the readme.
================================================================================ Closed Issues in 8.0.0_HF-004
PSW-794 Under high volume conditions, memory utilization grew rapidly, eventually leading to an Out of Memory condition.
================================================================================ Closed Issues in 8.0.0_HF-003
PSW-789 Memory leak when the Collector executed and there were more than 500 Audit records to collect. PSW-787 Network folder name cannot be saved in DNI scan directory due to access restrictions of logged on user account.
PSW-786 Platform Server for z/OS detected a network error when PSW issues a Send Command request
PSW-785 MFTCC initiated PSW to PSZ transfers with AES encryption failing with error message "Encrypt does not meet HIPAA regulations".
PSW-783 A CRC Validation Error Message was displayed in the EventViewer even though CRC checking was not enabled.
PSW-782 Added additional debug trace entries to the directory list program
PSW-772 Command Center initiated directory transfers did not honor the StopOnFailure parameter.
================================================================================ Closed Issues in 8.0.0_HF-002
PSW-769 Tunnel transfers failed when HIPAA=Yes was defined in the node definition.
PSW-768 When a user set the Using SSL field to "SSL" in the the Add Platform Node or Update Platform Node page of TIBCO Managed File Transfer Command Center, the node definition was created as TLS tunnel node instead of SSL node.
PSW-776 The TLS session negotiation failed when elliptical curve ciphers were used in the SSL or tunnel mode.
PSW-771 Responder transfers failed because of an intermittent service exception.
PSW-752 When the server status was checked from TIBCO Managed File Transfer Command Center, it did not show the version of TIBCO Managed File Transfer Platform Server for Windows.
================================================================================ Closed Issues in 8.0.0_HF-001
PSW-751 An exception was received when executing the fusping utility program.
PSW-750 File transfers failed due to intermittent exceptions when reading the cfnode.cfg file.
PSW-746 When the FUSUTIL MKDIR command was executed, an "Access Denied" error could occur if a directory in the path could not be accessed.
PSW-744 Earlier the "SSLV3" protocol option could be selected on the SSL Settings page. Now the "SSLV3" protocol option is removed from the SSL Settings page to disallow SSLV3.
PSW-742 When the "CRC Checking" field was set to "No" in the Add Platform Node page or Update Platform Node page, the CRC value in the node definition was incorrectly shown as "Default".