The new version of the application could not be verified (code 51)
The window of the starter says: “The new version of the application could not be verified and was not installed.” Below it stands the error code 51; the diagnostic details (Alt+D) name the file or the signature. The exit code of the starter is 51. When a version is installed already, the starter starts it instead and reports nothing; the log (%LOCALAPPDATA%\WKL\<Product>\Logs) then says “The delivery is not trusted”.
Environment
WKL Bootstrapper 2.0 with a project file of format 2.
Cause
One of:
- the project names a
deliveryKey, and the source has nodelivery.json, nodelivery.json.sig, or a signature made with another key; delivery.jsonis for another product or version than the source delivers (the delivery was changed after publishing without publishing again);- a file the project takes is not listed in
delivery.json, or its size or SHA-256 differs - checked before copying and again on the copy (a file replaced on the share after publishing, a copy cut off, a virus scanner that changed it).
See Signed deliveries.
Resolution
- Publish the delivery again on the publisher's computer, after the last change in the source:
Wkl.Bootstrapper.exe /publish /key <name>beside the project file (or with the configurator). See How to: Publish a signed delivery. - If the key does not match, use the delivery key whose public part stands in the project file the IT rolled out; a new key needs a new project file on the users' computers.
- Start again.
en/wiki/msaccess/bootstrapper/troubleshooting/51-delivery-not-trusted.txt · Last modified: by Wolfgang van der Stille