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

Conference pcbuoa::server_works

Title:	Server_works

Moderator:	PCBUOA::IS_SYSTEM

Created:	Fri Jun 30 1995
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	291
Total number of notes:	1063

209.0. "The handle is null" by VMSNET::C_MANDERSON () Mon Feb 10 1997 15:28

    Hi,
    
    When attempting to access an Alphaserver 8400 running 4.0b unix,
    receive the error "The handle is null". This error loops and does not
    allow the user to break away., 
    
    Serverworks is vrsion 2.1 and Manageworks is V2.2. This is installed on
    a 3.51 NT workstation.  This same client attempts to open an Unix 4.0a
    on an AlphaStation 3000-300x from this same client via the
    autodiscovery and this appears to open just fine.
    
    Could this be fixed by the new autotest.exe? If yes, if the
    autotest.exe available on the ftp.digital.com site?  If not, any thing
    I should check for that may/may not have been installed on the unix
    box?
    
    thanks1
    
    cindy

T.R	Title	User	Personal Name	Date	Lines
209.1	Digital Unix Agent in SW 2.2	PCBUOA::BRACKEN		`Mon Feb 10 1997 17:46`	2
	The Server Works 2.2 Agent is newer. You should try that first
209.2		SUTRA::16.36.2.177::Bats	Speeding, speeding, I'm always speeding	`Wed Feb 12 1997 00:02`	34
	I already answered this some notes back: The ServerWorks kits have an interesting error in the "SWEXTOMM.INI" that the installation creates. Edit it with an text editor and you will find references to directories for BMP files which you probably don't have. Like F:\..... The reason it only does this for Unix (and also VMS boxes) is that the ServerWorks has seen that this Server.Digital machine is a Unix or VMS system and is trying to probe if the KRCM thingie is installed in it. The .BMP file for it, that normally get's put into the Toolbar, when it finds this to be the case is however pointing this nice non-existant drive/directory. And if you install it in a Long File name directory, c:\Program Files\mworks You'll get entries like: c:\program\mworks Which obviously does not exist. Therefor after installation, take your favorite editor and modify mworks\swextomm.ini to straighten out the file location errors. Pjotrr
209.3	we turned your fix into a techtip too!	PCBUOA::WHITEC	Parrot_Trooper	`Wed Feb 12 1997 12:10`	9
	Hi Peter, I also wrote a techtip and put it on our website. We now have a special heading for ServerWORKS etc... Go to akin40.ako.dec.com and do a search for handle full.....should work, chet
209.4	Well, .....not 'exactly'!	PCBUOA::WHITEC	Parrot_Trooper	`Wed Feb 12 1997 12:19`	8
	well, I checked it, I'm not a WEB GURU by any stretch of the imagination. But here's the EXACT location. akin40.ako.dec.com/dataroot/internoteshtml/TECHTIPS/2376.htm chet
209.5	should this be put on external www	NNTPD::"[email protected]"	Eric R Schott	`Tue May 06 1997 09:28`	8
	Hi Shouldn't this tip get out to: http://www.windows.digital.com/support/techtips/server/prioristips.stm [Posted by WWW Notes gateway]
209.6	Done!	PCBUOA::WHITEC	Parrot_Trooper	`Tue May 06 1997 10:06`	3
	I can make that happen. Chet