Known Issues, Tips, and Workarounds

This section outlines known issues and typical workarounds for MOVEit Transfer 2018.

ID	Category	Known Issue in MOVEit Transfer 2018
MIDMZ-9145	Mobile Server	Mobile URLs do not resolve correctly with MOVEit Mobile deployments using IIS virtual directory names. This is caused because the virtual directory name is being included in the pathname appended to the MOVEit Mobile Server URL. For example: Expected (correct) Mobile Server URL and path: https://www.example.com:8443/mobile/switch Actual (incorrect) Mobile Server URL and path: https://www.example.com:8443/myvirtualfolder/mobile/switch To workaround this and remove the virtual folder name from the orgs MOVEit Mobile path. As system administrator (sysadmin user) you can adjust the default URL that MOVEit Mobile uses in the System Organization profiles.
MIDMZ-10481	WebUI	Group member list is not expandable for sharers or users. When a sharer or user views the Shared with list in folders UI they can't expand groups to see who are its members.
GW-1202	MOVEit Client	When using the new MOVEit Client, uploading files over a few MB can fail if the ingress path includes MOVEit Gateway. Workaround: Use the MOVEit Transfer WebUI to upload the file or connect to the MOVEit Transfer Server directly.
MID-87	MOVEit Client	Drop down list contains folders or files recently deleted by another user. This can happen in some concurrent user scenarios. Workaround: Click (refresh button).
MID-89	MOVEit Client	After removing MOVEit Client can leave its temporary application files. This can include the session token. Workaround: Clear the platform's app data. For example: On Windows: %APPDATA%/MOVEit Client On MacOS: ~/Library/Application Support/MOVEit Client On Linux: ~./Moveit Client
MID-129	MOVEit Client (macOS)	Uncaught Javascript exception when running two or more MOVEit Clients on the same desktop machine. Workaround: Close the exception alert box. Run only one instance of MOVEit Client at a time on a given desktop machine.

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 `https://mobile/?orgId=1234` --for example) To work around this, avoid deploying MOVEit Mobile with hostnames that begin with the string prefix "mobile" For example: mobile2017.example.com (causes redirect error) mymobile2017.example.com (correctly redirects)
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: Open Tomcat configuration in your favorite editor. For example: `notepad.exe C:\Program Files (x86)\MOVEit\TransferMobile\Tomcat\conf\server.xml` Scroll down to the port 8443 connection section and make the following change: `SSLProtocol="TLSv1.2"` Restart the MOVEit Transfer Mobile Service.
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.