This looks to me like you have a problem accessing the windows network share from the PXE client.
Try placing a pause in one of the steps before disk cleanup & breaking the pause with ctrl-c.
You will then have a DOS prompt.
try the following command:
net use q:
If this doesn't work, you will then have to troubleshoot the access issue with the network share.
I have also emailed this to you. I have duplicated the post here for the benefit of others who may have the same problem.
using the command you suggest i get this message:
Drive Q: exists locally
Do you want to continue ?
I think the solution to this is either to work out what is mapping to Q: and where, or edit blade.img to change the drive letter.
I'm not sure how to do either.
Oh - put the pause as early as possible, so it goes before a mapping in the system package
oh - just remembered: run the following before the net start command I gave you before!
net use q: /d
it will remove the existing mapping!
First off, I don't think the original error has anything to do with the drive mapping. You won't be able to use q: as a drive letter because that is the letter used by the ramdisk. If you want to test mapping a drive just use any other letter other than Q or A. As for the original problem, it seems like the vmware instance communication with the app server is not working properly. Are there any errors in the app server log at the time of provisioning?
As you supposed i have found error messages in the appserver.log.
These errors refers to communication with the client.
Is the workaround that to change the MTU of primary interface of server on which is installed the Application Server to 1300 ?