stderr/stdout logs are failing to be served to Marathon

Given an app in Marathon with the command powershell -noexit -c get-process, we expect it to deploy, and the "Error Log" and "Output Log" of the running instance to return the stderr and stdout files from the agent.

While the files exist on the agent with the appropriate contents, e.g. work_dir\slaves\ff198863-667e-46b9-a64d-e22fdff3b3cb-S4\frameworks\ff198863-667e-46b9-a64d-e22fdff3b3cb-0000\executors\get-process.4211c4e3-7181-11e7-b702-00155dafc802\runs\7fc924b4-4ec1-4be6-9386-d4f7cc17d5ad has stderr and stdout, and the latter has the output of get-process, Marathon is unable to retrieve them.

Clicking the link for the instance returns the error: "Sorry there was a problem retrieving file. Click to retry."

The Mesos master is receiving the request I0725 14:54:49.627329 226319 http.cpp:1133] HTTP GET for /master/state?jsonp=jsonp_15d7bbed282 from 10.123.175.200:55885 ..., but no further logging is displayed.