Installing the PSQL Workgroup for Windows
*Note: If the installation fails for any reason, the installation log file can be found in the Windows %Temp% directory.
The following steps explain how to install PSQL Workgroup from its media using the default interactive installation.
►
To install PSQL Workgroup for Windows
1
Launch the installation program from your Windows workstation:
c.
Insert the PSQL CD into the CD-ROM drive of your Windows server, or run the downloaded self-extracting installer executable.
d.
If the installation does not start automatically, run the autorun executable from the operating system: drive:\autorun\autorun where drive is the drive letter of your CD-ROM device.
The installation selection dialog displays.
2
Click Workgroup installation.
The installation program begins its initial preparation. After the preparation completes, the Welcome screen appears.
3
If prompted, close or uninstall any running applications that may interfere with the PSQL installation.
*Note: If you wish to leave one or more programs running that may interfere, you must click Ignore to continue. Unpredictable results may occur during the PSQL installation if you ignore programs that may interfere.
4
At the Welcome screen, click Next.
5
On the License Agreement page, read and accept the Software License Agreement, and then click Next.
6
Select the Workgroup Engine installation mode: Run as a Service or Run as an Application.
Figure 2 Workgroup Engine Installation Mode
 
By default for a fresh installation, PSQL Workgroup installs to run as a service. For an upgrade installation, PSQL Workgroup is installed to run in the same manner as the previous installed version. That is, if it was already installed to run as an application, the upgrade installation installs it to run as an application, and vice versa.
Select Run as a Service if:
•
You want to avoid User Access Control conflicts from the operating system. Running the database Engine as a service requires the Log On as Service privilege. If you run the Engine as a service under a user account other than the default Local System account, ensure that you modify the Log On Properties for the Service using the Windows Control Panel.
•
You want to run Workgroup Engine on a machine using Terminal Services environment.
Select Run as an Application if:
The data files only reside on a remote machine, are accessed via drive mappings, and no database Engine is running on the remote machine.
7
Select the setup type: Complete (default) or Custom.
The Complete setup (recommended for most users) installs all the PSQL v12 components using the default options and locations.
•
If you choose a Complete install, click Next and continue with step 12.
The Custom setup (recommended for advanced users) allows you to specify the installation location, select the components and associated subfeatures to install, and determine the space requirements for the components.
•
If you choose Custom, click Next and continue with the following steps.
8
To specify different installation locations, click Change for any of the folders listed, then enter or browse for a different folder. Click OK to accept the location.
9
Click Next to continue.
10
Select the components and associated subfeatures you want to exclude from the installation and click Next. All of the PSQL components and subfeatures are selected for installation by default.
•
Data Access
•
ActiveX Interface Controls
•
ADO.NET Providers
•
Btrieve DOS (32-bit only)
•
DTO
•
JCL
•
JDBC Driver
•
OLE DB
•
PDAC
•
Utilities
•
Java Utilities
•
PSQL Control Center
•
Documentation
•
Data Definition File Builder
•
Notification Viewer
•
Other Utilities
•
Cobol Schema Exec
•
PSQL System Analyzer
11
Click Next to continue.
12
Click Install to begin installation.
13
A dialog displays when the installation wizard completes. The product has been installed with a trial key that expires at the end of its trial period.
You have two choices at this point: continue and authorize the product with a permanent key, or end the installation (and later authorize the product with a permanent key).
•
If you choose to continue and authorize the product, an Internet connection is required. Click Next and continue with step 14. (If you have no Internet connection, click Next then click Finish. See Alternative Authorization Tasks in PSQL User's Guide.)
•
If you choose to end the installation at this point, click Next then click Finish. (You may run the License Administrator utility at a later time to authorize a key. See License Administration in PSQL User's Guide.) See also Authorization of Workgroup Key on Windows with UAC.
14
Enter your license key and click the button to authorize the key.
(If you decide not to authorize the product at this point, click Finish. You may run the License Administrator utility at a later time to authorize a key. See License Administration in PSQL User's Guide.)
15
A message box displays with the status of the authorization action. Perform one of the following actions depending on the status:
•
If the authorization status message is “key is authorized,” click OK, then click Finish to complete the installation.
•
If the authorization status message reports an error or warning, click OK, and repeat step 14, ensuring that you enter a valid license key.
16
Register your product (recommended) as explained on the Registration page that displays, then close the Registration page.
If you are prompted to restart your system, please do so in order to ensure proper operation of your PSQL v12 product.
*Note: The installation program modifies some of the environment variables. On Windows platforms, environment variables are stored in the Control Panel under System information.
Authorization of Workgroup Key on Windows with UAC
You can encounter difficulty authorizing a permanent key for PSQL Workgroup on Windows with User Account Control (UAC) if the following conditions are all true:
•
PSQL Workgroup was installed as an application.
•
The Workgroup database engine is running without administrative privileges. Note that, by default, applications run with privileges of a standard user unless the privileges are elevated. That is, even if you are a member of the administrator’s group and you start the Workgroup database engine without using Run as Administrator to elevate privileges, the engine runs with privileges of a standard user.
•
A permanent key for PSQL Workgroup was not supplied during the installation process. That is, you chose to authorize the permanent key after installation by using a licensing utility.
Complete the following steps to ensure a permanent key is correctly authorized:
1
If the PSQL Workgroup application is running, close the application (stop the database engine by right-clicking on the engine tray icon then clicking stop).
2
From File Explorer, locate the file w3dbsmgr.exe. Look for the file under <install_drive>\Program Files\Actian\PSQL\bin.
3
Right-click w3dbsmgr.exe then click Run as Administrator. You must have administrative rights or know the password and name of a user with administrative rights. You need to elevate the privileges of the database engine before authorizing a key with a licensing utility.
4
Start License Administrator from operating system Start menu or Apps screen (or use the command line interface licensing utility if you prefer).
5
Type, or paste, the permanent key for PSQL Workgroup in the Key field, then click the button to authorize the key.
6
Optionally, stop the database engine and re-start it without elevated privileges.
Note that elevating the privileges for a license administrator utility is not the solution. The database engine itself, w3dbsmgr.exe, is what requires elevated privileges.