[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::pwv50ift

Title:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Notice:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Moderator:CPEEDY::KENNEDY
Created:Fri Dec 18 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4319
Total number of notes:18478

4270.0. "5.0E License problem" by COL01::SENSCHE () Tue Apr 22 1997 08:38

Hello,

since a few days a customer is having trouble with his PW-Clusters.
He has serverbased licensing with enough available points as seen with 
$ SHOW LICENSE /USAGE. But the clients sometimes can not connect and
$ ADMIN/ANA shows "No server license for client - access denied".
Clients are WindowsNT 3.51,TCP/IP-only. PW is V5.0E ECO1. 
We had the problem last week and with the information off the license-logfile
and some entries in this conference i adjusted CTLPAGES, which seemed to work
until today. Today there are no special entries in the logfiles.
One strange thing i can see is that with nbtstat -a <server> i get
names from PWRK$LserverR02 to PWRK$serverR07, on another Cluster even to 
PWRK$LserverR0M. 
Licenseserver is not running on any of these systems.

Customer will enable verbose license logging in the evening.
Any ideas in the meantime?


Volker
T.RTitleUserPersonal
Name
DateLines
4270.1VMSNET::P_NUNEZTue Apr 22 1997 10:2233
    
>since a few days a customer is having trouble with his PW-Clusters.
>He has serverbased licensing with enough available points as seen with 
>$ SHOW LICENSE /USAGE. But the clients sometimes can not connect and
>$ ADMIN/ANA shows "No server license for client - access denied".
>Clients are WindowsNT 3.51,TCP/IP-only. PW is V5.0E ECO1. 
    
    Possibly the pwrk$license_r process aborted or was hung?  Any
    pwrk$logs:pwrk$license_registrar.dmp files?  Anything in
    pwrk$logs:pwrk$license_r_<nodename>.log?
    
>We had the problem last week and with the information off the license-logfile
>and some entries in this conference i adjusted CTLPAGES, which seemed to work
>until today. Today there are no special entries in the logfiles.
>One strange thing i can see is that with nbtstat -a <server> i get
>names from PWRK$LserverR02 to PWRK$serverR07, on another Cluster even to 
>PWRK$LserverR0M. Licenseserver is not running on any of these systems.

    Don't worry about those odd netbios names you got back from nbtstat. 
    They're used by the PWRK$LICENSE_R process to communicate with clients
    attempting to establish a session with the server.  The registrar is
    trying to determine if the client is properly licensed.
    
>Customer will enable verbose license logging in the evening.

    I hope this means on the pwrk$license_r process (pwrk$LrLogVerbose
    defined)?
    
    Also need to provide the version of VMS and the output from SHOW
    LICE/FULL PWLMVMSCU05.00.  
    
    Paul
    
4270.2some more infoCOL01::SENSCHETue Apr 22 1997 11:0686
Paul,

the pwrk$license_r process has not aborted, nor is he hanging. Also no
*.dmp-files. There are some entries in the logfile, but they are related
to some remoteboot DOS_Clients, that are still around and use DECnet.

17-APR-1997 23:25:25.00 INIT_LOGFILE: 
	OPEN: PATHWORKS for OpenVMS License Registrar Startup
17-APR-1997 23:25:25.00 MESSAGE: 
	Image Identification: V5.0-510E
21-APR-1997 08:22:44.00 MESSAGE: 
	PingConnect [4,70]: Cannot receive from client license responder
	Client Address: "DDO0AE         R", Transport: DECnet
	XTI error in IC at line 3126
	XTI error code t_errno = 9 ("event requires attention")
	XTI event code = 0X0010 ("disconnect received")
	XTI system error code = 0
22-APR-1997 07:47:38.00 MESSAGE: 
	PingConnect [4,136]: Cannot receive from client license responder
	Client Address: "DDO0AE         R", Transport: DECnet
	XTI error in IC at line 3126
	XTI error code t_errno = 9 ("event requires attention")
	XTI event code = 0X0010 ("disconnect received")
	XTI system error code = 0
22-APR-1997 08:40:12.00 MESSAGE: 
	PingConnect [4,143]: Cannot receive from client license responder
	Client Address: "DDO0AC         R", Transport: DECnet
	XTI error in IC at line 3126
	XTI error code t_errno = 9 ("event requires attention")
	XTI event code = 0X0010 ("disconnect received")
	XTI system error code = 0
22-APR-1997 09:42:33.00 MESSAGE: 
	PingConnect [4,159]: Cannot receive from client license responder
	Client Address: "DDO0E5         R", Transport: DECnet
	XTI error in IC at line 3126
	XTI error code t_errno = 9 ("event requires attention")
	XTI event code = 0X0010 ("disconnect received")
	XTI system error code = 0



Yes, logging will be done on the pwrk$license_r process.

The OpenVMS Version is V6.2-1H3. UCX is 4.0 Ecolevel 2.

Here is the License info:

DXCW3H>>>show lic /full pwlmvmscu05.00

Active licenses on node DXCW3H:

PWLMVMSCU05.00
        Producer: DEC
        Units: 180000
        Version: 0.0
        Release Date: (none)
        Termination Date: (none)
        Availability: 0
        Activity: 100

DXCW3H>>>

DXCW3H>>>sh lic /usage

View of loaded licenses from node DXCW3H                22-APR-1997 16:04:55.21

------- Product ID --------   ---- Unit usage information ----
Product            Producer       Loaded  Allocated  Available
DECPS-DC           DEC              1000          0       1000
DFG                DEC              1000          0       1000
NET-APP-SUP-200    DEC              2200       2200          0
NET-APP-SUP-300    DEC              2200       2200          0
OPENVMS-ALPHA      DEC               400        400          0
OPENVMS-ALPHA-ADL  DEC              1000        100        900
PWLMVMSCU05.00     DEC            180000      99200      80800
RDB-RT             DEC              1000          0       1000
SLS-REMOTE-MGR     DEC              2200       2200          0
VOLSHAD            DEC              2200       2200          0
DXCW3H>>>




Any more information needed ?


Volker
4270.3VMSNET::P_NUNEZTue Apr 22 1997 14:019
    Volker,
    
    Don't see anything obvious.  You may have to resort to getting a
    network trace of the failing connection attempt and submitting an
    IPMT.  
    
    Sorry,
    
    Paul
4270.4Thank youCOL01::SENSCHETue Apr 22 1997 18:113
    Thank you Paul. OK, it's IPMT time again....
    
    	Volker