Installation Difficulties
Windows Installer
We have encountered the following problems that may occur when installing VAST Platform.
1. An error with Windows Installer appears with Error 1301 and various messages. Several probable 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.
Difficulties launching an image from the Environments tool
The installation completed successfully, and Environments shows an environment is available, but I cannot open that image.
Solution:
If you have installed VAST Platform (or VA Smalltalk) in the past, you will have an older version on Environments on your machine. That older version may be on your desktop. You should discard that version of Environments and use the one installed for your most current release. Then, when you launch Environments, it will automatically register your installation, and your environments will start without a hitch.
Environment tool is backward compatible in that it recognizes the structure of Installations, the specific 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 latest installation. Once the installation is complete, delete the desktop Environments shortcut associated with the earlier version.
If you have been using Environments to organize your development images, you will already have an Environments data file (environments.dmp) in envroot when you install an updated version of the VAST Platform product.
When you install VAST Platform, Environments automatically becomes aware of this installation when it is subsequently launched. 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. They will also be visible from the
Installations view in the
System Settings. See the section on
Managing VAST Platform Installations for details.
Windows 32-bit/64-bit Considerations
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 VAST installations share a library (code repository) and the Environments tool included with each VAST installation shares private files like the data file, environments.dmp.
This situation leads to installation decisions regarding:
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 operating system), it is recommended to install the shortcut on your desktop only once. The second VAST Platform installation should not include a desktop shortcut to its Environments tool.
Note
Having just one shortcut means that, if you uninstall the installation to which the shortcut points, the shortcut will also be deleted.
Library
If you decide to install 32-bit v14.1.0 on a 64-bit system that already has a 64-bit v14.1.0 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 back up and overwrite the library.
Note
Likewise, whenever you uninstall one of your installations, you should take care not to delete the library (aka Manager.)
See “Windows 32-bit/64-bit 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 in:
o %temp%.
The name is of the form MSIxxx.log, where xxxx is a number assigned by the Installer.
Last modified date: 07/16/2025