VMware Cloud Community
MMRNOLA
Contributor
Contributor

V2V failing with "Permission to perfrom this action was denied"

I'm trying to V2V a Citrix server and am having issues. I've already done this several times here the past few days with the same exact setup so I know it's not an issue with the application itself.

I've gone through many threads regarding this issue and have tried all of the following:

VMware Vcenter Converter Standalone 5.5 build 1362012

Source VM; WIndows 2008 R2 Citrix (XenApp 6.5) server

*Using domain admin account for credentials

*Explicitly added to local admin group on source VM

*Disabled UAC

*Disabled firewall

*Disabled anti-virus

*attempted with local administrator account on source VM

* Started app with admin rights

None of this has gotten me past the error. Any help is greatly appreciated.

0 Kudos
4 Replies
POCEH
VMware Employee
VMware Employee

Please don't post logs, attach them, also seems you can't install the Converter Agent due to wrong credentials:

2014-04-23T20:49:04.815-05:00 [02404 info 'Default'] [AgentManager] Install Agent on LAFCTX205

2014-04-23T20:49:04.824-05:00 [02404 info 'Default'] [ufaUtilsWin32,210] Connecting to ADMIN$ on LAFCTX205 as LAFCTX205\admin-ww

2014-04-23T20:49:08.213-05:00 [02404 error 'Default'] [ufaUtilsWin32,223] File share connection failed - Authentication error

2014-04-23T20:49:08.242-05:00 [02404 error 'Default'] [AgentDeployment] Deployment on LAFCTX205 failed: converter.fault.IncorrectCredentialsFault

0 Kudos
MMRNOLA
Contributor
Contributor

The credentials used are domain admin credentials. Verified that they are part of the local admin group. I also tried using the local administrator account.

Any ideas?

0 Kudos
POCEH
VMware Employee
VMware Employee

The easy way for you is to install Converter Agent on source machine and try conversion again. HTH

0 Kudos
MMRNOLA
Contributor
Contributor

the agent actually was being installed even with the errors.

I removed this and then manually installed and still had the same error.

I then tried the newest converter with the same issue.

I rolled back to version 5.0 and was able to pull past the error. Not sure why an older version was required but I am good now.

thanks for the help though.

0 Kudos