The problem turned out to be due to the winnt\....etc\services file.  
Somehow, either from some of the win2k security patches or the Veritas 
patches, the services file lost most of the port number mappings for 
various NetBackup daemons.  Unfortunately, the error message wasn't the 
most helpful in tracking this down.


barry

        
On Wednesday, October 22, 2003, at 11:56 AM, Barry Lustig wrote:

> I should have mentioned that I first upgraded to 4.5FP3 and then up to 
> 4.5FP5.
>
>
> barry
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>

and

> Last night, I upgraded my 4.5 BusinessServer to 4.5FP5.  The first 
> problem was a missing entry in windows services (bpdbm) file that 
> stopped daemons from starting.  I tracked that down and fixed it.  The 
> problem I'm having now is with starting vmd.  Everything the process 
> tries to start it fails with a windows event error of:  The NetBackup 
> Volume Manager service terminated with service-specific error 58.
> I created the ...\Volmgr\debug\daemon directory to get a debugging 
> trace from vmd.  The error I get is:
>
>       00:36:53.559 [3336.2784] <4> vmd: INITIATING
>       00:36:53.606 [3336.2784] <4> vmd: Host name is neo
>       00:36:53.606 [3336.2784] <16> vmd: vmd:  Unable to get daemon lock 
> file
>       00:36:53.606 [3336.2784] <4> vmd: terminating - successful (0)
>
> Has anyone seen this kind of an error before?  Any suggestions on 
> getting it back up and running?
>
> By the way, the Win2k box is running at SP4 with all of the lastest 
> security patches.