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/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

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" <ADSM-L AT VM.MARIST DOT EDU> 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" <ADSM-L AT VM.MARIST DOT EDU>
>
> 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 <
> Thomas.Denier AT jeffersonhospital DOT org> 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
> sstackwick AT jasi DOT com