Re: [ADSM-L] Win64 2008: tsmutil164.dll and dsmntapi64.dll not found

* After you installed to the default location, where did dsmc.exe wind up?

* Try this:

1. Download to the VMware guest in question a fresh copy of the install
image from public.dhe.ibm.com
2. Uninstall the TSM client. Reboot if it tells you to.
3. Run the install package you just downloaded.

What are the results?

Best regards,

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 2011-01-31
11:30:54:

> From: Rick Adamson <RickAdamson AT WINN-DIXIE DOT COM>
> To: ADSM-L AT vm.marist DOT edu
> Date: 2011-01-31 11:31
> Subject: Re: Win64 2008: tsmutil164.dll and dsmntapi64.dll not found
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> FYI: Same results if I let the client install into the default
> directory.
>
>
> ~Rick
>
>
> -----Original Message-----
> From: Rick Adamson
> Sent: Monday, January 31, 2011 11:22 AM
> To: 'ADSM: Dist Stor Manager'
> Subject: RE: [ADSM-L] Win64 2008: tsmutil164.dll and dsmntapi64.dll not
> found
>
> Andy,
> My client install files are on another server using a Windows share. I
> log into the Win2008 (x64 SP2)virtual guest as a domain administrator
> and perform these steps:
> Start>Run> \\servername\clientfileshare
> Select English for the language
> The installer comes up, agree to the EULA
> Our clients are not installed in the default dir, instead they go to
> %systemdrive%/adsm (c:\adsm)
> The client install completes without noticeable issue.
> Go to the command prompt, right click and select "run as administrator"
> Change to the baclient dir and attempt to run:
>    Dsmcutil inst /name:'Service Name' /node:nodename /pass:password
> /auto:y
>
> This is when I get the error described below which led me to
> investigate. Results; the registry is looking for the tsmutil164.dll in
> the system32 directory but it is actually in the sysWOW64 directory.
> Same issue when trying to open the TSM-GUI but the file name is
> dsmntapi64.dll in that instance.
>
> Thus far I have found nothing in any of the usual TSM log files and know
> that we are using this client version on other 2008 servers.
>
> The VMware admin claims there are no policies, etc. that are applied by
> him, or modifications to the template that he is using to stand up these
> virtual guests.
>
> Appreciate your feedback.
>
> ~Rick
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Andrew Raibeck
> Sent: Monday, January 31, 2011 9:29 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Win64 2008: tsmutil164.dll and dsmntapi64.dll not
> found
>
> Rick,
>
> Did the TSM executables (dsmc.exe, dsmcutil.exe, etc.) install to
> "C:\Program Files"? Or did they wind up in the "C:\Program Files (x86)"
> directory? Or did you choose a different install location?
>
> Because this is a 64-bit program, the DLLs should have gone to
> C:\Windows
> \system32.
>
> I tried this on a VMware install of Windows 2008 Server, x64 SP2. Even
> when
> I used the command prompt in 32-bit mode (C:\Windows\SysWOW64\cmd.exe),
> running the installer yielded the files in all the right places.
>
> I have no idea how this could have happened, but I would have to think
> it
> is somehow unique to how the install was performed. It would be helpful
> if
> you would provide a finely detailed, blow-by-blow description of how you
> performed the TSM client install, starting with, "I logged on as a local
> administrator", and providing all the detail like, "then I right-clicked
> on
> the Start button, chose "Open Windows Explorer" or "I pressed
> <WINDOWS>-R
> to bring up the Run dialog and typed xxxxx", and so on and so forth. For
> this issue, the details may be critical to running down how this
> happened.
>
> Best regards,
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Product Development
> Level 3 Team Lead
> Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS
> Internet e-mail: storman AT us.ibm DOT com
>
> IBM Tivoli Storage Manager support web page:
> http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_
> Storage_Manager
>
> "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 2011-01-28
> 11:21:13:
>
> > From: Rick Adamson <RickAdamson AT WINN-DIXIE DOT COM>
> > To: ADSM-L AT vm.marist DOT edu
> > Date: 2011-01-28 11:23
> > Subject: Win64 2008: tsmutil164.dll and dsmntapi64.dll not found
> > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
> >
> > Details: Windows 2008 64bit SP2, client versions 5.5.2.12 and 5.5.3.1
> > (both x64).
> >
> >
> >
> > This is a new VM guest and after installing the 5.5.2.12 client which
> > went fine,  attempting to install the scheduler service I get the
> > following error:
> >
> >
> >
> > "This application has failed to start because TSMUTIL164.dll was not
> > found. Reinstalling the application may fix this problem."
> >
> >
> >
> > A reinstall did not help so I tried a newer client (version 5.5.3.1),
> > same issue. Searching found no reference at IBM and Google showed one
> > hit (in this forum with no solution).
> >
> >
> >
> > I then tried to open the GUI and received the same error message
> > referencing the dsmntapi64.dll
> >
> >
> >
> > The application event log has an error:
> >
> > "Faulting application dsmcutil.exe, version 5.5.3.1, time stamp
> > 0x4ca9895e, faulting module TSMUTIL164.dll, version 6.0.6002.18005,
> time
> > stamp 0x49e0421d, exception code 0xc0000135, fault offset
> > 0x00000000000b8fb8, process id 0x6c0, application start time
> > 0x01cbbf053c1d2efb."
> >
> >
> >
> >
> >
> > Searching the registry reveals that it is looking for the files in the
> > system32 folder and I actually found them in the sysWOW64 folder.
> >
> >
> >
> > Copying them over to the system32 folder does at least let me open the
> > GUI but did not give a warm & fuzzy, so I thought I would ask has
> anyone
> > else seen this issue. If so, were you able to determine the cause?
> >
> >
> >
> > I know it would be preferred to move to a 6.2.x.x client but our
> servers
> > are currently at level 5.4.5.2 which is a support issue.
> >
> >
> >
> > Thank in advance for any feedback you can provide.
> >
> >
> >
> > Rick Adamson
> >
> > Jacksonville, FL
> >
> >