Start here if you are installing LeasePak on your client computer for the first time.
Start here if you have finished installing or upgrading LeasePak and need to perform additional configuration on your client computer.
Start here if you have a previous installation of LeasePak on your client computer.
Review the LeasePak Client section of the document System Requirements before beginning the installation process to ensure your client computer meets the minimum requirements for LeasePak .
Each LeasePak client user requires the following:
For more information, refer to LeasePak Users.
This is the procedure for installing LeasePak on a client computer where no previous installation of LeasePak exists. If the computer has a previous installation, use the procedure described in the Upgrade and Conversion section of this document.
Select the installation appropriate to your needs:
Perform the following required configurations:
Windows 2000, Windows 2000 Terminal Server only: complete the following additional configuration for each user's LeasePak
installation on the computer. This procedure provides each user with individual LEASEPAK.INI
and
LPCODE.TXT
files.
From the Microsoft Windows Update web site, install the latest updates for your version of Windows.
Test the connection between the LeasePak client and server:
ping host
where host is the name or IP address of the LeasePak server, then click Enter.
You should receive a reply from the server similar to the following:
If the window displays "Request timed out," the client was unable to complete the connection to the server. If the window displays "Bad IP address," either the IP address is incorrect, or you need to set either your network or the client computer to resolve the host name properly.
Set the Windows Short Date format:
This setting must match the User Date Preference set for the user in the LeasePak Security [U0706] update.
Refer to the appropriate document for installing, upgrading, and/or configuring the DBMS client:
Install MDAC (if needed) for the following situations:
If you need to install MDAC, contact your MSI representative for information on locating or obtaining the setup programs.
To install MDAC:
Close all other Windows programs prior to running the setup.
Windows NT, Windows 2000: log on the client computer as Administrator or other user with Administrator privileges. The installer requires Administrator privileges to correctly write to the registry and the systems directory.
The path of setup.exe
is:
\lpux\software\lpclient\setup.exe
To install LeasePak directly from the CD or over your local network, either:
path\lpux\software\lpclient\setup.exe
in Windows Explorer,
where path is the CD-ROM drive or network location; orpath\lpux\software\lpclient\setup.exe
(where path is the CD-ROM drive or network location) and click OK.
The installer displays the following messages:
When the following dialog box appears, click Next to begin the installation:
Enter user information then click Next:
Accept the default destination folder or change to another destination folder, then click Next.
MSI recommends installation to the default folder.
To change the destination folder, click Change. The following dialog box appears:
Click OK to use the specified destination folder. The installer returns to the previous dialog box:
Click Next to continue.
For custom installation, refer to the section Custom Installation.
From the Setup Type dialog box, select Typical and click Next.
The Typical installation option installs the most common options, including:
In addition, the Typical option uses the default path and folder for the LeasePak user directory:
Windows 98 c:\my documents\LeasePak\
Windows NT c:\winnt\profiles\user\personal\LeasePak\
Windows 2000 c:\documents and settings\user\my documents\LeasePak\
Windows XP c:\documents and settings\user\my documents\LeasePak\
Files in the LeasePak user directory include:
CMDBUFF.LOG, DBG1.LOG, DBG3.LOG, LEASEPAK.INI, LPCODE.TXT
and NEWLABLES.TXT
Windows NT, Windows 2000, Windows XP: Machine-level installations for multi-user computers may require installing the LeasePak user files in a location accessible by all users. Change the location of the LeasePak user directory by using the Custom Installation
Click Install to begin the LeasePak client software installation.
The following dialog box displays information on the progress of the installation. Wait for the installer to finish, or click Cancel at any time to abort the installation.
When the installation is finished, the following dialog box appears. Click Finish to exit the installer.
You must restart your computer before using LeasePak.
For typical installation, refer to the section Typical Installation.
From the Setup Type dialog box, select Custom and click Next.
Do not accept the default LeasePak user directory folder--this is the Administrator user's folder and the actual LeasePak client user, in most cases, will not have access to it. Click Change to switch to another folder.
Files in the LeasePak user directory include:
CMDBUFF.LOG, DBG1.LOG, DBG3.LOG, LEASEPAK.INI, LPCODE.TXT
and NEWLABLES.TXT
To change the user directory folder, click Change. The following dialog box appears:
Use this dialog box to select another folder, either locally or on your network.
Windows 98 c:\my documents\Leasepak\
Windows NT c:\winnt\profiles\all users\Leasepak\
Windows 2000 c:\documents and settings\all users\Leasepak\
Windows XP c:\documents and settings\all users\LeasePak\
To use a folder on your network, select a network share previously mounted for the installing user (Administrator).
The drive letter must be available to all users on the client computer. LeasePak will resolve the path
specified and store local preference files in the selected folder. In this example, drive O: must be mapped to a
unique location for each user on the client computer, and for each user the drive must contain the path
O:\Leasepak\. If this is not set up, exit the installer and complete the required
configurations, then restart the installation. Within the Administrator's setup, the installer uses this network share
to establish the registry entry in HKEY_LOCAL_MACHINE
. Once the installation is complete, the share may be removed from
the Administrator's setup.
The following is an example of the HKEY_LOCAL_MACHINE
registry entry
The registry entry is located in the folder My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\McCue Systems\Leasepak\(ver), where (ver) is the specific LeasePak installation.
An additional registry entry is located in My Computer\HKEY_CURRENT_USER\Software\McCue Systems\Leasepak
This contains items such as the toolbar preferences and others that are not stored in the user's
leasepak.ini
file.
Click OK to use the specified user folder. The installer displays the Change User Folder dialog box again. Verify the user folder and click OK.
The installer returns to the previous User Folder dialog box (your dialog box will feature the specified path and folder):
Click Next to continue the installation.
Select the program components to install and click Next.
The program components include:
After customizing the installation, click Next to continue.
Click Install to begin the LeasePak client software installation.
The following dialog box displays information on the progress of the installation. Wait for the installer to finish, or click Cancel at any time to abort the installation.
When the installation is finished, the following dialog box appears. Click Finish to exit the installer.
You must restart your computer before using LeasePak.
In addition to the Configurations described in this section, you can also customize the LeasePak form, field, and menu labels as they appear within the software. For more information on customizations, refer to the document LeasePak Customization.
In the Windows Start menu, select Programs, LeasePak UX
Do not log on. In the LeasePak menu, select Setup.
Prior to version v5.0a, native VB grids did not feature client search capabilities, nor did they display multi-column descriptions for drop-down help. Due to the complexity of existing LeasePak code, grids that support the expanded help option may impact normal LeasePak behavior and cause unexpected results.
index.html
file
(location)\refguide\index.html
where (location) is the drive letter and path containing the folder refguide
.
The client user must have access to this folder in order to use the Help [F1] function within LeasePak.
You must use updates within LeasePak to configure printers for the client. You can find the documentation specified in this section in the LeasePak Reference Guide.
lpadmin
or other user with full privileges. Refer to the
document LeasePak Basics for more information about
logging on the client.start_queues.com
. Locate the queue name at the
end of the the line:
$ init/que/start/form=default/on=LP4SI: sys$print
In start_queues.com
, the queue name is in lowercase, but you must type the queue
name in uppercase in Destination Device or Queue.
Length
parameters defined at the top of the start_queues.com
file. In most cases, portrait
printers have 66 lines, while landscape printers have 45. Contact your MSI representative for more
information.lpadmin
within
LeasePak through
Report Profile [F4]:
In most cases, users have access to Report Profile [F4] and can set or change their own default report destinations. The document LeasePak Basics describes the use of Report Profile [F4].
You can change the report profiles for other users through the LeasePak Security [U0706] update. Refer to the Reports section of the document Security [U0706] for information.
Windows 2000, Windows 2000 Terminal Server: after installing LeasePak, you will need to complete
the following procedure for each user's LeasePak installation on the computer. This procedure provides each user with individual
LEASEPAK.INI
and LPCODE.TXT
files.
"lp_ini_path.reg"
(include quotation marks) on the
Windows Desktop."lp_ini_path.reg"
and save:"lp_ini_path.reg"
to load it into the Windows registry. Click OK
and other confirmation buttons when prompted.Repeat these steps for each user's LeasePak installation on the computer.
The installer allows the user to Modify, Repair or Remove LeasePak and/or the additional components included in the set up.
From the Control Panel, select the Add/Remove Software. The following screen will appear: Select LeasePak from the list of installed programs.
Click the Change button. Select the Change option. The installer will start and assist in the required modifications.
Select Next.
Modify/Repair/Remove dialog box.
Select the Program Maintenance option desired. Click Next.
This screen is displayed when the Modify maintenance option is selected. This option is used to add and/or remove program features via the Custom Setup installation option. Select the desired program to add and/or remove.
Copy down custom install components information.
Click Install.
This screen is displayed when the Repair maintenance option is selected. This option is used to repair installation errors in the program. This option repairs missing, corrupt files, shortcuts and registry entries.
Click Install.
This screen is displayed when the Remove maintenance option is selected. This option completely removes LeasePak from the users computer.
Click Remove to continue.
Restart machine.
If the Modify or Remove option was selected, the screen displays the following message: "The InstallShield Wizard has successfully installed LeasePak (version number). Click Finish to exit the wizard." If the Remove option was selected, the screen displays the following message: "The InstallShield Wizard has successfully uninstalled LeasePak. Click Finish to exit the wizard."
Review the LeasePak Client section of the document System Requirements before beginning the upgrade process to ensure your client computer meets the minimum requirements for LeasePak .
Each LeasePak client user requires the following:
For more information, refer to LeasePak Users.
This is the procedure for installing LeasePak on a client computer where a previous installation of LeasePak exists.
Unless the user requires more than one version of LeasePak installed, MSI recommends removing all earlier installations of LeasePak prior to installing version General Availability (GA). If the user has a version of Release Candidate (beta) installed, it must be removed prior to installing GA. Use Add/Remove Programs from the Windows Control Panel to remove earlier installations of LeasePak.
Removing earlier installations of LeasePak
may also remove ODBC driver installations. If you are retaining an existing version of LeasePak (5.0a or earlier), or require ODBC for
other applications, verify that the necessary ODBC drivers are still installed after removing LeasePak.
If drivers are missing, reinstall MDAC 2.5 and the appropriate database client (Oracle or Sybase), then reconfigure the ODBC driver
installations.
Select the installation appropriate to your needs:
Perform the following required configurations:
Windows 2000, Windows 2000 Terminal Server only: complete the following additional configuration for each user's LeasePak
installation on the computer. This procedure provides each user with individual LEASEPAK.INI
and
LPCODE.TXT
files.
Close all other Windows programs prior to running the this program.
Windows NT, Windows 2000: log on the client computer as Administrator or other user with Administrator privileges. The installer requires Administrator privileges to correctly write to the registry and the systems directory.
The path of leasepaksanitizer.exe
is:
\lpux\software\leasepaksanitizer
leasepaksanitizer.exe
.
The installer displays the Welcome dialog box. Click Next.
Once the installation is complete, the installer displays the Setup Complete dialog box. Click Finish.
The leasepak.ini
file, located in the client LeasePak directory, contains the user settings.
It also has sections that the user or administrator can use to assist MSI in troubleshooting.
[login] DefaultUsername=lpadmin [database] DataSource=server1_sybase [server] TcpIpAddress=server1 Environment=production Port= MaxConnections=10 Timeout=60 [credit dial-up] Port=6000 Subscriber_Code= [window] IsMaximized=1 Xpos=0 Ypos=0 Width=9390 Height=7770 [logicals] leasepak_core=1 ;normally LeasePak dumps 0-length leasepak_cmd_buffer_log=1 ;transactions between lpadriver.exe and Sybase [debug] logfile=1 ;transactions between client and lpadriver.exe cmdbufferlog=1 ;transactions between client and Sybase
LeasePak automatically dumps a core file for many errors encountered during End of Period processing.
For End of Period troubleshooting, you do not need to set the leasepak_core
logical.
The About LeasePak dialog box in the LeasePak client contains information pertaining to the current environment,
LeasePak license, leasepak.ini
settings, and other user preferences.
In the LeasePak menu, select Help, then About
In the field Information, select the type of information you wish to view:
leasepak.ini
settings for the user.
LeasePak Documentation Suite
© by McCue Systems Incorporated. All rights reserved. The information
contained in this document is the property of McCue Systems, Inc. Use of the
information contained herein is restricted. Conditions of use are subject
to change without notice. McCue Systems, Inc. assumes no liability for any
inaccuracy that may appear in this document; the contents of this document
do not constitute a promise or warranty. The software described in this document
is furnished under license and may be used or copied only in accordance with
the terms of said license. Unauthorized use, alteration, or reproduction of
this document without the written consent of McCue Systems, Inc. is prohibited.
This message should disappear within 5-15 seconds, depending on the size of the document and the speed of your connection to the Documentation Suite.
If you can still see this message after 20 seconds, try clicking the Refresh or Reload button on your Web browser.
If your document still does not load, refer to Document Load Troubleshooting for instructions on how to fix possible problems with either your Documentation Suite installation or Web browser setup.
If you do not have read access to the parent docsuite directory, you will not be able to load the Document Load Troubleshooting document. In this case, contact your network administrator for assistance.