Answer
Try renaming the existing client.war file (for example, to client_.war or _client.war) in that instance's folder before re-running the installation — this has resolved the same error for others, letting the installer regenerate/redeploy that file cleanly on the rerun rather than trying to work with whatever state the existing one was left in.