APPNOTE: Known issues running PmUpdate, the web update utility.

Last reviewed: May 7, 2009
Article ID: 090311sab

The information in this article applies to:

Pronto for Windows all versions from 5.50 onwards.

Target Audience.

This article is aimed at:

All Users of Pronto for Windows.

Summary.

Pronto for Windows Release 5.50 and later includes PmUpdate, a utility that updates a users Pronto installation to the latest release by downloading updated components from the Outram Research web site.
This application note details known problems that have been encountered by users running this utility and suggests solutions.

Known Issues.

1) Installation not valid.

Symptom:
PmUpdate produces the message: "Installation of Pronto for Windows does not appear to be valid"
Cause:
PmUpdate checks for the presence of several files to be certain that it can safely upgrade a users Pronto installation. One of the files expected is PRONTO.HLP. At Pronto release 5.53 the PRONTO.HLP file was removed from the setup as the online help was changed to the new "compiled HTML" format PRONTO.CHM.
Due to an oversight on my part I did not revise PmUpdate and it still looks for PRONTO.HLP which is not present.
Solution:
Copy the file PMSCREEN.HLP and rename it to PRONTO.HLP then re-run PmUpdate.
Applies to:
This occurs ONLY on a computer where the first version of Pronto installed was 5.53 and it was installed from the CD.

2) Unable to download the update list.

Symptom:
PmUpdate produces the message: "the file pmupdate.txt was not found"
Cause:
PmUpdate is unable to download the file containing the list of latest versions from the Outram research web site.
Solution:
The first step to fixing this problem is to check what is returned as a "HTTP result code" in the progress window when PmUpdate tries to get "pmupdate.txt".
The status window should contain the text something like this:

Getting revisions list ===============================
opening http://www.outramresearch.co.uk/updates/pmupdate.txt result code 407 <----HTTP result code.

The meanings of all possible result codes are here: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
The most common failure I have seen is result code 407 explained here: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.8. This applies when a user is inside a company firewall with a proxy server that requires authentication. To resolve this problem enter the proxy authentication information using the "Configure Proxy..." button on PmUpdate (Your IT department should be able to provide you with the username and password used for authentication with your proxy server).

3) The requested operation requires elevation.

Symptom:
On Windows Vista, when launching PmUpdate using the HELP - CHECK FOR UPDATES menu item from within Pronto for Windows the message: "Failed to launch the utility <PmUpdate.exe> Error: <The requested operation requires elevation" appears.
Cause:
PmUpdate requires write access to the Pronto application directory in order to update Pronto.exe and other utilities, on Windows Vista write access requires higher (elevated) access rights.
Solution:
Launch PmUpdate directly by browsing to the Pronto application directory, right clicking on PmUpdate and selecting Run-As Administrator.

Back to Knowledge Base index

THE INFORMATION PROVIDED IN THE PRONTO FOR WINDOWS KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. OUTRAM RESEARCH LTD DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL OUTRAM RESEARCH LTD OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF OUTRAM RESEARCH LTD OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.