A doubt it. This is a different computer and I don't have any client set up to work with this NEW HOSTNAME. All clients are currently working with other "original" TSM server.
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Thursday, January 06, 2005 11:17 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Upgradedb question On Jan 6, 2005, at 10:22 AM, Yury Us wrote: > ANR9999D sminit.c(656): ThreadId<20> SM Failed to Initialize - Time > Out. Yury - It's conceivable that this message is spurious, resulting from a client connection attempt while dsmserv was doing conversion work and thus not in a position to accept sessions. If you're invoking it in foreground, console mode, then setting server option COMMmethod NONE should prevent accesses; or change TCPPort to an unusual value during the conversion. You may want to pass this by TSM Support, to be certain. Richard Sims