ADSM-L

Re: [ADSM-L] TDP for Virtual Environments - Self Contained application MS Exchange

2014-05-02 12:47:02
Subject: Re: [ADSM-L] TDP for Virtual Environments - Self Contained application MS Exchange
From: Del Hoobler <hoobler AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 2 May 2014 12:44:02 -0400
Hi Harry,

This looks like a bug that was fixed. It is fixed in the 7.1 client
package.

If you do not want to upgrade to 7.1, it will be fixed in the
6.4.2 PTF coming out this summer.


Del

----------------------------------------------------


"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 05/02/2014
04:41:04 AM:

> From: Harry Redl <harry_redl AT YAHOO DOT COM>
> To: ADSM-L AT vm.marist DOT edu,
> Date: 05/02/2014 04:41 AM
> Subject: Re: TDP for Virtual Environments - Self Contained
> application MS Exchange
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> Hello,
>
> so I have run the trace and this is the error I see
>
> 05/02/2014 10:01:34.830 : ..\..\common\vm\wsops.cpp( 442):
> WsGuestOperations::CopyFileTo(): Command
>  >C:\PROGRA~1\Tivoli\TSM\baclient\\jvm70001\jre\bin\javaw.exe -jar
> "C:\Program Files\Tivoli\TSM\baclient\\httpagent.jar" TO "C:\Program
> Files\Tivoli\TSM\baclient\\vmtsmvss\BackupMon.exe"
> "https://<secret_ip>:443/guestFile?id=12&token=52ad163b-6447-81c9-
> d40b-e4e6232fdbed12"<
> failed, output:
> HttpAgent.uploadData():
>                          urlString =
> https://<secret_ip>:443/guestFile?id=12&token=52ad163b-6447-81c9-
> d40b-e4e6232fdbed12
>                          fileName  = C:\Program
> Files\Tivoli\TSM\baclient\\vmtsmvss\BackupMon.exe
>                          fileSize  = 258560
> ERROR: failed to upload file: C:\Program
> Files\Tivoli\TSM\baclient\\vmtsmvss\BackupMon.exe to
> https://<secret_ip>:443/guestFile?id=12&token=52ad163b-6447-81c9-
> d40b-e4e6232fdbed12
> javax.net.ssl.SSLHandshakeException: Remote host closed connection
> during handshake
>
> So it seems the ESX itself does not accept the file transfer. So far I
> know the problem is not the firewall as the port is open and I can
> connect to the https page of the ESX via browser.
> Looking at the ESX side now.
>
> Harry