Failed to publish transfer package

[8Corners]

Hello,

I'm not able to publish any transfer package.

The viewserver works fine, but the publishing process stops at 3% with an error message "Failed to publish transfer package".

last log entry:

Error publishing transfer package: 5cad620d-96c8-4f9f-b0dc-19646cb92e76 com.vmware.vdi.transfer.imagerepository.PublishWorker.run(SourceFile:123)

com.vmware.vdi.transfer.commoncontrol.TransferServerException: Mvdi error occurred in framework queue:mvdi, hint:transferDiskForPublish. Mvdi error code:4

at com.vmware.vdi.transfer.commoncontrol.TransferServerException.fromFrameworkError(SourceFile:77)

at com.vmware.vdi.transfer.imagerepository.DiskBasedPublishWorker.b(SourceFile:492)

at com.vmware.vdi.transfer.imagerepository.PublishWorker.run(SourceFile:105)

at java.lang.Thread.run(Thread.java:619)

I searched Google, the VMware KBs, this forum, I do not find the solutions for this issue.

[amandasmith]

Hi,

Check the following information http://communities.vmware.com/message/1743836

Hope this information helps you.

[8Corners]

hi,

unfortunately that's not the same problem.

Port 902 is open and we don't use ipsec.

That's why i posted the log. It differs from the post you mentioned.

[8Corners]

No idea?

[itguybri]

Did you ever get this worked out?

Mine was working, but now I can't publish anything.

I only get an ace.dat file in the work forder for the image.

[itguybri]

Mine was working then broken.  I finally got it resolved.

I found an obsure note int he docs that if you 'recompose' your pool you will break it.  So I had to re-create my pool.

I then had to move the Transfer Server to the same cluster as the VMs were published on.

Watching what happens it looks like the Transfer Server VM needs direct LUN access to the datastore where the VMs are provisioned.

This was the last thing that fixed it for me.

So if oyu have multiple clusters or LUNs that are not shared you need multiple Transfer Servers.