|
|
|
|
|
This section outlines known issues and typical workarounds for MOVEit Transfer 2017 PLUS.
2017 Service Pack 1 (SP1). Issues identified for current MOVEit Transfer release.
This section outlines known issues and typical workarounds for MOVEit Transfer 2017 PLUS Service Pack 1.
ID |
Category |
Known Issue in MOVEit Transfer 2017 PLUS |
MBL-2659 |
Mobile Server |
Certain mobile server names can trigger a faulty URL redirect (to To work around this, avoid deploying MOVEit Mobile with hostnames that begin with the string prefix "mobile" For example:
|
MBL-2652 |
Mobile Server |
A freshly deployed MOVEit Transfer Mobile Server is configured to allow fallback to TLS 1.1 or 1.0 depending on the connection negotiated with the client. However, PCI and other data security standards require or recommend strict use of TLS 1.2. To configure MOVEit Transfer server to use TLS 1.2 connections with clients:
|
MBL-2661 |
Mobile App |
When sending a package, MOVEit Transfer Client App for Android might crash when loading certain contact lists at package composition time. Workaround: enter contact manually or use contacts from MOVEit Transfer user account. |
2017 Plus. Issues identified from last full release.
This section outlines known issues and typical workarounds for MOVEit Transfer 2017 PLUS.
ID |
Category |
Known Issue in MOVEit Transfer 2017 PLUS |
MIDMZ-7593 |
Wizard |
On some Windows computers, the Java Wizard might not be able to display characters for the Tamil language. This is caused by a limitation of Java. |
MIDMZ-9090 |
MFA pairing |
The SysAdmin can enable multi-factor Authentication using the Authenticator App in the MY ACCOUNT settings, but only when working in the system organization. If acting as administrator of another organization, the MFA setup will fail. |
DEP-3819 |
Upgrade/Licensing |
When updating to 2017Plus, the latest installer overwrites the registry key location. This affects your environment if you already edited the registry for the purposes of moving your license file (to reside on a fileshare, for example). To work around this, you can either:
|
DEP-3790 |
Install |
MOVEit Transfer server installation can fail because of a dependency on the SQL Native Client. If a message during install indicates the SQL Native Client installation failed, apply this client from Microsoft at the Windows Server machine where you installed MOVEit Transfer and then re-run the MOVEit Transfer installation. |
DEP-3850 |
Install |
MOVEit Transfer shows SysStat application errors due to uncaught Known Issue in MOVEit Transfer 2017 PLUSexception. This can happen if a process that tries to get system status (SysStat) throws an unhandled exception when you deploy MOVEit Transfer and use an existing IIS server. |
DEP-3851 |
Install |
Startup fails with error "Could not load all ISAPI filters for site 'MOVEIT2017PLUS'". This occurs because an existing IIS server does not load the ISAPI filters because they are 32-bit binaries and in this case IIS expected 64-bit binaries. |
DEP-3675 |
Installer - Download Agent |
The new MOVEit Transfer bootstrap installer downloads the latest product packages and dependencies. In cases where the MOVEit Transfer Installer exits before the downloader agent attempts to download a package from the Product Distribution CDN, you might see an outgoing connection request. |
Internet Explorer |
Install |
MOVEit Transfer Online Help does not open after install on a fresh server. You must add docs.ipswitch.com to the Trusted Sites list. |