{"id":2364,"date":"2013-05-08T17:32:59","date_gmt":"2013-05-09T00:32:59","guid":{"rendered":""},"modified":"2025-02-11T12:30:03","modified_gmt":"2025-02-11T20:30:03","slug":"2364","status":"publish","type":"post","link":"https:\/\/www.vernier.com\/til\/2364","title":{"rendered":"Common causes of problems with the Logger Pro silent installer"},"content":{"rendered":"

Logger Pro<\/i> is no longer sold and will no longer receive updates.<\/strong>
For more information see Logger Pro<\/i> will no longer receive updates<\/a>.<\/p>\n

We strongly recommend that you use the Logger Pro<\/i> MSI file as-is. We have tested on a wide variety of systems. Although it is technically possible to dissect the file, this often breaks the custom USB driver installation.<\/p>\n

The MSI installer needs to be run with the correct arguments. A batch file is provided as an example script. You do not have to use it, but it is recommended that you read it, especially if you are having problems.<\/p>\n

The installer requires explicit administrative rights. For testing purposes on Windows Vista and newer, simply being logged in as administrator is not sufficient; rather, you will need to be running in an administrative shell (Start Menu, All Programs, Accessories, right click on Command Prompt and select “Run as Administrator”). As such, just double-clicking on the batch file doesn’t work on those operating systems. (For actual deployment, this is a very rare cause of problems. Your tool will normally run as either an admin or system.)<\/p>\n

The included batch file does several things, including uninstalling previous versions of Logger Pro<\/em>. If you don’t have a previous version of Logger Pro<\/em> installed, the batch file will give two messages in the command prompt window (i.e., not as windows dialogs) about not being able to find a previous version. (It tries twice for various reasons related to the number of versions over the years.) Thus, even if you do have a previous version installed, the batch file may still give a message about not finding it. Those messages are normal.<\/p>\n

UNCs (which use a path to a network drive in the form of \\\\servershare) don’t work in most command line commands. Instead, do one<\/strong> of the following:<\/p>\n