Author: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Date: Wed, 13 Dec 2000 16:47:51 -0500
Well, I'm stumped. I've got a Win2K system running the Win32 client; was at 3.1.0.6, now at 3.7.2.01. It's been running fine for months, with PASSWORDACCESS GENERATE in dsm.opt. THe scheduler service
Author: Doug Thorneycroft <dthorneycroft AT LACSD DOT ORG>
Date: Wed, 13 Dec 2000 14:32:06 -0800
Just a guess, but if you're runing the scheduler service, you probably need run dsmcutil to update the password in the scheduler service. Try setting the Scheduler Service to manual, reboot, and see
Wanda - I don't know if your Windows case is similar, but we had a comical case of this in AIX. The AIX system had the v2 ADSM client, and then the AIX operating system was upgraded, and it came wit
Author: Jack Palmadesso <Jack.Palmadesso AT SWPC.SIEMENS DOT COM>
Date: Thu, 14 Dec 2000 07:28:53 -0500
Try using the dsmcutil program in the client directory. I believe the correct syntax is: dsmcutil showpw /node:nodename This should show you what password is in the registry. dsmcutil updatepw /node:
Author: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Date: Fri, 15 Dec 2000 10:54:34 -0500
Thanks Jack When I run dsmcutil showpw, it shows the correct password in the registry for this machine. Then when I reboot and run dsmcutil showpw again, it says it can't find the registry key. It ap