Installing SilverCreek Workgroups
Installing Dongle-locked SilverCreek on Windows Platform
Installing SilverCreek on WinNT/2K/XP/2003
Installing SilverCreek on Solaris, Redhat Linux and Linux
Extensions for Solaris and Linux Platforms
Extensions for Windows NT/2000/XP/2003
Installing SilverCreek Workgroups
SilverCreek license server should be installed on a stable machine that is accessible to all SilverCreek application machines. By using a license server, you can install SilverCreek on as many user machines as you want. These SilverCreek installations will consult the license server to check out a license at runtime. The maximum number of concurrent users of SilverCreek is determined by the seats you licensed.
The license server only serves license requests, and does nothing else.
The following instructions show you how to start SC license server manually, if you want to start license server automatically when the machine reboots please refer to
Flexlm end user manual chapter 6 "The License Manager Daemon"
Section 6.2 "Starting the License Manager Daemon on UNIX Platforms" and
Section 6.3 "Starting the License Manager Daemon on Windows Platform"
For details on how to manage INTRWORK FLEXlm license server please also refer to
Flexlm end user manual .
1. Download and install "SilverCreek License Server"
(a) Download SilverCreek License Server
Note: If you plan to install the license server on Redhat Linux 9 and later or Fedora Core
releases please download wgserver9.2-linux9.tar.Z package.
Install License Server on Solaris, Redhat Linux or Fedora Core Linux systems
Uncompress and extract the package from the downloaded file. If you have zcat on your
system, this can be done as follows:
zcat <zipped-tarfile> | tar xvf -
The wgserver files will be installed in a directory named wgserverx.x under the
current directory.
The lmgrd utility is used to start INTRWORK license server.
Install License Server on Windows (NT/2K/XP/2003) systems:
Click on the downloaded self-extractable workgroup installer and it will walk you through
the installation.
2. Get the hostID of the server machine
The start.sh shell scripts will print out your host ID, for example: "The hostid of this
machine is 8022c723"
Email this host ID to
This e-mail address is being protected from spambots. You need JavaScript enabled to view it
and a license file will be generated for you.
The hostID can also be obtained by executing command "lmhostid" (found in the
SilverCreek installation bin directory).
The application will prompt you for a license file and also provide you a host ID in a DOS
Prompt.
Email the chosen host ID to
This e-mail address is being protected from spambots. You need JavaScript enabled to view it
. We will generate a license file for you.
Note on Windows systems, the hostID is the MAC address of the installed NIC card. The
hostID can also be obtained by executing command "lmhostid" (found in the SilverCreek
installation 'bin' directory) in a DOS prompt. If multiple hostIDs are reported please
choose the one that is most unlikely to be removed from the system.
3. Install the license.lic file you received on the license server machine


4. Download and install SilverCreek application
(a) Download SilverCreek application installer
To download SilverCreek for Windows platform , select -->scx.x-winnt.exe
To download SilverCreek for Linux (x86) platforms,
select scx.x-linux..tar.gz
To download SilverCreek for Solaris 8 and later platforms (SPARC),
select scx.x-solaris8..tar.Z
You might need to click 'Next' button at the page bottom to see all files.
(b) Install SilverCreek application
Run install.sh scripts
   You will need an X Windows server running to finish installation. You can start the  
   installation by moving to the extracted directory (e.g., sc100-solaris8) and then run
   the following command:
cd sc10.5-solaris8
./install.sh
The installation script will start a setup wizard to guide you through the rest of the
   installation process.
5. Install the same license.lic file used to start the license server into SilverCreek's home
directory and you are ready to go!
There are several ways to install a license file on SilverCreek clients:
  Take a copy of license.lic file that you used to start the license server and place it in your
  SilverCreek Pro SP or SilverCreek Professional's home directory. Note you must retain the file
  name as license.lic.
 Alternatively you can use the "Import" button on the "License File Required" dialog when
  SilverCreek starts up to browse for it.
