StarLicense Server for Windows v1.31 Release Notes
November 2010
Introduction
StarLicense for Windows is a license server for StarQuest products, including StarSQL. A client uses TCP/IP to connect to the server to obtain a product license. The client may be an application running on the local or another Windows system, an application running on a UNIX system, or a Java application running locally or remotely.
Setting up a StarLicense server allows centralized management of the licenses and allows an organization to take advantage of floating licensing available for client computers running StarQuest software.
The following topics are addressed in these Release Notes. Refer to the StarLicense for Windows Quick Start Guide for detailed information about installing StarLicense Server for Windows for the first time, and refer to the StarLicense Manager Help for detailed information about using the StarLicense Server for Windows software. Refer to StarLicense_doc_addendum.pdf for details about new features and documentation errata.
- What's New in this Release
- Upgrade Considerations
- System Requirements
- Installing and Using the StarLicense Server for Windows Software
- Known Issues
- Release History
- Contacting StarQuest
What's New in this Release
This release of the StarLicense Server for Windows introduces the following new features and improvements:
- Support for Windows 7
- improved logging and journaling
- 64-bit version for Windows
Upgrade Considerations
This section describes issues of interest for users who are upgrading from a prior version of StarLicense Server for Windows.
- Save your current StarLicense configuration before upgrading from versions of StarLicense prior to v1.22.
System Requirements
You can install and run the StarLicense Server for Windows on computers with the following operating systems.
StarLicense (32-bit):
- Windows 2000
- Windows XP
- Windows Server 2003
- Windows Server 2008
- Windows Vista
- Windows 7
StarLicense (64-bit):
- Windows XP Professional x64 Edition
- Windows Server 2003 x64 Edition
- Windows Server 2008 x64 Edition
- Windows Vista x64 Edition
- Windows 7 x64 Edition
StarLicense Server for Windows requires Visual C++ 2008 runtimes. The StarLicense installer will install the Microsoft-supplied Microsoft Visual C++ 2008 SP1 Redistributable package if it is not already present on the system. The Microsoft Redistributable package will remain on the system if StarLicense is upgraded or uninstalled.
Installing and Using the StarLicense Server for Windows Software
- The StarLicense for Windows Quick Start Guide provides step-by-step instructions for installing and using the StarLicense Server for Windows in the shortest time.
- After you've installed the software, refer to the contents, index, or search the StarLicense Manager Help for the topic or issue you want to learn more about.
- Browse the StarLicense technical documents at http://www.starquest.com/Supportdocs/techStarLicense/browseSL.shtml for specialized information, such as using the StarLicense Server for Windows in a particular environment or to accomplish a special task.
- Refer to StarLicense_doc_addendum.pdf for details about new features and documentation errata.
Known Issues
Installation Error on Windows 2000 using terminal services and a mapped drive
When installing StarLicense on Windows 2000 using terminal services and a mapped drive, you may encounter this error:
Error 2755.Server returned unexpected error 3 attempting to install package.
Solution: copy the installer to a local disk.
This restriction does not exist for a remote sessions run on Windows XP or later.
Installation of Visual C++ 2008 Redistributable Package on Windows 2000
On Windows 2000, you may receive a message that the installation of the Visual C++ 2008 Redistributable Package has failed, even though it has succeeded. You may ignore this message. Also, the StarLicense installer may attempt (and appear to fail) to install the Visual C++ 2008 Redistributable Package even if it is already installed.
Release History
This section provides information about problems or enhancements that are made available as "point releases" and major releases of the StarLicense Server for Windows software.
| Version Number | Release Date | Significant Changes |
|---|---|---|
| V1.31.1130 | Nov 2010 | 11497 Server: notify clients when a license is removed from the server |
| V1.30.0725 | Jul 2010 | 10222 Failover scenario fails silently if port 4997 is blocked 10934 Include in the journal log output the soft-license checkins due to timeout 10955 Expand timestamp resolution to milliseconds 10956 Change timestamp format to conform to ISO standard 11099 Create 64-bit Windows installer 11204 Installer: 32-bit installer should check for presence of 64-bit installation 11287 Identify service dependency (or implement retry) if nodelocked IP addresses not available 11339 Expand single character codes to full words 11342 Add subtype to journal/log to further elucidate reason for reclamation 11383 Journaling: record soft-license timeout (grace) value on "Service" entries |
| V1.21.1020 | Oct 2009 | 10934 Include in the journal log output the soft-license checkins due to timeout
10957 Include "grace" period in journal output 10969 Windows Installer: update installer (IS2009, VS2008, readme.html) |
| V1.10.1210 | Dec 2008 | 10496 Build with Visual Studio .NET 2003 Client changes |
| V1.07.0428 | Apr 2008 | 10298 Client: Revisit lookup order (starlic vs local and configured licenses) 10383 Client: WSAStartup called in DllMain causes problem on Windows Server 2008 as Local System 8455 Zombie checkouts remain after client loses connectivity 10322 Move location of log directory 10347 Installer modifications for Vista and Server2008 10386 add new features to starlic-remote-admin: active-checkout-count |
| V1.06.1203 | Dec 2006 | 9942 StarLicense Management Console hangs on Win2003 |
| V1.02.0610 | Jun 2003 | 8250 StarLicense Win&Unix - journaling does not record failed connections 8259 StarSQL Win&Unix - Journal Filenames, should be YYYYMMDD 8271 StarLicense/Win&UNIX - Doesn't read licenses from > 1 failover server 8272 StarLicense - backup server enhancement 8199 Starlicense/Win - removing failover, leaves licenses 8202 Starlicense/Win - purge licenses after connection to the primary had been deleted from the server 8268 StarLicense/Win - Journal retention 8271 StarLicense/Win&UNIX - improve failover 8279 StarLicense/UNIX&Win - improve failover 8280 Exploit multiple server addresses defined by DNS |
| V1.01.0521 | May 2003 | 8216/8220 Write and close the journaling log file(s) after each entry 8249 StarLicense Win&UNIX - Journal file contains YYYYDDMM |
Contacting StarQuest
If you need to contact technical support, please provide the following information to help the support engineers address your issue. You can contact StarQuest via phone, email, or facsimile as indicated at the bottom of this page.
| Company Information | Address Phone Fax |
| Contact Information | First and Last Name of individual contact Email Address |
| Host Type | Hardware and Operating System (i.e., AS/400 V5R4) |
| Network Protocol/Gateways | Protocol and/or Gateways used (i.e., TCP/IP, HIS 2000) |
| Client Type | Client Type and Operating System (i.e., Windows 2008 SP2) |
| StarQuest Product, Version, and Source |
Which StarQuest product and what version is installed (i.e., StarSQL for Windows v5.50.02.18) Where you obtained the software (i.e., direct from StarQuest, name of specific reseller) |
| Problem Information | Provide as much detail as possible, including information about any application that is using the StarQuest product when the problem occurs and the exact error message that appears. |
© 2010 StarQuest Ventures, Inc. All rights reserved.
StarQuest Ventures, Inc.
PO Box 1076
Point Reyes Station, CA 94956
Telephone: 415-669-9619
FAX: 415-669-9639
Sales & Support: contact@starquest.com
URL: http://www.starquest.com