johnsmith1
Contributor
Contributor

cant convert to smb share

hi,

I installed VMware vcenter converter 6.2.0 build 8466193 (latest one) which has in log history fix for smb share I had.

Conversion of a powered on Windows machine to an SMB share fails with the following error message: Unable to obtain the lock on virtual disks.

This issue is resolved in this release.

even that issue was fixed I have another issue which is thrown once I execute convertion ... with status FAILED: Insufficient permissions to access the source.

2018-11-09T15:32:38.150+01:00 info vmware-converter-server[17732] [Originator@6876 sub=Default] [task,379] [task-2] -- ERROR -- Convert: converter.fault.ImportSourceNoPermission

--> (converter.fault.ImportSourceNoPermission) {

-->    faultCause = (vmodl.MethodFault) null,

-->    source = "\\10.0.1.129\storage3-shared\vmware-x11-clone-20181109\x11\x11.vmx",

-->    msg = ""

--> }

why clone to SMB share is still broken? or do I miss something?

thanks

Tags (2)
26 Replies
POCEH
VMware Employee
VMware Employee

"Insufficient permission" should be self explanatory error, but probably you miss to give enough permission for share and/or, if target is NTFS, for folder's permission.

The easiest way is to add read/write permissions for everyone, otherwise you'll need to add read/write permissions for used user and for computer accessing share.

HTH

0 Kudos
johnsmith1
Contributor
Contributor

as I stated its snb mount and dir has perms fo everybody Full

now its diff error:

2018-11-09T18:16:52.079+01:00 info vmware-converter-server[14744] [Originator@6876 sub=Default] [task,379] [task-5] -- ERROR -- Convert: converter.fault.FileNotFound

--> (converter.fault.FileNotFound) {

-->    faultCause = (vmodl.MethodFault) null,

-->    file = "Z:\vmware-x11-clone-20181109\x1\x1.vmx",

-->    msg = ""

--> }

that software is like randomized Turing machine.

these dirs. and files were created there and then accidentally deleted and process exited with error no file ..ehm

0 Kudos
POCEH
VMware Employee
VMware Employee

This is because of using letter Z:! Only user making this share letter can see it, no one else can see it, including elevated (or non-elevated) one.

Simply use UNC notation.

HTH

0 Kudos
johnsmith1
Contributor
Contributor

hello there,

using unc notation ie \\10.0.1...\...

I got again insufficient permissions to access the source, even the target dir has Full access for everybody. I am desperate.

pastedImage_0.png

0 Kudos
POCEH
VMware Employee
VMware Employee

First check, via advanced, that rights are propagated to the subfolders and files.

Second check the NTFS permissions via cacls and eventually add new permissions.

The effective rights are combination of the above permissions.

If conversion still failed, upload log bundle - the problem could be somewhere else.

HTH

0 Kudos
johnsmith1
Contributor
Contributor

hi,

advanced is below

pastedImage_0.png

ntfs? its snb share...

please find attached log

0 Kudos
POCEH
VMware Employee
VMware Employee

Please attach worker's log.

0 Kudos
johnsmith1
Contributor
Contributor

whats worker log? or how can I get it?

pastedImage_0.png

0 Kudos
POCEH
VMware Employee
VMware Employee

Look inside diag.zip or find in folder "%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\logs"

0 Kudos
johnsmith1
Contributor
Contributor

that dir : C:\Users\ADMIN\AppData\Local\VMware\VMware vCenter Converter Standalone Client\Logs contains only

pastedImage_0.png

0 Kudos
POCEH
VMware Employee
VMware Employee

This is %LOCALAPPDATA%

Try "%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\logs"

0 Kudos
johnsmith1
Contributor
Contributor

thx, there are multiple errors..

but related to the smb share:::

2018-11-09T19:46:04.538+01:00 info vmware-converter-worker[14940] [Originator@6876 sub=Default] Stopped impersonating in session 5205e561-00bb-4c1b-1dcf-ea1e305bf210

2018-11-09T19:46:04.538+01:00 info vmware-converter-worker[14940] [Originator@6876 sub=Default] Session is closing, releasing cached session objects

2018-11-09T19:46:04.538+01:00 info vmware-converter-worker[14940] [Originator@6876 sub=Default] ConverterConnection: KeepAlive timer canceled, StopKeepAlive succeeded

2018-11-09T19:46:23.864+01:00 error vmware-converter-worker[13212] [Originator@6876 sub=task-3] No permissions to access \\10.0.1.129\storage3-shared\vmware-x11-clone-20181109\x1\x1.vmx. Error FileIO error: Permission denied for file  : \\10.0.1.129\storage3-shared\vmware-x11-clone-20181109\x1\x1.vmx.

2018-11-09T19:46:23.864+01:00 error vmware-converter-worker[13212] [Originator@6876 sub=task-3] TaskImpl has failed with MethodFault::Exception: converter.fault.ImportSourceNoPermission

2018-11-09T19:46:23.864+01:00 info vmware-converter-worker[13212] [Originator@6876 sub=task-3] TargetVmManagerImpl::DeleteVM

2018-11-09T19:46:24.613+01:00 info vmware-converter-worker[13212] [Originator@6876 sub=task-3] Virtual machine \\10.0.1.129\storage3-shared\vmware-x11-clone-20181109\x1 destroyed

0 Kudos
POCEH
VMware Employee
VMware Employee

Nothing suspicious from log about opening the VMX file. The error seems strange but exists.

Could be something specific with your share or how windows see that share. I've no idea which one is true and how to avoid it.

The simple workaround is to do conversion on locally attached USB disk.

HTH

0 Kudos
johnsmith1
Contributor
Contributor

agree with local drive...but I needed to do it on remote... so I have also no clue... might by issue with vconverter itself... im really desperate. simple task not working at all.

0 Kudos
POCEH
VMware Employee
VMware Employee

I understand your frustration, but all is about error ERROR_ACCESS_DENIED from CreateFile...
If I were you, I'll check the share - who can access to it, for example it is possible to access it from "local system" from source computer (it must part of 'everyone' access but who knows).

Good luck.

0 Kudos
johnsmith1
Contributor
Contributor

I cant use usb anymore, and the vconverter is not able produce any meaningful error.. its really frustrating and needles to say that software even years passed is crap. Also apparently no one from VMware is able to provide any help, seems they produce broken piece of software and they don't care about it at all.

0 Kudos
johnsmith1
Contributor
Contributor

also there is apparently no way how to submit officially issue to VMware. so they provide user forum and they absolutely ignore their products are broken..wonderful approach.

0 Kudos
Ultramation
Contributor
Contributor

Sorry i'm late to the thread, but i ran into this problem like you recently and i figured out a way to fix it.

Apparently all you need to do is using VMWare vcenter converter version 6.0 instead of version 6.2, and everything worked like a charm.

Dont know why maybe version 6.2 is broken, it can not even be installed on some machines that i tried.

boltzman
Contributor
Contributor

I struggled tonight with this SMB problem. All the shares are proper access. The log shows it stop when it tries to create directories. Obviously, the vCenter converter (Ran as administrator) is trying to be a different user than the allowed list.No permissions to access \\NAS\Public\DESKTOP-FFH0NPU\DESKTOP-FFH0NPU.vmx. Error FileIO error: Permission denied for file. This is where I clued in this must be a guest access level as that is denied. Once guest was enabled for the share, It worked like a charm

Maybe VMware wants to add to their software to use the current user privilege or ask for credentials for the shares... but the thing is, you can brows to the share just fine. I vote for a bug on this causing guest account being used. I log on to the NAS dashboard and see guest on SMB use.

0 Kudos