To start SilverCreek in SilverCreek Pro SP and SS Edition
Now you should be ready to start SilverCreek. If you have problems please check out the
Frequently Asked Questions on license file installation or contact
This e-mail address is being protected from spambots. You need JavaScript enabled to view it
Dongle Locked SilverCreek on Windows Platform Installation Guide
SilverCreek for WinNT/2k/XP/2003
1. Download software
2. Run self-extractable installation binary
After the software downloads, go to the destination folder and click the self-extractableUpon SilverCreek startup, you will be given a hostID in the "License File Required" window.
executable to begin the installation process. A setup wizard will guide you through the rest
of the installation process. A program group and program icon will be created
automatically for you, no icons will be added to the desktop.
3. Start the application to get the Host ID
To start SilverCreek in SilverCreek Pro SP and SS Edition:
Select "Start -> Programs -> SilverCreek Pro S* -> Run SilverCreek Test Suites
To start SilverCreek in SilverCreek Pro SL and SB Edition
Select "Start -> Programs -> SilverCreek Pro S* -> Run SilverCreek Tools
4. Install the license file you received to unlock the software
After receiving the license.lic please place it in SilverCreek's home directory. This is usually
"Program Files->InterWorking Labs, Inc->SilverCreek Pro SP x.x.".
Now you can try to restart SilverCreek. Alternatively if you saved the license.lic file received in your email inbox into a folder on your computer you can click the "Import" button to copy it into your SilverCreek root directory when prompted for license.
You should be up and running. If not please write to This e-mail address is being protected from spambots. You need JavaScript enabled to view it .
If you encounter problems when installing license, please check out SilverCreek installation FAQ to see if you can figure out the problem. Otherwise please contact This e-mail address is being protected from spambots. You need JavaScript enabled to view it .
SilverCreek for Solaris and Linux
1. Download and extract software package
2. Run install.sh scripts
You will need an X Windows server running to finish installation. You can start the
installation by moving to the extracted directory (e.g., sc8.0-solaris6) and then run the
following command:
cd sc10.5-solaris8
./install.sh
The installation script will start a setup wizard to guide you through the rest of the
installation process. Note the installation process requires Unix "zcat" utility.
3. Start the application to get the Host ID
To start SilverCreek move to the installed target directory
(e.g., /home/mary/silvercreekSP10.0) and initiate the application like following:
SilverCreek Pro SP and SS Edition:
bin/test-agent (to start SC test suites and tools) or
bin/browse-agent (to start SC tools only)
SilverCreek Pro SL and SB Edition
bin/browse-agent
Upon SilverCreek startup, you will be given a hostID in the "License File Required" window.
You can also get hostID by executing the command lmhostid found in SilverCreek's "bin"
directory.
Please email your Serial Number, the Host ID and the installed product
(e.g., sc10.5-solaris8.tar.Z) to
This e-mail address is being protected from spambots. You need JavaScript enabled to view it
.
4. Install the license file you received to unlock the software
After receiving the license.lic please place it in SilverCreek's home directory. Now you can try to restart SilverCreek.
Alternatively if you saved the license.lic file received in your email inbox into a folder on your computer you can click the "Import" button to copy it into your SilverCreek root directory when prompted for license.
You should be up and running. If not please write to This e-mail address is being protected from spambots. You need JavaScript enabled to view it .
Back to the top
Extensions for Solaris/Linux Platforms
1. Download the desired SilverCreek extension.
What Works With What will provide you a guide to selecting an appropriate combination of products and extensions based on particular version numbers.
2. Move the downloaded package to SilverCreek's home (root) directory and extract it.
zcat <tarfile> | tar xvf -
Here, tarfile is the name of the file to be extracted. This will place all the files in their correct
place to run with SilverCreek.
3. Restart SilverCreek
Extensions for Windows NT/2000/XP/Windows Server 2003 Platforms 1. Download the desired SilverCreek extension.
What Works With What will provide you a guide to selecting an appropriate combination
of products and extensions based on particular version numbers.
2. An installation wizard will direct you to extract files, just extract these files to SilverCreek's
home (root) directory.
This will place all the files in their correct place to run with SilverCreek.
3. Restart SilverCreek
Windows users should use the Uninstall shortcut found in the SilverCreek program folder. After running the uninstaller it may be necessary to manually delete the remaining directories and shortcuts. This step is necessary when addition files such as the license file have been added to the SilverCreek installation directory.
Users of Solaris and Linux versions of SilverCreek simply need to delete the installation directory.
Frequently Asked Questions about Software and License Installation
This problem is caused by the Solaris operating system's limitation with the number of available file descriptors.
Fortunately, there is an easy workaround:
1) start lmgrd from a /bin/sh script
2) The script should look like this:
#!/bin/sh
ulimit -n 1024
ulimit -H -n 1024
lmgrd [...]
where, [...] is the lmgrd arguments.
This resets the limit to 1024 for lmgrd that resolves the problem.
The result of PING, TELNET, and NSLOOKUP all work and return the expected output. The system environment variable LM_LICENSE_FILE is pointing to the correct license file. However, SilverCreek still returns License Manager Error -12. Another computer with the exact same configuration of hardware and software works fine.
Solution:
This may be due to a problem with the way you have your network set up. When doing a PING, TELNET, or NSLOOKUP, it returns with the expected output because it adds the domain name suffix to the computer name. However, when the license manager tries to connect to the server, the DNS Server does not find it because it does not add the domain name suffix into the search.
If all of your client machines are having this problem, changing the server name to the fully qualified name should fix this:
1. Change the SERVER line in ALL license.lic files on your network, which are located in the root directory of SilverCreek's license server and clients), to have the fully qualified name of the server or IP address.
2. Restart the License Manager on the server and then restart SilverCreek.
If only some of the clients on your network license are having this problem, editing the hosts file on your client systems should fix this:
1. Open your Hosts file located here:
C:\WinNT\system32\drivers\etc
or
C:\Windows\system32\drivers\etc
2. Add your license server to this file. You can find your license server information from the SERVER line of your license.lic file. For example, if your SERVER line looks like this:
SERVER myhostname 4546
If myhostname has IP address 192.168.123.1, you should add the following line to your Hosts file:
192.168.123.1 myhostname
3. Save the changes to the Hosts file.
Here is the message:
> feature removed during lmreread, or wrong SERVER line hostid
> Feature: SilverCreek
> License path: .\license.lic;.\license.dat > FLEXlm error: -92,147 > For further information, refer to the FLEXlm End User Manual, > available at "www.globetrotter.com".
Some possible causes of this message include:
1. There is a typographical error in the license file's SERVER line. Typically, the hostID was not the ID of the server machine.
2. The feature was removed during lmreread but the client is reading an old copy of the license file that still contains the removed feature. Make sure you are using the same license.lic as your server.
3. Check the log messages on the Server and see if it shows that the license was being rejected because there was time difference between the server and client. If this is the case, fixing the date and time difference should fix the problem. See also System clock has been set back.
> Invalid (inconsistent) license key
> The license-key and data for the feature do not match.
> This usually happens when a license file has been altered
> Feature: SilverCreek
> License path: .\license.lic;.\license.dat FLEXlm error: -8,544
Some possible causes of this message include:
1. The license.lic file on the server side is different from the one on the client side.
2. License.lic file has been altered or corrupted somehow during editing and copying on different platforms or in different editors. In this case a new license.lic file has to be re-issued to you. Restart the license server and then reapply license file after editing the new license.lic file.
3. There was time difference between the server and client. If there is, fix the date and time should fix the problem. For details see System clock has been set back
SilverCreek uses FLEXlm ( http://www.macrovision.com/products/legacy_products/flexlm/index.shtml) to manage license files. Any action that puts future-dated files on the license manager machine will result in this error message. Setting the system clock to the past, setting the clock ahead and then back to the present, or getting future-dated files from another source are all examples of such an action.
Solution or Workaround
1: Verify that the date and time on the system are correct. Also verify that AM or PM is set properly.
Select Start > Settings > Control Panel > Date/Time.
2: Verify the time zone is correct.
Windows NT and 2000:
1). Select Start > Settings > Control Panel > Date/Time.
2). Select the Time Zone tab.
Windows XP:
1). Select Start > Control Panel > Date and Time.
2). Select the Time Zone tab.
3. Search for files that are dated in future.
First we need to Verify that there are no hidden files and folders before searching.
Windows NT:
1). Right click the My Computer icon on the desktop and select Explore.
2). Select View > Options.
3). On the View tab verify that:
"Show all files" is selected.
"Hide files of these types" is unselected.
"Hide file extensions for known file types" is unselected.
4). Click Apply and OK.
Windows 2000:
1). Right click the My Computer icon on the desktop and select Explore.
2). Select Tools > Folder Options.
3). On the View tab verify that:
"Show hidden files and folders" is selected.
"Hide file extensions for known file types" is unchecked.
"Hide protected operating system files (Recommended)" is unchecked.
4). Click Yes when prompted.
5). Click Apply and OK.
Windows XP:
1). Right click the My Computer icon on the desktop and select Explore.
2). Select Tools > Folder Options.
3). On the View tab verify that:
"Show hidden files and folders" is selected.
"Hide file extensions for known file types" is unchecked.
"Hide protected operating system files (Recommended)" is unchecked.
4). Click Yes when prompted.
5). Click Apply and OK.
Now we Search the computer's hard drive for files with future file dates.
Windows NT:
1). Select Start > Find > Files or Folders.
2). Select the Date Modified tab and choose Select between.
3). Type in tomorrow's date and 12/31/2099.
4). Click Find Now.
Windows 2000:
1). Select Start > Search > For Files or Folders.
2). Select Search Options.
3). Check the Date box and select Between.
4). Type in tomorrow's date and 12/31/2098.
5). Click Search Now.
Windows XP:
1). Select Start > Search.
2). Choose All Files and Folders.
3). Select Search Options.
4). Check 'When was it modified?' and select Specify Dates.
5). Type in tomorrow's date and 12/31/2098.
6). Click Search Now.
Remove all files and folders whose time/date stamp is greater than 4 hours ahead of the current system time and date. This may require moving them onto another workstation, reloading applications, or in the case of system files, it may be necessary to reinstall the operating system. On Windows XP you can delete C:Windows\Prefetch directory if there are files dated in future there. Windows XP monitors the files that are used when computer starts and also when you start applications using Microsoft's prefetching technology and this often stops Flexlm license programs because it may have recorded incorrect time when system clock time was changed. WARNING: IWL recommends that you make a complete backup of your system before removing any files. IWL cannot guarantee that you can solve problems that result from incorrect operations.
1. Make sure the license server is running properly. Make sure the client is using the exact same license.lic as the server.
2. Make sure there is no firewall between clients and the server. If there is, please read
http://www.iwl.com/Support/sc/install.html#firewall
3. Upgrade SC license server to use the latest Flexlm license manager
Download the latest lmgrd to replace the lmgrd under your license server installation directory then restart the license server and reconnect SC.
You can download an appropriate copy of the latest lmgrd at
http://www.macrovision.com/services/support/flexlm/lmgrd.shtml#unixdownload
4. Restart the license server and watch the log message on license server when the client is trying to connect. See if any helpful diagnostic information can be found there.
5. The DNS issue
Modify the license.lic both on server and client to use the license server's fully qualified domain name (for example, "myserv.mycomp.com" instead of just "myserv").
If this fails to allow the client to access the server, try using the license server's IP address instead of the fully qualified domain name in the above environment variable.
If you are still unable to connect to the server and get the same error condition, you may need to modify the "hosts" file on your client so that it maps the fully qualified domain name of the server to its IP address.
123.456.789.012 myserv.mycomp.com
On Solaris or Linux, the hosts file is /etc/hosts. On Windows XP or 2000, the hosts file is C:\WINNT\SYSTEM32\DRIVERS\ETC\HOSTS. You may need administrator privileges to edit these files.
6. Fix broken TCP/IP stack on client machines
The "connection refused" error could be caused by a corrupted TCP/IP stack on your client machine.
Assuming you specified a port no. to use explicitly in the license.lic on the server such as 4545,
For example:
SERVER myserv 80c671b3 4545
you can test if the TCP/IP connection is possible by doing follows:
From the client machine, try using telnet host port where host and port are the same as on the SERVER line in your license file.
open a DOS command prompt (or Unix shell) and issue the following command:
telnet myserv 4545
If a connection is established, the DOS prompt (or Unix shell) will not be returned since a TCP connection has been established with the license manager service.
However, if a connection is not established this may indicate that the license manager is not running properly or that there is a network communication problem between the client and the server machine. (Close the DOS window (or Unix shell) to end a telnet connection to the license manager.) If network problems are suspected, contact your system administrator for assistance.
You may try to reinstall your TCP/IP stack on WindowsXP by following the instructions at
http://support.microsoft.com/?kbid=299357
You can also re-install the client PC's operating system.
FLEXlm end user FAQ from Macrovision
All information below is copyright 2003 Macrovision Corporation
| Problem: How do I enable the options file? |
| Answer: First you need to create the options file (i.e.daemon.opt). Then add the path to the options file on the VENDOR/DAEMON line in your license file. For example: VENDOR demo c:\flexlm\demo.exe c:\flexlm\demo.opt or VENDOR demo options=c:\flexlm\demo.opt |
|
Last Update: 6/17/2003 |
| Problem: How do you create a report log? |
| Answer: You will need an options file to create the report log. In the options file you will add a REPORTLOG line to create a report log. For example: REPORTLOG +c:\flexlm\demo.rl The plus sign appends new information to the existing report log when you restart the license server. You must restart server to initiate reportlog. |
|
Last Update: 6/17/2003 |
| Problem: I am getting Error -16,287 when I start my server on Solaris. |
| Answer: This problem is caused by the Solaris operating system. Fortunately, there's an easy workaround: 1) start lmgrd from a /bin/sh script 2) The script should look like this: #!/bin/sh ulimit -n 1024 ulimit -H -n 1024 lmgrd [...] where, [...] is the lmgrd arguments. This resets the limit to 1024
|
|
Last Update: 6/17/2003 |
| Problem: Only if the FLEXlm license file Environment Variable is set, in which order the license file is referred to by the client application? |
| Answer: The rule is: (1) VENDOR_LICENSE_FILE takes priority over LM_LICENSE_FILE. (2) Environment variable takes priority over .flexlmrc/registry. (3) Rule #1 takes priority over rule #2: if LM_LICENSE_FILE is set in the environment, but VENDOR_LICENSE_FILE is set in .flexlm/registry, then VENDOR_LICENSE_FILE takes priority over LM_LICENSE_FILE (Rule #1), even though that means that .flexlm/registry takes priority over the environment variable (which conflicts with Rule #2). |
|
Last Update: 7/24/2001 |
| Problem: Windows 2000 systems (laptop/desktop) returns "000000000000" or "FFFFFFFFFFFF" for the Ethernet hostid, when physically disconnected from the network. |
| Answer: This is a known issue with Windows 2000. This problem is associated with it's Media Sense for TCP/IP. In the past, we suggested disabling the Media Sense for TCP/IP on Windows 2000 system as a workaround; and referred the following MS web-page for details: http://support.microsoft.com/support/kb/articles/Q239/9/24.asp However, we no longer recommend the above workaround, since, this problem has been fixed in the FLEXlm v7.2d. For this fix to take affect, both the client application and the vendor daemon has to be upgraded to FLEXlm v7.2d+. |
|
Last Update: 7/24/2001 |
| Problem: The client application fails to checkout a license, and returns FLEXlm Error -14. |
| Answer: FLEXlm Error -14 indicates that the client is not recognizing the hostname of the server. 1. You can put on the SERVER line the IPaddress as the hostname. SERVER IPaddress hostid port 2. On the client machine make sure the hosts file(windows directory) contains the server hostname and ipaddress. 3. Set the environment to port@ipaddress VENDOR_LICENSE_FILE= This e-mail address is being protected from spambots. You need JavaScript enabled to view it (all uppercase) 4.Try putting "this_host" on the SERVER line in place of the machine hostname. |
|
Last Update: 6/18/2003 |
| Problem: How to configure FLEXlm license manager as an NT Service using LMTOOLS.exe? |
| Answer: The Following are the steps to configure and start the FLEXlm license manager as an Windows NT (and Windows 2000) Service: 1. First create you license file (license.dat). It should contain the SERVER line, the VENDOR line, and the FEATURE line(s). 2 Startup LMTOOLS.exe 3. Press the "Configuration using Services" button. 4. Select the "Configure Services" tab. 5. Enter in a Service Name (e.g., demo) and hit the Tab key. The next 3 fields below should be empty. 6. Browse to the path of lmgrd.exe 7. Browse to the path of license.dat 8. Browse to the path of debug.log (it will create a file for you, just choose a path). 9. Mark the "Use Services" option 10. Mark "Start Server at Power Up", if you want license server to start at bootup. 11. Click on "Save Service". 12. Choose Yes to "Save". 13. Select the "Start/Stop/Reread" tab. Make sure your service is highlighted. 14. Click on Start button. You can perform license server status enquiry under the "Server Status" tab. |
|
Last Update: 7/24/2001 |
| Problem: What happens if my server hostname has a space? |
| Answer: Your license server will not start because it will think the second part of the host name is the hostid. You will need to rename the hostname into one word. Otherwise try using the IP address or "this_host" in place of the single word hostname. |
|
Last Update: 7/24/2001 |
| Problem: When I run lmhostid or lmtools in Windows, I get multiple ethernet card addresses. |
| Answer: FLEXlm will detect multiple ethernet cards. You can use any of the valid addresses. We recommend using the first ethernet card address on the list if more than one is listed. |
|
Last Update: 6/17/2003 |
| Problem: Can I start a single license server(lmgrd), if I have separate floating licenses from two different companies? |
| Answer: Yes, you can combine the licenses, but we recommend running separate servers. To combine licenses you need to put in one license file a single SERVER line, all the VENDER/DAEMON lines, and all the FEATURE lines. For example: SERVER ... VENDOR daemon1 VENDOR daemon2 FEATURE f1 daemon1 ... FEATURE f2 daemon2 ... |
|
Last Update: 7/24/2001 |
| Problem: Is there a way to append to the debug.log file after the license server restarts? |
| Answer: Currently, this can only be done through the command line, and not as available through a Windows Service. You can add a plus '+' sign immediately in front of the path for the debug log. Example: lmgrd -c c:\flexlm\license.dat -L +c:\flexlm\debug.log |
|
Last Update: 6/17/2003 |
| Problem: Can I disable the Windows License File Finder dialog box? |
| Answer: This can be disabled only by the Software vendor. This dialog box is displayed when the application does not find a license file or license server. The user is then prompted for a server or license file. |
|
Last Update: 6/17/2003 |
| Problem: The vendor daemon consumes 100% CPU usage when starting the license manager? |
| Answer: There is a possibility that the FLEXlm service paths are too long. Check the path to your license file, debug log and daemon path in your license file. Shorten the paths to under a total of 256 characters. |
|
Last Update: 6/17/2003 |
| Problem: When I checkout an application I get an Error -37 Duplicate selection mismatch for this feature. |
| Answer: If you are using v8.x or below, then you are using 2 different DUP_GROUP values. The DUP_GROUP values are either set in the application or the license file. You cannot use 2 different values for the same FEATURE. The license server will reject the second value that is requested. In the debuglog, you will see this error message. 19:44:56 (demo) Feature f1 parameter mismatch - checkout denied (current: 4000, request: 0)19:44:56 (demo) DENIED: "f1" This e-mail address is being protected from spambots. You need JavaScript enabled to view it (Duplicate selection mismatch for this feature (-37,350)) If you look at the current and request number, this will tell you what DUP_GROUP value you have set for this FEATURE. For example, current: 4000 means you have set this value to LM_DUP_NONE request: 0 means you have set the value to LM_DUP_SITE or zero(0). The current and request must match. |
|
Last Update: 6/17/2003 |
| Problem: The client application fails to checkout a license, and returns FLEXlm Error -15. |
| Answer: Check if there is a firewall between the client and server. Allow firewall access to port numbers. The VENDOR/DAEMON and SERVER lines should have different port numbers. For example, SERVER hostname hostid 27000 DAEMON demo /path/..demo PORT=27005 |
|
Last Update: 6/18/2003 |
| Problem: When I run lmremove and lmdown, FLEXlm returns Error -63. |
| Answer: FLEXlm error -63 indicates that lmutils such as lmremove and lmdown, require the user to be apart of the lmadmin group. If you are on UNIX most likely lmgrd was started with the -2-p option. |
|
Last Update: 6/18/2003 |
| Problem: The client application fails to checkout a license, and returns FLEXlm Error -12. |
| Answer: FLEXlm Error -12 indicates that the client application has problems connecting to the daemon. 1. Check if there is a firewall in between client and server. 2. Check if there is VPN(Virtual Private Network) software installed on client. 3. Check it you are pointing to the correct port@host on the server. 4. Check WINS settings.(Windows) |
|
Last Update: 6/18/2003 |
| Problem: What are the default tcp ports for the lmgrd? |
| Answer: FLEXlm's default ports for lmgrd are between 27000-27009. Therefore if you do not specify a port number in the license, then lmgrd will choose one of these ports. The vendor daemon chooses an open port automatically. It has no range. |
|
Last Update: 6/18/2003 |
| Problem: I am getting an error in the debug log that says, "tcp_s is bad!" |
| Answer: This error means the main socket that the vendor daemon listens on has gone bad. You will need to upgrade the vendor daemon to v7.2 or higher. |
|
Last Update: 6/18/2003 |
| Problem: When I start lmgrd, I get a "CreateProcess error code" |
| Answer: Check the syntax in your VENDOR/DAEMON line. The path to the daemon may be incorrect or you have the path to the options file without "options=" in front of the path. |
|
Last Update: 6/18/2003 |
Download information on dongle device drivers is available to the software publisher on the Macrovision Support Site. Users of applications that use dongles should contact their vendor directly.
Here you can find answers to the following situations:
What is the correct hostid syntax when using a FLEXid in a license file?
The FLEX lm utility lmhostid is not returning the FLEXid number for a Dallas manufactured FLEXid.
How can I remove the FLEXid Drives from my computer systems?
| 1. Problem: What is a dongle? |
| Answer: A dongle is a serialized hardware key attached to a parallel port on a Windows system. A dongle is used to limit or lock software access to whomever has the dongle attached to their system via the associated license file. Our dongle is called a FLEXid. The dongle works in conjunction with FLEX lm as a form of a hostid - just like an Ethernet address can be a form of a hostid. A dongle is automatically supported as a valid hostid by any FLEX lm licensed application. |
|
Last Update: 7/24/2001 |
| 2. Problem: Which operating systems support FLEXids? |
| Answer: FLEXids are supported on systems running Microsoft Windows 95/98/ME/2000/NT/XP. |
|
Last Update: 9/16/2003 |
| 3. Problem: Where can I purchase a FLEXid? |
|
Answer: |
|
Last Update: Feb. 1, 2002 |
| 4. Problem: What are the different types of FLEXids? | ||||||||||||||||||||||||
| Answer: There are four different types of FLEXids supported by FLEX lm . Please refer to the following chart to see which FLEXid is supported by your FLEX lm licensed application.
Note: "n" represents a hex digit in the serial number. * These FLEXids are no longer available. The demand exceeded the maximum available serial numbers. |
||||||||||||||||||||||||
|
Last Update: Feb. 1, 2002 |
| 5. Problem: How do I know if a dongle is from Macrovision or not? |
| Answer: Every FLEXid has a unique serial number printed on it called a "FLEXID". A Macrovision dongle will be labeled with a serial number beginning with FLEXID=6-, FLEXID=7-, or FLEXID=8-, or FLEXID=9-. |
|
Last Update: 9/16/2003 |
| 6. Problem: Can I use more than one FLEXid on a single machine? |
| Answer: Yes. You can use multiple FLEXids on a single system by chaining them together. To chain FLEXids together, simply connect opposite ends to each other. USB's can not be chained to each other like the parallel dongles can. Multiple USB dongles can be plugged into a USB hub. |
|
Last Update: Feb. 1, 2002 |
| 7. Problem: What is the correct hostid syntax when using a FLEXid in a license file? |
| Answer: The following are examples how a FLEXid would appear on a SERVER or FEATURE/INCREMENT line. Floating License controlling which machine can run the License Manager: Node-Locked License controlling which machine can run the application: |
|
Last Update: 7/24/2001 |
| 8. Problem: How do I install a FLEXid? |
| Answer: 1) You will attach the FLEXid to the parallel port or USB port of your Desktop PC or Laptop. You can attach more than one FLEXid on a single parallel port by chaining the FLEXids together. Multiple USB dongles can be plugged into a USB hub. 2) Each combination of FLEXid types and Windows operating system requires a separate FLEXid driver. ISV's that purchase FLEXids from Macrovision will receive a FLEXid installer (can be redistributed) that will install all the necessary device drivers for our FLEXids. 3) Verify the FLEXid is attached and working properly by using a FLEX lm utility, such as lmutil or lmtool s. Check to see if the PC returns the correct FLEXID number for the FLEXid. Anyone can download these FLEX lm end user utilities. |
|
Last Update: 9/16/2003 |
| 9. Problem: How can I determine the FLEXid number? |
| Answer: You can use the FLEX lm utility "lmutil" to list all the hostids for any FLEXid on your system: "lmutil" is FLEX lm 's command-line version of utilities. The correct syntax for using lmutil to find the hostid from the command-line/MS-DOS prompt (c:\>) is: "lmtools.exe" is FLEX lm 's GUI version of utilities. To find the hostid using lmtools.exe, click on the System Settings tab. |
|
Last Update: 7/24/2001 |
| 10. Problem: The FLEX lm utility lmhostid is not returning the FLEXid number for a Dallas manufactured FLEXid. |
| Answer: Be sure the FLEXid contains a FLEXID=8 label on it. Be sure the FLEXid is installed on the parallel port of a Windows operating system. Reinstall the appropriate FLEXid drivers for your version of Windows platform. The device drivers are available to our ISV's from our web site via a FLEXid installer, which ISV's can redistribute to their end users. Note: Dallas does not offer Alpha-NT support for their dongles. |
|
Last Update: 7/24/2001 |
| 11. Problem: How can I remove the FLEXid drivers from my computer systems? |
| Answer: You may uninstall the FLEXid drivers from Start->Settings->Control Panel; Click Add/Remove Programs; Highlight "Globetrotter FLEXID Drivers"; Click the Add/Remove button. |
|
Last Update: 7/24/2001 |
| 12. Problem: The FLEXid I have sent to our customer with our licensed software does not work if any other dongle is attached to the computer system. Our dongle works if it is the only dongle connected to the system. |
| Answer: Most computer systems have only one parallel port. However, by connecting one FLEXid on top of the other, you can attach multiple FLEXids to the single parallel port. FLEX lm is capable of detecting all the attached FLEXids. Workaround: Issue a new license to the customer based on the FLEXid they are currently using with the other FLEX lm based software. This way customer will have one FLEXid to authenticate two or more software. (Note: Ask the customer to return your dongle.) |
|
Last Update: 7/24/2001 |
| 13. Problem: I bought a dongle directly from a Rainbow representative. How can FLEX lm detect it correctly as a hostid? |
| Answer: Dongles purchased directly from Rainbow (or Dallas) will not work with FLEX lm unless you implement Vendor-Defined hostids. You would issue keys based on the customized hostid you created. Vendor-defined hostid is documented in the FLEX lm Reference Manual. |
|
Last Update: 7/24/2001 |
| 14. Problem: On Windows 98, the Dallas manufactured FLEXID disappears on a first boot, but reappears on the second boot. Have you seen this problem before? |
| Answer: Yes, this is a known issue with Windows 98. Simply, reinstall the latest FLEXid device driver for MS Windows 98. These drivers are available to you by your software vendor. |
|
Last Update: 7/24/2001 |
| 15. Problem: Do FLEXids occupy a COM port so that it cannot be used for anything else (such as a modem)? Which COM port the dongle is attached to? |
| Answer: Dongles are parallel devices. You should attach dongle to the Parallel port only. If the parallel port is occupied by the dongle, you can still connect another parallel device, such as printer, on top it (dongle). |
|
Last Update: 7/24/2001 |
| 16. Problem: I can't find Windows 2000 drivers for FLEXID=6 or FLEXID=8. |
| Answer: FLEXid drivers for Windows NT should work for Windows 2000 system as well. The FLEXid installer will install the NT driver automatically. |
|
Last Update: 7/24/2001 |
| 17. Problem: Does FLEX lm support USB FLEXids? |
| Answer: Yes. FLEXlm v7.2g and higher includes support for the Alladin USB dongle. If you are using Alladin's USB dongle on an XP machine, you need FLEXid drivers v1.05 or higher (included in the FLEXlm v8.1a SDK). |
|
Last Update: Jan. 24, 2002 |
| 18. Problem: If the FLEXid-user has more than one parallel port on his system, does it matter if they connect their dongle to LPT1 or LPT2? |
| Answer: By default you need to connect it to parallel port LPT1. However Rainbow dongle setup utility will allow you to configure a different port. |
|
Last Update: 07/24/2001 |