Solved: No available servers for this transfer

Eternal_Snow · ‎11-01-2010

Hello everyone.

I'm testing VMware View 4.5 with Local Mode.

Environment:

VCenter 2.5 and View Composer 2.5 are installed on a same server.

Connection Server 4.5 is installed on a Windows 2008 R2 (x64) server. Transfer repository sharing is opened on this server.

Transfer Server 4.5 is installed on another Windows 2008 R2 (x64) server.

Guest: XP SP3

VMView with agent: XP XP3

All servers are in the same domain. Network is good.

Any client in this network can access VMware View desktop as remote session without any problem.

When I try to check-out. I get this error at 88%:

Local Mode Operation StartTransfer failed for Desktop xxx, ID: xxx. Error message: failed to start the disk transfer: com.vmware.vdi.desktoptracker.MVDIOperationControl$MVDIOperationException: No available servers for this transfer. Please try again later, or contact your system administrator.

What's the problem?

Thanks.

jbrazio · ‎11-10-2010

Well.. somewhere near the 88% the transfer server VM needs to mount the user disk so datastore access is required from the host running the Transfer Server VM; when I look at the log files you've posted I see "No ready transfer servers have access to the storage for VM" and this really makes me thing that the user disk datastore is not seen by the host running the Transfer Server.

Can you try to logon into vCenter with the user defined on the Connection Server and try to manually hot add a user disk to the Transfer Server ?

-

If you find this post helpful please don't forget to award points to it.

----- If you find this post helpful please don't forget to award points to it.

View solution in original post

Eternal_Snow · ‎11-03-2010

I've tried to reinstall transfer server system to Windows Server 2003 x86 R2 (SP2) and moved the transfer repository from connection server to transfer server. The error is still the same.

Do I need more than 1 transfer server? I have only one desktop to be checked out.

Lazlo · ‎11-03-2010

Just to verify a couple things:

The transfer fails at 88% or 8%? at 88% the transfer should be almost complete, at 8%, the transfer should be about to start.
What kind of pool are you trying to check out? Manual? Linked clone? Full clone?
What's the status of the transfer server? Is it in the 'Ready' state?

Can the client ping the transfer server? The client being able to connect to the desktop remotely isn't an indication that it will be able to check out the desktop based on the network configuration (the transfer server has nothing to do with remote connections).

-Lazlo...

Lazlo · ‎11-03-2010

One other note: I wouldn't recommend having the Transfer Server Repository on the same system as the Connection Broker. The purpose of the Transfer Server was to offload the burden of Local Mode Desktop transfers from the connection broker (like it was when Offline Desktop was just experimental from 4.0 and earlier).

Also, unless you're dealing with linked clone desktops, you technically don't need the transfer server repository setup. It's still recommended that you set one up in case you'll create a linked clone pool down the road.

-Lazlo...

Eternal_Snow · ‎11-03-2010

Thanks for you reply.

1 The transfer fails at 88% often, at 10% sometime.

2 Pool: Automatic Pool - Linked Clone.

3 Transfer server is ready and image is published.

4 From the client, I can ping to all servers: vcenter, connection server, transfer server and domain controller. And, I tested to visit the network sharing directly from client with no error. Also, I use my browser from client to visit the transfer server, "It works!" returned.

Eternal_Snow · ‎11-08-2010

I found that the status when error message box raised:

Checking out: Releasing disk

Lazlo · ‎11-08-2010

ok, does it sit there a long time before it finally times out? There could be an issue on the transfer server side. It sounds like it's at the state where the TS is unmounting the disk. There should be something more specific in one of the log files.

Check the client's log files for any additional information at the time of the disconnection.

If there's nothing there. Note the time it happened and check the transfer server's log.

This isn't something I've run across, I'm not sure what could keep the TS from releasing the disk. If it has enough permission to mount it, it should have enough permission to unmount it (one would think).

-Lazlo...

Eternal_Snow · ‎11-08-2010

I guess it's not about timed out. The error occurred no more than 1 sec after the percentage number changed.

