![]() |
Telelogic System Architect (steve huntington) | ![]() |
Topic Title: Running License Manager as a service in Windows 2003 Server Topic Summary: Services in Windowns 2K3 Created On: 9-Aug-2005 18:47 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Is it possible to run the License Manager as a service in Windows Server 2003? If not how are you suspose to keep the tool operational for extended periods of time?
|
|
![]() |
|
![]() |
|
Yes it is possible. You should contact Tech support; they can give you a full write up on how to do it.
|
|
![]() |
|
![]() |
|
Matthew, Can you post the response from Tech Support? |
|
![]() |
|
![]() |
|
Hi - I asked that question about 2 or 3 months ago and received an method to do this using the NT "SRVANY" tool. After running through the process, I get a mysterious runtime failure that I haven't been able to figure out. I think it launches the LM, but somehow an error gets generated that SRVANY can't handle and it dies.
|
|
![]() |
|
![]() |
|
We use a tool called FireDaemon to run LM as a service.
More here: www.firedaemon.com Edited: 6-Sep-2005 at 12:12 by Mike Lovett |
|
![]() |
|
![]() |
|
Andrea,
I'm posting the instructions below. However, the instructions specify use of some files that Tech Support gives out; you should contact them if you need those files and wish to follow these instructions: There are advantages to running License Manager as a service. The application must be running at all times for users of System Architect to checkout and use a license. Since License Manager is not a Windows® NT service it cannot be run as one without the use of the Microsoft Windows® NT Resource Kit and its SRVANY.EXE utility. The three files needed from the NT Resource kit to setup any application as a service under NT are: SRVANY.EXE, INSTSRV.EXE, and SRVANY.WRI. WARNING: There are implications and precautions stated in the SRVANY.WRI document which are not described here. Before following these instructions you must first read the SRVANY.WRI document. Since these instructions will require the edit of the NT registry, please be aware that improper modification of the system's registry may cause unpredictable results. User's should have a complete understanding of system and registry backup procedures. NOTE: If you have a special domain account that you intend to use to run this service, you should log into the server with this account and install the License Manager under this account. The account should have the “Logon as a service” priviledge. Before you begin, install License Manager and get it working not as a service. Once working and servicing the clients with no problems then follow these instructions. CONSIDERATIONS: -The domain account that will be used to run the service should be account that is used to install the license manager. -The license manager should maintain its Common Path on the same server where the service runs. This location should be set up as a shared folder and SA users should have read/write access to it. -The domain account used to run the service should have local administrator privileges to the server and have the permission “Log on as a service” in the server’s local security policy. -The program SRVANY.EXE is actually responsible for running SANETMGR.EXE as a service. SANETMGR.EXE was not designed to run at a native NT service. Popkin has plans to change this in future releases. Follow these steps to setup License Manager as a service: 1. Copy SRVANY.EXE and INSTSRV.EXE to your %windir% folder (typically, C:\WINNT) 2. From a command prompt use INSTSRV to install SRVANY.EXE as a service and give it a name that will help you identify it. Here is an example of how to do this: c:\winnt> INSTSRV SANETMGR c:\winnt\srvany.exe a. If this command is executed properly then a message like the following will be displayed: "CreateService SUCCESS Don't forget!!! You must now go to the Control Panel and..." 3. Run the registry editor program (regedt32) from Start>Run. Under the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SANETMGR, create a 'Parameters' key. 4. Under the newly created Parameters key, create an 'Application' value of type REG_SZ and specify the full path of the SANETMGR.EXE application (including the file extension). For example: a. Application: REG_SZ: c:\sysarch\SANETMGR.exe 5. Find the SANETMGR service via the services applet. Set the startup as automatic. That gives you the gist of it, but is actually only the first page of an eight page document which includes pictures. I would contact Tech Support for the full document. Edited: 6-Sep-2005 at 20:37 by Telelogic System Architect Moderator |
|
![]() |
|
![]() |
|
This is a bit off topic but in SA 10.3 there is an entirely new and much improved licensing mechanism. The new license server is specificaly designed to run as a Windows service so you no longer need to go through all of the machinations detailed in this topic. See the installation guide for SA 10.3 for more info on how to setup a license server.
|
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.