Installation Difficulties
We have encountered the following problems that may occur when installing VAST Platform.
1. An error dialog from Windows Installer appears with the text: "Error opening installation log file. Verify that the specified log file location exists and is writable” Microsoft has confirmed this to be a problem with Windows 7 Professional. To work around this issue, stop and restart the Explorer.exe process using Task Manager.
2. An error with Windows Installer appears with Error 1301 and various messages. Several possible causes of this error are:
a. The directory specified in the error is currently open in Windows Explorer. This locks the location and prevents the installation from being able to access it.
b. Another application or utility, such as a virus scanner, is currently locking the directory specified in the error message.
c. The user performing the installation does not have sufficient security privileges to access the directory specified in the error message.
Do you have VAST Platform on your Machine?
If you have an ealier version of VAST Platform or VA Smalltalk installer, here are some things to consider:
You should upgrade the version of the Environments tool you use
You will want to make VAST Platform 10.0.2 available to the Environments tool so that you can create development environments tailored to your work.
Environments Tool Upgrade
Environment tool is backward compatible in that it recognizes the structure of Installations the particular version of VAST Platform with which it is installed and all prior versions, but not any later versions.
Installation Action:
If you already have an Environments Shortcut on your desktop, you should choose to make a shortcut to the Environments tool on your desktop during your 10.0.2 installation. Once the installation is complete, delete the desktop Environments shortcut associated with the earlier version.
If you use environments, register the new installation
If you have been using Environments to organize your development images, you will likely already have an Environments data file (environments.dmp) in envroot when you install a new version of the VAST Platform product.
The Environments tool is not automatically aware of your newest installation. This is true whether you are simply adding the most recent VAST Platform or constructing a joint 32-bit 64-bit VAST Platform installation.
Post Installation Action:
After installing, you should register the new installation location by starting the Environments tool for that installation from its Program Starter start menu item. This will make the new installation visible to Environments by adding the installation location to the Environments data file.
Windows 32bit/64bit Considerations
This section assumes you do not have VAST Platform previously installed on your machine. See “Do you have VAST Platform on your Machine?” If you do for issues surrounding the first of the 32-bit (or 64-bit) installers you run.
There are several things to be aware of when installing both 32-bit and 64-bit VAST Platform. Each installation comes with its own Environments tool. However, the installations share a code repository (library,) and the Environments tool included with each installation share private files like the data file, environments.dmp.
This situation leads to installation decisions regarding
Protecting any existing library (code repository)
And post installation decisions regarding registering the 32-bit and 64-bit installations with the Environments tool.
Let’s take the Environments considerations first, then library considerations.
Environments Desktop Shortcut
If you are installing both 32-bit and 64-bit VAST Platform versions (on a 64-bit system), it is recommend to install the shortcut on your desktop only one time. The second VAST Platform installation should not include a desktop shortcut to its Environments tool.
Having just one shortcut means that, if you uninstall the installation to which the shortcut points, the shortcut will also be deleted.
If you decide to install 32-bit v10.0.2 on a 64-bit system that already has a 64-bit v10.0.2 installed (or vice versa) you should install just the Client portion of the second installation. If you install accepting all defaults, the library will also be installed. If the library from the first installation resides in the default location, the second installation will backup and overwrite the library.
Likewise, whenever you uninstall one of your installations, you should take care not to delete the library (aka Manager.)
See “Windows 32bit/64bit Considerations” under Environments Advanced Topics for more details.
Log file
The installation log is accessible from the final Installation Complete Success or Installation Error Dialogs. It is located in
The name is of the form MSIxxx.log, where xxxx is a number assigned by the Installer.
Last modified date: 02/18/2021