The server log i've posted in this thread.

Client Logs:

09:32:41,900 ERROR <1940> VMHSLaunchVM failed: There is no VMware process running for config file D:\VM\Dev\Visual Studio 2008 With Oracle Client\CN=VS2008Oracle,OU=Applications,DC=vdi,DC=vmware,DC=int.vmx

Either run "C:\Program Files\VMware\VMware View\Client\Local Mode\x64\vmware-vmx.exe D:\VM\Dev\Visual Studio 2008 With Oracle Client\CN=VS2008Oracle,OU=Applications,DC=vdi,DC=vmware,DC=int.vmx" manually on the server,

or register the config file.

09:37:21,914 ERROR start-disk-transfer (start-disk-transfer) response xml ERROR = failed to start the disk transfer: com.vmware.vdi.desktoptracker.MVDIOperationControl$MVDIOperationException: No available servers for this transfer. Please try again later, or contact your system administrator.

09:37:21,919 ERROR OnOVDICompletion: operation failed: No available servers for this transfer. Please try again later, or contact your system administrator.

I guess the "Releasing" is the last text for the job its finished. May be the problem is it cannot start the next job.

Eternal_Snow · ‎11-08-2010

I found that all files in Published folder of Repository has been downloaded to local except a file with ".transfer" before the error occurred.

I think there may be some error while client gets the different data between this vm and the published image.

From this local computer, I can ping to all esx servers and vcenter.

Lazlo · ‎11-08-2010

Since it says there are no available transfer servers, I'd say the the next step is to look at the transfer server log files and the Broker log files. I'm interested to see what the transfer server thinks is going on at this point. I have a feeling the answer lies there.

-Laz...

Eternal_Snow · ‎11-08-2010

I read though the logs from transfer server and not found any problem.

Lots of publishing, removing and http get. No error.

I guess there may be no error on transfer server. coz it supplied all files it contains.

It may be something wrong on connection server that the client cannot get the increasing data based on the snapshot published.

Eternal_Snow · ‎11-08-2010

I found something interesting in connection server log:

15:44:12,758 INFO <Thread-33> (Request31) User Allen connected to the Secure Gateway Server - session ID: 73FA6A03B1DF600FDFB04060E71943BE

15:44:25,660 ERROR <TP-Processor8> (SESSION:E73D23D677398BB018AF01FB65448177;73FA6A03B1DF600FDFB04060E71943BE) No transfer server available for transferring VM: /NTI56/vm/Personal/VMwareView/Deployment/VS2008Oracle/VS2008Ora-3

15:44:25,660 ERROR <TP-Processor8> (SESSION:E73D23D677398BB018AF01FB65448177;73FA6A03B1DF600FDFB04060E71943BE) Reason: No ready transfer servers have access to the storage for VM moid: vm-2691 , disk key:3000

15:44:25,662 ERROR <TP-Processor8> (SESSION:E73D23D677398BB018AF01FB65448177;73FA6A03B1DF600FDFB04060E71943BE) Hot add disk failure for user: Allen desktopDn:CN=VS2008Oracle,OU=Applications,DC=vdi,DC=vmware,DC=int com.vmware.vdi.broker.DesktopsHandler.a(SourceFile:3120)

com.vmware.vdi.desktoptracker.MVDIOperationControl$MVDIOperationException: No available servers for this transfer. Please try again later, or contact your system administrator.

at com.vmware.vdi.desktopcontroller.VirtualCenterDriver.a(SourceFile:5726)

at com.vmware.vdi.desktopcontroller.PoolManager.mapVmDiskForTransfer(SourceFile:603)

at com.vmware.vdi.broker.DesktopsHandler.a(SourceFile:3071)

at com.vmware.vdi.broker.xml.ProcessorStartDiskTransfer.a(SourceFile:162)

at com.vmware.vdi.broker.xml.AbstractProcessor.b(SourceFile:82)

at com.vmware.vdi.broker.servlets.XmlServlet.doPost(SourceFile:71)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:647)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)