This Question is Possibly Answered
1 "correct" answer available (10 pts) 1 "helpful" answer available (6 pts)
10 Replies
Last post:
Sep 5, 2008 3:24 PM by
etung
Well, I still have the issue with one VM. 2.0 shows the lock and isn't capable to take ownership…
I opened the VM on the server from my Mac via afp and usign Fusion 1.x, which cleared the lock on the 2nd vm.
let me attache the file, then.
Michael
I opened the VM on the server from my Mac via afp and usign Fusion 1.x, which cleared the lock on the 2nd vm.
let me attache the file, then.
Michael
Attachments:
-
Picture 1.png (248.7 K)
Hi etung
Yes, your recap is to the point!
The issue then is: Fusion 2.0b1 cannot delete the .lck folder and it's contained files (in my case there was one of them).
Workaround:
delete the files manually. I did and I can't show/reproduce the situation anymore; but I am sure, that VMWare team is able to, if they want
Michael
P.S.
I had another workaround before that and just wanted to draw your attention to the issue.
Yes, your recap is to the point!
The issue then is: Fusion 2.0b1 cannot delete the .lck folder and it's contained files (in my case there was one of them).
Workaround:
delete the files manually. I did and I can't show/reproduce the situation anymore; but I am sure, that VMWare team is able to, if they want
Michael
P.S.
I had another workaround before that and just wanted to draw your attention to the issue.
