On 18 dec 2008, at 06:01, Steven Harris wrote:

Thanks for the reply Wanda

Yep tried all that.  In the end application of the latest driver
6.1.9.9
fixed the problem.  Why the old one stopped working is inexplicable,
alignment of the planets or a stray cosmic ray perhaps?

the must have been a reason for the release of a new version, so maybe
the old version had a bug that would indeed cause it to stop working
indefinitely.

Regards

Steve.




            Wanda Prather
            <wanda.prather@JA

SI.COM>                                                    To
            Sent by: "ADSM:           ADSM-L AT VM.MARIST DOT EDU
            Dist
Stor                                                  cc
            Manager"
            <[email protected]
Subject
            .EDU>                     Re: [ADSM-L] IBMTape driver
issues
                                      on Win2K3

            18/12/2008 01:10
            PM


            Please respond to
            "ADSM: Dist Stor
                Manager"
            <[email protected]
                  .EDU>






Hm.
- Make sure the Windows Removeable Media service is stopped and
disabled.
Doesn't normally cause exactly that problem, but obviously something
has
changed.

-If you look at the TS3310 via its web interface, does it still show a
control point defined on a drive?
-Have you checked its web interface for errors in its log?
-Are any drives offline in the library?

If Windows can't see the control point, TSM can't.  I'd be inclined to
define an alternate control point on a different drive and
rediscover the
hardware with Windows, just to see if it pops up like it should.

W






On Wed, Dec 17, 2008 at 12:17 PM, Steven Harris
<sjharris AT au1.ibm DOT com>wrote:

Hi All

I wonder if any of you have some insight.

Windows 2003 SP1 running TSM 5.4.4.0  IBMtape driver 6.1.9.8 which is
almost the latest.  This was installed a month ago and has been
running
fine.

Suddenly, Monday afternoon, my TS3310 tape library could not be
contacted
by TSM.  Looking at windows device manager I see a warning icon and
"This
device cannot start (Code 10)" on the Media changer device. The
Changer

bus

enumerator cannot now see the media changer but the drives appear
to be
visible,

I've uninstalled/reinstalled the driver several times,  Specialists
have
been over the tape library and SAN with a fine tooth comb and can
find
nothing.  The box has rebooted multiple times.  Nothing works.

Has anyone seen this problem before, have any idea what causes it
or  how
it may be fixed?

Thanks

Steve

Steven Harris, who used to be an AIX admin before being sucked into
the
Redmond Vortex

--

Remco Post
r.post AT plcs DOT nl
+31 6 24821 622