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

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

146.0. "Hubwatch for VMS fails with access violation" by BACHUS::FOLENS () Thu Feb 04 1993 10:22

I've installed hubwatch fo VMS on my VS4060. When I start it up with the 
parameters of the DECagent named dechub.mlo.dec.com the icon of the
hub appears and then the program exits with an exception.
Am I giving the wrong parameters?

-Geert-

BHT362> mcr hubwatch -x 16.123.96.253 -c public
(W): NMS_DIR is not defined - using [.uid] directory
(W): Using SYS$MANAGER:HUBWATCH_AGENTS.TXT
(D):
HUB CONFIGURATION:
(I): ___________________________________________________________________________
(D): Slots:     1       2       3       4       5       6       7       8
(D): Cards:     DETMR   DS90L+  ?       DS90L   DECMR   Empty   DENMA   DEWGB
(I): ___________________________________________________________________________
(D): retry[1/0/12] (slot=1[1/0/1],vw=1,rq=5668e0)

(D): Slot 1: Port 1:  status = DISCONNECTED (OFF)
(D): Slot 1: Port 2:  status = DISCONNECTED (OFF)
(D): Slot 1: Port 3:  status = DISCONNECTED (OFF)
(D): Slot 1: Port 4:  status = DISCONNECTED (OFF)
(D): Slot 1: Port 5:  status = DISCONNECTED (OFF)
(D): Slot 1: Port 6:  status = DISCONNECTED (OFF)
(D): Slot 1: Port 7:  status = DISCONNECTED (OFF)
(D): Slot 1: Port 8:  status = DISCONNECTED (OFF)
(D): Slot 2: Port 1:  status = DISCONNECTED (OFF)
(D): Slot 2: Port 2:  status = DISCONNECTED (OFF)
(D): Slot 2: Port 3:  status = DISCONNECTED (OFF)
(D): Slot 2: Port 4:  status = DISCONNECTED (OFF)
(D): Slot 2: Port 5:  status = DISCONNECTED (OFF)
(D): Slot 2: Port 6:  status = DISCONNECTED (OFF)
(D): Slot 2: Port 7:  status = DISABLED
(D): Slot 2: Port 8:  status = DISCONNECTED (OFF)
(D): Slot 4: Port 1:  status = DISCONNECTED (OFF)
(D): Slot 4: Port 2:  status = DISCONNECTED (OFF)
(D): Slot 4: Port 3:  status = DISCONNECTED (OFF)
(D): Slot 4: Port 4:  status = DISCONNECTED (OFF)
(D): Slot 4: Port 5:  status = DISCONNECTED (OFF)
(D): Slot 4: Port 6:  status = DISCONNECTED (OFF)
(D): Slot 4: Port 7:  status = DISCONNECTED (OFF)
(D): Slot 4: Port 8:  status = DISCONNECTED (OFF)
(D): Slot 5: Port 1:  status = DISCONNECTED (OFF)
(D): Slot 5: Port 2:  status = ONLINE
(D): Slot 5: Port 3:  status = ONLINE
(D): Slot 5: Port 4:  status = DISABLED
(D): Slot 5: Port 5:  status = DISABLED
(D): Slot 5: Port 6:  status = DISABLED
(D): Slot 8: Port 1:  status = ONLINE
(D): Slot 8: Port 2:  status = ONLINE
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000001, PC
=002EE29F, PSL=03C00000
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           002EE29F  002EE29F
                                                           002EE327  002EE327
                                                           002EE623  002EE623
                                                           002EDADD  002EDADD
ONEHUB          main                            65565      0000062F  0002AB5F
T.RTitleUserPersonal
Name		DateLines
146.1had similar access violationZPOVC::SINSPSWed Nov 24 1993 05:1431
    Hi, nobody can advise on the problem ?
    
    My customer has encountered similar access violation as follows :-
    
    %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
    address=00000000, PC=0003A5A1, PSL=03C00004
    
    Improperly handled condition, image exit forced.
    
    	Signal arguments		Stack contents
    
    	Number = 00000005		   200C0000
    	Name   = 0000000C		   7FF10854
    		 00000000		   00119954
    		 00000000		   00000001
    		 0003A5A1		   00112B90
    		 03C00004		   7FF1085A
    					   00115EE4
    					   7FF10858
    					   001593CA
    					   00304CB4
    
    Register dump
    
    R0 = 00000000	R1 = 003689C8	R2 = 00000008	R3 = 00000006
    R4 = 0067CF28	R5 = 000000BE	R6 = 006756A8	R7 = 7FF1080C
    R8 = 7FF10808	R9 = 00304CB4	R10= 00000000	R11= 00304D3E
    AP = 7FF107C4	FP = 7FF10784	SP = 7FF10800	PC = 0003A5A1
    PSL= 03C00004
    
    - LEH
146.2More details, please.SLINK::HOODI'd rather be surfingWed Nov 24 1993 13:466
Re: .1
What version?
What was happening when the crash occurred?

Tom H
HUBsquash development
146.3ZPOVC::SINSPSThu Nov 25 1993 07:2515
    re: .2
    
    > What version?
    
    	version 2.0
    
    >What was happening when the crash occurred?
    
    The customer mentioned that he clicked on the "minimize" of the window.
    
    Any idea ?
    
    
    	- LEH
146.4Need more detailsQUIVER::HAROKOPUSMon Nov 29 1993 13:0410
    What windows were up when he did this and which window did he try
    to minimize.  Was it the fornt panel display or one of the
    module windows?
    
    I haven't seen this happen before so we'll need more information
    on exactly what your customer did to make this happen.
    
    Thanks,
    
    Bob
146.5more accviosKYOSS1::WALKERClarke Walker, NJ DC, DTN:323-4040Fri Dec 15 1995 14:3612
    I am getting access violation using:
    
    	HubWatch V3.1.3
    	OpenVMS V6.1
    	90Agent firmware 3.0.1  (replace module since 2.5 couldn't see
    				 any ot the IP addresses on this network)
    
    So far it happens after I open a 90TL module window and after I click 
    on any of the more info (tree, arrow, bridge, statistics) for a 90FL
    module.
    
    Thanks.