virtualbox.org

Host: 2003 server
What I have is a external drive setup on Server 2008 being shared
I setup virtualbox on 2003 server and successfully setup 2003 server as guest as well over the network share
After getting the guest to a reasonable fresh install state with update I decided to clone it using vboxmanager using the longest command line ever I think.. and it completed fine over the network. It cloned the vdi file over the network to another vdi file in exactly the same place just different file name.
I then attempt to create a new guest and use the cloned vdi file and at final step when I click finish get a verr_access_denied message. Failed to create a directory.
I go on the share, navigate to the reported spot that virtualbox is reporting access denied message on to create directory and remotely create directories fine. Virtualbox did not have any issues creating directories on initial install.
I should also mention the initial install took place on a fat32 share which has been recently converted to ntfs
On 2008 server there is no logs indicating any failed events
I double checked the share permissions and security settings but found no issues.
Any help would be great

All I can say is that I have the same issue on my Linux Host. Creating a new VM ends up barfing that same error. It seems that in 2.2.2, you can't create a new VM.

I thought I had the same issue, but it seemed I had an error in my VirtualBox.xml file, where it had a non-existing path in the defaultMachineFolder property. After fixing that, it was OK again.

Your problem might be the point of it being on a share.

Alright, I looked through XML file for the original and nothing found there that might be bad.
XML's for other machines not created yet of course
I went ahead and created the folder it was trying to create to see what it would do then.. Seems to have created the machine fine and added files into that directory fine
Started the VM and got same error only this time with the log file.
Noticed Log directory not created so made that
started VM again and no complaints. Started right up.

Was going to take this path earlier but figured since its not exactly fixing the issue it may be back to bite me. And thought maybe I did something wrong.

I do have 2008 server to accept connections only from my users (not everyone or other generic users) so not sure if this is causing a problem but then again VirtualBox seems to have no problems creating and modifying files. just directory creation is a issue.

Best thing to try your idea, is to allow everyone read and write in the share, then create a new test VM to see if that's the problem. If it is, you can check the logs on your server for any authentication failures it had before changing the share permissions. It's possible VB runs something as a different user, not accepted by your strict permissions.