We help IT Professionals succeed at work.

Plug in fails to connect to VMware Data Recovery service

funasset asked
Last Modified: 2012-06-16
I recently replaced my workstation and moved from XP to Windows 7 Pro x64 (OEM licence). I have installed the same copy of the vSphere client as I was using previously and the same copy of the Data Recovery plug-in.  My old PC is still alive and i've checked all the version numbers in the Manage Plug-ins menu and they are identical.

For some reason I now cannot connect to the Data Recovery Appliance from my new PC.  I've tried it on another similar PC and it works and it still works on my old PC. My firewall is off and I can ping the target OK.  When I try to connect in vSphere it reports "Could not connect to the data recovery service on the appliance. If the problem persists restart or redeploy the appliance".  If I try to connect using the IP address I get the same error but the IP address is immediately resolved to the appliance name so i guess there's communication somewhere!

VMware support want me to re-install Windows but as I've just got the new PC as I like it with everything installed I don't really want to do that.  I renamed a couple of DLLs they asked me to and that didn't work - neither did bouncing the appliance or trying to attach when logged in to my PC under a different profile.

Can anyone help?
Watch Question

Andrew Hancock (VMware vExpert PRO / EE Fellow)VMware and Virtualization Consultant
Expert of the Year 2017



If the Control Panel is to be believed then all firewalls are Off.


I am at a loss - this is doing my head in!!

I did a 'complete' uninstall and got the most recent software I could find on the VMware site.  I installed that and still no joy.  I say 'complete' because when I fired it up vSphere client somehow knew the last screen I looked at using the version I removed.  Perhaps the uninstall isn't very clean? Yet another straw clutched.
Andrew Hancock (VMware vExpert PRO / EE Fellow)VMware and Virtualization Consultant
Expert of the Year 2017

is this only this client which is affected?

have you checked the plugin is enabled on the client?

Is your firewall service actually disabled??


It seems to be the only PC affected. I installed the same software on a test PC which is Windows 7 Ultimate (not Professional like mine) and not in our AD domain and it worked first time. By 'enabled' do you mean listed in the vSphere Client?

The firewall service was indeed started but I got the same result after stopping it though. I never realised the service stayed alive after setting the firewall to Off!! You'd think Windows would take the hint and stop the damned thing.

Have you checked the VMWare logs on the client?
It's in C:\user\%username%\AppData\Local\VMware\vpx\ folder.

Also check the cache.xml in C:\user\%username%\AppData\Local\VMware\vpx\PluginCache
It should look like this:

    <FileName>C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Plugins\Data Recovery\Data Recovery.dll</FileName>
    <AsseblyName>Data Recovery, Version=, Culture=neutral, PublicKeyToken=null</AsseblyName>

Open in new window


Thanks for that.  The cache.xml entries look identical albeit there is a lot of other gubbins in that file - I presume that isn't important which is why you didn't mention it?

I'm afraid I don't know what I'm looking for in the logs as this is all new to me.  There are currently 8 in total - are they just created when the vSphere Client is started or does it write entries in there when I do certain things like trying to connect to the Data Recovery appliance?

I would have posted the latest or all of them for someone to look at but I don't want to make them available to all in case this poses a security risk.

I've deleted the DLL again - the one that VMware support asked me to - as  I did a re-install last night but it crops up in several places and I'm not sure which is the correct one. Support told me it would be in ...windows\system32 but there isn't one on this Win7 PC - they are all in c:\program files (x86) subdirectories.  Still no joy. I recall that I had some kind of problem with this on XP and had to delete the same DLL but in that case it got rid of the problem! I got a colleague who runs the same OS on his laptop to try and connect and he was successful. To recap, if I try and login using the appliance's IP address it immediately resolves to the actual name. If it does that then I presume the client and device are talking and it can't be a port problem?

It's a really strange one
This one is on us!
(Get your first solution completely free - no credit card required)


VMware support didn't have a clue and they said that my idea of running it in Windows' XP mode was "probably the best thing to do".

Gain unlimited access to on-demand training courses with an Experts Exchange subscription.

Get Access
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Empower Your Career
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.