Andy, I'm not at the customer anymore, although I might get remote access to the client at some future date. Believe it or not, I actually ran that command (duh, never made the connection) yesterday morning and I eventually cancelled it because it never came back. So I must say your diagnosis seems spot on. Also, Richard Sims pointed me to dsmerror.log this morning, and it showed:
02/12/2009 22:25:52 cuGetFSQryResp: Received rc: -50 from sessRecvVerb 02/12/2009 22:25:52 fsCheckAdd: received error from server query response 02/12/2009 22:25:52 ANS5250E An unexpected error was encountered. TSM function name : vssInitBackupSpec TSM function : fsPrepareFilespace() returned '-50' TSM return code : -50 TSM file : vssback.cpp (1577) So, definitely a bug. I guess it's time to hit the Knowledge Base. Steve On Fri, Feb 13, 2009 at 9:52 AM, Andrew Raibeck <[email protected]> wrote: > Steve, this is almost certainly a VSS issue non-specific to TSM (except > that TSM uses VSS). > > Put the following into a script (say, vsslist.cmd), then run it: > > @echo off > echo %date%%time% > vssadmin list writers > echo %date%%time% > > How long does vssadmin list writers take to complete? > > Best regards, > > Andy > > Andy Raibeck > IBM Software Group > Tivoli Storage Manager Client Product Development > Level 3 Team Lead > Internal Notes e-mail: Andrew Raibeck/Tucson/i...@ibmus > Internet e-mail: [email protected] > > IBM Tivoli Storage Manager support web page: > > http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html > > > The only dumb question is the one that goes unasked. > The command line is your friend. > "Good enough" is the enemy of excellence. > > "ADSM: Dist Stor Manager" <[email protected]> wrote on 02/13/2009 > 08:35:37 AM: > > > [image removed] > > > > Re: TSM Client GUI hanging at initializing > > > > Steve Stackwick > > > > to: > > > > ADSM-L > > > > 02/13/2009 08:38 AM > > > > Sent by: > > > > "ADSM: Dist Stor Manager" <[email protected]> > > > > Please respond to "ADSM: Dist Stor Manager" > > > > Here's the output from the trace. Looks like Andy's VSS thoughts were > right > > on, because there's kind of a long gap (almost 4 hours!) between the dsm > > start and it's appearance: > > > > 02/12/2009 17:25:05.745 [000700] [1096] : vssreq.cpp (1416): > > VssRequestor::InitializeVss(): VSS[SetBackupState] > > 02/12/2009 17:25:05.745 [000700] [1096] : vssreq.cpp (2160): > > VssQuerySystemWriters(): Entry --- querying for files to exclude from > > backup.. > > 02/12/2009 17:25:05.745 [000700] [1096] : vssreq.cpp (2166): > > VSS[GatherWriterMetadata] > > 02/12/2009 17:25:05.745 [000700] [1096] : vssreq.cpp (8431): > > VssRequestor::QueryStatus(): VSS - waiting for asynchronous operation to > > complete for caller 'VssQuerySystemWriters()' > > 02/12/2009 21:05:25.427 [000700] [1096] : vssreq.cpp (2185): > > VssQuerySystemWriters(): Asynchronous GatherWriterMetadata finished. > > 02/12/2009 21:05:25.427 [000700] [1096] : vssreq.cpp (2189): > > VSS[GetWriterMetadataCount] > > 02/12/2009 21:05:25.427 [000700] [1096] : vssreq.cpp (2201): > > VssQuerySystemWriters(): Number of writers that responded: 7 > > > > Now, what to do? I''ve told the admin that they may have a problem with > VSS > > on this server, but maybe it's a client bug? > > > > Steve > > On Thu, Feb 12, 2009 at 5:15 PM, Andrew Raibeck <[email protected]> > wrote: > > > > > My guess is that the slow startup is VSS-related. > > > > > > Try adding this to your options file: > > > > > > traceflags service > > > tracefile c:\somefilename > > > > > > (you can name the trace file whatever you want, enclose in double > quotes if > > > the file name contains blanks) > > > > > > Then start dsmc and wait for the prompt to appear. > > > > > > After you get the prompt, quit out of the client. > > > > > > Then look in the trace... while much of it might not make sense, what > you > > > want to focus on is the time stamps that begin each line of trace > output. > > > Look for a large gap between two trace lines, which would indicate at > that > > > point in the trace, the client attempted to call some function and > > > experienced a delay. > > > > > > Alternatively, it might not be one big time gap, but lots of smaller > (but > > > not insignificant) gaps in time. > > > > > > Best regards, > > > > > > Andy > > > > > > Andy Raibeck > > > IBM Software Group > > > Tivoli Storage Manager Client Product Development > > > Level 3 Team Lead > > > Internal Notes e-mail: Andrew Raibeck/Tucson/i...@ibmus > > > Internet e-mail: [email protected] > > > > > > IBM Tivoli Storage Manager support web page: > > > > > > http://www.ibm.com/software/sysmgmt/products/support/ > > IBMTivoliStorageManager.html > > > > > > > > > The only dumb question is the one that goes unasked. > > > The command line is your friend. > > > "Good enough" is the enemy of excellence. > > > > > > "ADSM: Dist Stor Manager" <[email protected]> wrote on 02/12/2009 > > > 05:07:55 PM: > > > > > > > Re: TSM Client GUI hanging at initializing > > > > > > > > Steve Stackwick > > > > > > > > to: > > > > > > > > ADSM-L > > > > > > > > 02/12/2009 05:09 PM > > > > > > > > Sent by: > > > > > > > > "ADSM: Dist Stor Manager" <[email protected]> > > > > > > > > Please respond to "ADSM: Dist Stor Manager" > > > > > > > > Note that, on the same machine, I just installed the SQL Server TDP > and > > > it > > > > works just fine, connects to the TSM server, backs up, etc. This has > got > > > to > > > > be a client bug. > > > > > > > > On Thu, Feb 12, 2009 at 4:57 PM, Thomas Denier < > > > > [email protected]> wrote: > > > > > > > > > -----Steve Stackwick wrote: ----- > > > > > > > > > > >I have a W2K3 SP2 32bit server whose brand new TSM 5.5.1 client > > > > > >install is behaving peculiarly. The GUI hangs at Initializing > > > > > >(though it does start after a *LONG* time), the command line hangs > > > > > >at an open window, likewise. > > > > > >The usual suspects: this is not a cluster, and the admin sez he > > > > > >tried to apply the VSS fix and was told it was superseded by what > > > > > >was already on the machine. Any clues? > > > > > > > > > > Is there any chance that the DNS servers are specificed incorrectly > > > > > and you are waiting for a succession of queries to time out? The > > > > > quick test for this is to specify the server address in dotted > > > > > decimal form. This eliminates any dependence on DNS, and hence > > > > > will eliminate the delay if it is due to DNS problems. > > > > > > > > > > > > > > > > > > > > > -- > > > > Stephen Stackwick > > > > Jacob & Sundstrom, Inc. > > > > 401 East Pratt St., Suite 2214 > > > > Baltimore, MD 21202-3003 > > > > (410) 539-1135 * (866) 539-1135 > > > > [email protected] > > > > > > > > > > > -- > > Stephen Stackwick > > Jacob & Sundstrom, Inc. > > 401 East Pratt St., Suite 2214 > > Baltimore, MD 21202-3003 > > (410) 539-1135 * (866) 539-1135 > > [email protected] > -- Stephen Stackwick Jacob & Sundstrom, Inc. 401 East Pratt St., Suite 2214 Baltimore, MD 21202-3003 (410) 539-1135 * (866) 539-1135 [email protected]
