VDP 6.1 can´t connect to vdp appliance inside vsphere web client

[chrsun02]

Hi,

I have depolyed VDP 6.1 and have it up and running. now im trying to connect to the appliance frpm vsphere Web client. After pressing connect the screen goes grey and nothing happens.

No error message no time out, just grayed out with timeglas not moving.

DNS is ok

account for vdp in vcenter ok

all services for appliance are ok

vcenter 5.5 ESXI 5.5

Regards

mgd

[agolota]

Hi,

I have  the same issue with VDP 6.1 and vCenter 6.0.0.

I've opened support request.

Regards

Adam

[TimR26]

Any response from VMware Support?

[magi]

No. They have all logfiles now and they are investigating the problem. But I'm in contact with them.

[agolota]

No response from support since 07.04. They also have my logifles.

[pascalsaul]

Yes, busy with them now...

Check out: virtuallyPeculiar: VDP 6.1.2 Plugin Not Available After A Fresh Deployment‌

In my case after removing the plugins and restarting the webclient without the VDP2 plug-in I see after rebooting an appliance that a directory is created. But the directory is named: C:\ProgramData\VMware\vSphere Web Client\vc-packages\vsphere-client-serenity\com.vmware.vdp2-6.1.0.19

In the directory the right 6.1.2.war is there :smileysad: (<pluginPackage id="com.vmware.vdp2" version="6.1.2" name="VDP 6.1" description="vSphere Client VDP plugin" vendor="VMware">)

So the correct plug-in is loaded in the webclient but still hanging...

[SavkoorSuhas]

I currently have a case with me where 6.1.2 vdp grays out after the connect. My colleague has the same with 6.1.1

validate the following:

1. Port connectivity verification

VMware KB: Required ports for VMware vSphere Data Protection 5.x

2. Name resolution for vdp

3. Restart tomcat service

emwebapp.sh --restart

4. Verify time sync and restart VMware tools on vdp

service vmware-tools restart

5. Re register to vCenter

If all these steps are implemented and still the connect fails with the hung gray screen, then you are in the same place as I am..still working on it

Suhas

[pascalsaul]

Yes, been there done that :/ I think these cases need to be escalated to engineering... Because back-ups ain't running also...

My case: 16959042704

[SavkoorSuhas]

Little more info after testing:

1. I migrated my VDP network to vDS and it stays grayed out on connect in web client

2. Migrated the VDP networking to standard switch and it connected immediately.

Are we running distributed switches?

Suhas

[pascalsaul]

Correct, after switching to VSS I can connect to the appliance again...

During the upgrade to 6.2.1 I lost my back-upjob with attach existing disks method.

Now trying to create a new job for tonight...takes long for submitting the job? Still waiting or I'm not patient enough.

Well a little step further now... Now is the questing what is causing this behaviour :smileyhappy:

[SavkoorSuhas]

Backup job creation should be quick.

What is causing the behavior? That's a good question. Unfortunately I do not have the answer right away, let me dig in more into this.

Suhas

[RyanJMN]

I recently ran into this issue with VDP webclient not loading at a customer of mine.  vCenter and PSC recently was updated to 6.0 U1.  I believe its a vCenter or PSC permission issue and not specifically a VDP issue.

We looked at the webclient vergo logs at the time attempting to open the VDP webclient.  Looks like the web client has an issue with com.vmware.vim.binding.vim.dvs.PortConnection which has to do with distributed switches.

[2016-04-06T17:50:42.280-05:00] [INFO ] http-bio-9443-exec-14 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint vdp-amf received request.

[2016-04-06T17:50:42.367-05:00] [INFO ] http-bio-9443-exec-14         org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint vdp-amf received request.

[2016-04-06T17:50:42.382-05:00] [ERROR] http-bio-9443-exec-14 Endpoint.AMF Cannot create class of type 'com.vmware.vim.binding.vim.dvs.PortConnection'.

1. flex.messaging.MessageException: Cannot create class of type 'com.vmware.vim.binding.vim.dvs.PortConnection'. Type 'com.vmware.vim.binding.vim.dvs.PortConnection' not found.

at flex.messaging.util.ClassUtil.createClass(ClassUtil.java:70)

Moving VDP from distributed switches to standard switches did get it to work and the errors disappeared in the vergo log.  vCenter can still be connected to a distributed switch.  Backup jobs continued to work when the webclient would not load.

It looks similar to this KB https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2125229  which is why I'm thinking its a vCenter or PSC permissions issue due to the upgrade.  At this point we will probably wait for VMWare support to resolve the issue because for us moving VDP to a standard switch is an alright work around.

We also have an odd behavior with some of the roles displaying differently.  For example there is a role called "inventorhyservice.tagging.taggingadmin" instead of "Tagging Admin".  Might be related.

[SavkoorSuhas]

Informative. Let me get the analysis going and I can try correlating to what we are seeing in your virgo logging.

Suhas

[pascalsaul]

I can do everything with the VDP on the VSS except creating a simple back-upjob with 1 VM :/

Showing the logs/reports, running a manual integrity check and deleting a restore point is not a problem. Rebooted the appliance twice allready.

Annoying...

Are there any logs for these actions? And where are they located on the VCS?

[SavkoorSuhas]

Yes.

vdr-server.log has these information.

Location: /usr/local/avamar/var/vdr/server_logs

It's going to look something like this for a successful create:

2016-04-15 18:55:47,371 INFO  [http-nio-8543-exec-10]-rest.BackupService: Create backup job qwerty

2016-04-15 18:55:47,387 INFO  [http-nio-8543-exec-10]-services.BackupJobManagementServiceWS: VCenterClient fqname="/192.168.1.1/192.168.1.1" name="192.168.1.1" cid="d03a58d99b282b9c7c6cb9c6367ff23394f0f014" os="N/A" ver="Unknown" init-time="2016-04-04 00:00:00.0 (1459708200000)" last-contact-time="2016-04-07 00:00:00.0 (1459967400000)" plugins=[] vcenter-port=443 vcenter-user="vsphere.local\Suhas"

2016-04-15 18:55:47,469 INFO  [http-nio-8543-exec-10]-job.JobServiceImpl: Setting the window start time: Fri Apr 15 20:00:08 IST 2016

2016-04-15 18:55:51,102 INFO  [http-nio-8543-exec-10]-ddr.DdrDatasetServiceImpl: Successfully Set DDR DatasetOptions (enabled=false, index=0) On Dataset "qwerty"

2016-04-15 18:55:51,102 INFO  [http-nio-8543-exec-10]-job.JobServiceImpl: Created Backup Dataset "qwerty"

2016-04-15 18:55:51,184 INFO  [http-nio-8543-exec-10]-services.BackupJobManagementServiceWS: Client  name=CentOS7 uuid=5039665b-4899-9c00-1695-e42ff9d4eda2 vcc=VCenterClient fqname="/192.168.1.1/192.168.1.1" name="192.168.1.1" cid="d03a58d99b282b9c7c6cb9c6367ff23394f0f014" os="N/A" ver="Unknown" init-time="2016-04-04 00:00:00.0" last-contact-time="2016-04-07 00:00:00.0" plugins=[] vcenter-port=443 vcenter-user="vsphere.local\Suhas" vmpath=[Protected_LUN] CentOS7/CentOS7.vmx guestid=centos64Guest guestfullname=CentOS 4/5/6/7 (64-bit)

2016-04-15 18:55:51,587 INFO  [http-nio-8543-exec-10]-services.BackupJobManagementServiceWS: Schedule: 0

is your backup create failing? If so does it display any error in GUI?

And what does vdr_server log state?

Suhas

[pascalsaul]

Ah ok Suhas! Lohit just called me and also told me the protected clients need to be on the VSS to be able to create a back-up job. That's is working for me also but in our situation not doable :smileyhappy:

I need to downgrade to the previous version now and wait for the bugfix. It's now at the EMC/VMWare engineering teams he said.

[SavkoorSuhas]

Yes, just got the same validated in my lab and well as with the Open ticket with me.

Yes the following are seen in the virgo.log during the VDP connect when on vDS

[2016-04-15T14:08:15.093Z] [ERROR] http-bio-9090-exec-10         Endpoint.AMF                                                      Cannot create class of type 'com.vmware.vim.binding.vim.dvs.PortConnection'.

flex.messaging.MessageException: Cannot create class of type 'com.vmware.vim.binding.vim.dvs.PortConnection'. Type 'com.vmware.vim.binding.vim.dvs.PortConnection' not found.

        at flex.messaging.util.ClassUtil.createClass(ClassUtil.java:70)

        at flex.messaging.io.AbstractProxy.getClassFromClassName(AbstractProxy.java:87)

I also ran into issues creating backup job when VM is on vSS as well (Just for one VM)

The error: <backuperror>

And when I click "Show sources" in backup tab, it shows the ESXi host where the VM resides.

Unfortunately, no more workaround are available at the moment.

Suhas

[jo_strasser]

Hi,

same here.

I can reproduce this issue.

VDP access through Web Client and Backup Job creation only will work if the VDP appliance and the VMs to backup are on a standard vswitch.

I will escalate this bug also to VMware.

Following versions are affected for me right now: VDP 6.1.1 and VDP 6.1.2.

Thanks JO

[pascalsaul]

6.1.1.19 is working without a problem on a VDS here...

[jo_strasser]

Which version of DVS are you using? 6.0?

Have you fresh deployed the appliance or done a downgrade?

Greets JO

[pascalsaul]

I'm using 5.5...

I did a downgrade and a new deployment...

[santhoshbiradar]

In my testbed, I have the same problem of VDP appliance not getting connected in web client!

I have performed all 5 steps mentioned. But still the grey transparent screen is being displayed!!

[chrsun02]

Update

im running 6.0 for VC and ESXi in this Environment :smileyhappy:

/Chrsun02

[CMSA]

Hi,

same here. I wanted to give VDP a test in my VCSA 6 Update 2 (just updated from Update 1 a few hours ago) environment and maybe use it as a replacement for our current vmware backup solution. I Downloaded the current VDP ova from VMWare Downloads (v6.1.2) and followed the install guide - all went well - up until I tried to click on the "connect" button in the vCenter Web Client VDP plug-in.

And yes, I have double checked DNS - forward and reverse.

Its not the known bug that the plug-in does not even show up in the Web Client. I see the plug-in and can basically start it. I just cannot connect to my VDP instance when asked to. The screen grays out (changing the cursor to the famous "please wait" clock) as soon as I click on the "connect" button and nothing happens. ever. I even uninstalled and unregistered the VDP installation (via https://MyvCenter/mob), reinstalled the whole VDP appliance. Same result.

Any news on this?

[chrsun02]

Hi

Same story here, i have reinstalled and unregistered the VDP installation. Connect = grayed out!

/Chrsun02

[MXP1L0T]

I'm in the same boat here with vCSA 6.0 U2 and VDP 6.1.2.  The screen in the web client turns grey and there is no error message or timeout.

[magi]

Hi everyone,

same problem here. U2 with VDP 6.1.2.

Also opened a request ticket 3 days ago.

Do you use a Standard Switch or a distributed Switch? When I connect VDP to a Standard Switch it worked. But when I add a VM on a distributed Switch to a backup Job it hangs

When I reconnect it to qa distributed Switch same Problem as you.

Greetings

Martin

[agolota]

Hi,

We are using distributed switch. When we changed to standard it worked.

Thanks!

But still waiting for support.

EDIT:

@mglich

As I wrote I connect with standard switch, but it's immposible to add new backup job - system hangs.

[MXP1L0T]

Yes we use a distributed switch also.  I was wondering about this.  The port group that I'm using for the vCenter and the VDP appliance is in ephemeral mode.  I changed to vCenter and VDP to a port group with static binding but there was no difference.  I'll see if I can try the standard switch.

[cans]

Are the vCenter and the vApp in the same subnet ?

We got same problem here (deployment is okay but we cannot connect to the vapp thru vsphere web client) and vmware support respond to us that VDP doesn't support routing between VDP and vCenter (?!).

We use dvs too with all component un 6.0U2 (vcenter/esxi) and VDP in 6.1.2 version.

[magi]

Yes, same subnet between vCenter and VDP. ESXi is on a different subnet.

[MXP1L0T]

In my case all vCenter, VDP and ESXi in same subnet. As soon as you go to vCenter 6.0 U2 the only supported version of VDP is 6.1.2.  Backups would be great to have.

[MXP1L0T]

I tried installing VDP 6.1.1 but ended up with the same issues.  I think that the issue is vCenter (VCSA) 6.0 U2.  If there are no patches for it I might be forced to try to VCSA 6.0 U1 that was working fine before.

[pascalsaul]

This is also the case with vCenter 5.5 U3 :/

[brtvd]

me too have the same problem connecting VDP 6.x through web-client, see image

[chadc1979]

I am experiencing the exact same issue, figured I'd poke around here before submitting a ticket.

I'm on vCenter 6.0 U2/ESXi 6.0 U2 and VDP 6.1.2, all VMs use 9.10.5 VMware Tools on HW Profile 11

If I switch to a Standard Switch things work but on a Distributed Switch the Web Client hangs on connecting, I have found I can create backup jobs against a vSAN datastore but not against a shared storage array. Not sure if local storage works!

Glad to see I'm not alone.

[cans]

Feedback from VMware support: VDP 6.1.x doesn't work with Virtual Distributed Switch !

They were able to reproduce the bug.

Next step is to open a ticket to EMC support (since VDP is a EMC solution just rebranded by VMware) , but this might take time ... :smileysad:

Perhaps if all of you guys open SR regarding this problem it will reduce the resolution time ?

Workaround is to use Standard vswitch but in my case this is very complicated since we have a full dvswitch environment (due to LACP usage).

[Evato]

Interesting scenario here...

vSphere 5.5 U2 with ESXi 5.5 U2 with vDS 5.1 and VDP 6.1.1 working fine

vSphere 5.5 U2 with ESXi 5.5 U2 with vDS 5.5 neither VDP 6.1.1 or 6.1.2 will connect via web client

Has anyone else reporting issues tried with a vDS 5.1 ?

[jo_strasser]

I´ve tested vSphere 6.0U2 with VDP 6.1.2 on VDS 6.0 -- isn´t working

vSphere 6.0U2 with VDP 6.1.1 on VDS 6.0 - isn´t working

Looks like a dependence to newer versions of vDS (5.5 or newer)

Greets JO

[kencox]

This scenario presented the same issue for me:

vSphere 6.0U2 with vDS 5.1 and VDP 6.1.2

As soon as I moved the VDP back to a local standard switch, the web client connects with no problem.  I attempted to create a backup job for a single VM ('testvm') which was still on the vDS and that just hung.  After moving 'testvm' to the same local standard switch, the backup job creation completed successfully.

[jo_strasser]

Thanks fpr updating.

Please also create a VMware Support Ticket to get a quick and fast resolution for that.

Thanks JO!

[Evato]

All going well, fixes should be out soon. Have been working with VMware and EMC support and it looks like there may be an update to the .war file in the VDP plugin on the vCenter server.

For those experiencing the problem who haven't created a ticket with VMware, please do so. Ensure that you also advise the version of vCenter server being used.

Will update once have managed to test here.

[jo_strasser]

Hi,

same info from my site.

My SR is also escalated to VMware.

Waiting for the fix :smileywink:

Thanks JO

[dsohayda]

I'm having this issue with a new 6.1.2 VDP deployment connected to a 5.5u3c VCSA.

The strange thing is I am having no issue with the same 6.1.2 VDP version in our lab connected to the same version VCSA, 5.5u3c, using a 5.1 VDS.

The one difference I can think of is that the VDP appliance in the lab started as 6.0, or whichever version required a migration upgrade, and has been upgraded to 6.1.1 and then 6.1.2.

The lab was upgraded over a month ago and has had no issues. Backups are running fine.

The new deployment has never worked.

I opened a ticket with VMware support, but they have been of little help. At first they just flat out told me the 6.1.2 VDP was only supported under vCenter Server 6 or higher. When I showed them that this was not true and I had it running under 5.5 they said nothing.

Yesterday I finally heard back from them, but only to say that they escalated the case to EMC.

This, in addition to the many backup failures and orphaned snapshots, is really pushing us away from VDP.

[magi]

Hello,

VMware patched my vCenter with a new VDP client plugin and everything works fine now. There will be a KB with this fix very soon he said.

I think everyone who opened a ticket will get it.

Greetings

Martin

[jo_strasser]

Thanks for that information! :smileyhappy:

[mabrown76]

Martin could you share your SR # with me?

Thanks,

Mike

[magi]

The SR# is 16947588504.

Martin

[mabrown76]

Thanks!

[tomz997]

Thanks for the "Standard switch" solution..

We had Distributed switch and we were unable to connect to the appliance .... now with Standard Switch, everything works!

But, ideally, we would like to use only Distributed switchs

[SavkoorSuhas]

So there is a hot fix available now for the appliance 6.1.2

Patched successfully on multiple platforms.

Please open a ticket with VMware, and we will get it fixed for you.

Suhas

[chadc1979]

Is there a KB article yet on this or do we have to open a ticket to get the fix and does it address the issue of not being able to create backup jobs if the guest VM is also on a distributed switch?

[agolota]

I've got a patch with vdr-ui-war-6.1.2.war file. After swapping old war for new war file everything started working fine. Also on distributed switch.

[encode]

Would you mind sending me a copy of the patch?  Thanks.

[jo_strasser]

VMware is able to share the patch.

Please open a SR and you will get the patch directly from VMware.

The official KB is offline because VMware will release a new build soon.

[chadc1979]

Here is the KB 2145236, it's available online now along with the patch file.

[wilsonmj]

Thanks so much for this.  Support has been... disappointing.

Only stumbling block I ran into was ownership on the war.  "chown vsphere-client:users vdr-ui-war-6.1.2.war" fixed me right up. 

[vmwaredownload]

I can not find KB 2145236 :smileysad:

Would you pls share it for me? or give me url.....

Many thanks.

[HughCW2207]

After a bit of digging, was able to find the KB article only to be told I'm not authorised to view it, it's been removed or the reference is out of date.  Logged a SR with support as I can't get access to any of our VDPa's using the Web Client. :smileysad:  (http://kb.vmware.com/kb/2145236)

[dsohayda]

I hope they're updating the kb because when I was following it yesterday the path to the plugin on the VCSA was incorrect:

Navigate to following directory:

cd etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vdp2-6.1.0.19/plugins/

on my 5.5u3c VCSA it's actually

/var/lib/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vdp2-6.1.x

the patch worked for me once I figured out where to apply it.

[jo_strasser]

Thanks a lot for all replies here :smileywink:

Greets JO

[Evato]

Unfortunately it looks like the post has been removed and will need to be referred to when opening a support case with VMware.

It sounds like once the patch has gone through all the QA it will be re-released (hopefully with an updated VDP appliance)

[jkoebrunner]

Can somebody please share the patch?

We need a solution for this issue right now.

[vmsysadmin20111]

So it's been more than a month now, the problem is still there. No official KB and no patch. WTF, VMware???

[szilagyic]

I've spend over 8 hours setting up a new VDP instance before seeing this post.  Thank you for posting the workaround, which is to set the VDP to a standard vswitch instead of a dvswitch.  That got it working here too.  How could this have gone through and been released with this bug??  Does VMware not test these solutions before they are released?  Especially this which geared at enterprises, chances are they are not using a standard vswitch.  Very frustrating and makes me doubt VMware's releases at times.

[jo_strasser]

Hi,

repeated:

Please open a official SR at VMware to get the patch.

If you have a supported environment U are save.

VMware will release a new build of VDP soon.

Thanks...

BR/JO

[jffgrnfld]

The frustration comes from the fact that this thread is about the only "official" way to get information about this pretty major bug.  There should be an active KB article with updated information (eg. open an SR to get a hotfix / awaiting 6.1.3 release / or whatever) and the product download should have a warning pointing to the KB.  Too many hours wasted by customers only to finally find this thread and understand why.

[griggiel71]

I am having the same issue, been looking at this for over a week now.

originally told it was a certificate issue ... obviously not....

new build on latest software, so originally thought it was the build side as works fine unless pointing to vDS, systems do not even need to be turned on or connected, just the vhardware needs to be set to a vDS to have it stall.

I will be raising a call with VMware as still looks like they have not released anything for this issue.

[Dragan201110141]

Anything new on this problem? Does anybody can share patch resolution because it's not available???

BR,

Dragan

[Madmax01]

Hi guys,

i did the patching also and restarted webclient.  So i'am able to connect now to VDP's. but seeing speed differences between vCenter 5.5/6.0

once clicking on the VDP Plugin on 5.5 until 2 secs i could choose between the VDP Appliances.

if i do same on 6.0 U2 > i could wait  >30secs to see the Appliances. didn't had that with 5.5 before. (No performance issues there. Thinking PSC is not the best Solution)

So i hope next version is back more stable > as currently i regret did upgrade to vCenter 6.0.

PS: not sure if it's allowed to post non-officially Patches

Best regards

Max

[Carcaridon]

I've had the issue with the VDP plugin not showing in the vSphere Client since the upgrade to 6.1.2.19 on vCenter 5.5U3a.  Been working with VMware for a week to get it resolved.  They supplied the patch file, which was only 2kb different than the .war file already there.  Dropped it in and restarted vsphere client.  Still didn't show.  Now we're looking at perms for that file since it's owned by root, but in 5,5U3a I'm not showing the vsphere-client as a user.  Waiting to hear back now.  It's been escalated to EMC.

[SavkoorSuhas]

Do you have the SR number for this one?

Suhas

[Carcaridon]

Here is my SR# 16112176705.

Thanks.

[SavkoorSuhas]

Try this:

http://www.virtuallypeculiar.com/2016/05/unable-to-connect-vdp-61-to-web-client.html

Worked for all cases with me.

Suhas

[Carcaridon]

Thanks for the link to your site.  I actually tried this yesterday but the vsphere-client user does not exist in 5.5 vCenter.

[SavkoorSuhas]

Interesting. Are you on appliance 5.5? I can get this tested in a day.....

Suhas

[Dragan201110141]

Thx Suhas for provided patch...works like charm...

BR,
Dragan

[Madmax01]

Guys, are you facing same issues also with :

- The most recent checkpoint for the VDP appliance is outdated

- Backup scheduler is not running

- Maintenance service are not running

- Replicationservice is not running

even with the new war file  i get for some Appliances an Issue for Connect.  Seems it's not fully Backward compatible. having 80% 6.1.1.19 Versions

Need to bounce the VDP's several times per week.

very annoying.

Best regards

Max

[parapa29]

Hello, I was with this same problem in my VDP 6.1.2.19 environment.

The following solution given by VMWare now working environment.

Hello Ney,


I am Rui Ferreira from VMware support and i will be working with you on this VDP case.

I didn't call you because i picked up this case today and it is Saturday.

By looking at your case description, my understanding is that you are able to install VDP without any problem.
After installation, on vSphere Web Client you select VDP, select one of the appliances and then nothing happens, a watch icon shows, screen gets greyed out and it stays like that forever.

You deploy VDP from web client, right?
Your VDP is running on a distributed switch, right?

If the above are correct, you may be running into a known issue.

In order to fix this issue, please follow this procedure:


1 - Download the attached file vdr-ui-war6.1.2.zip



If you are using Linux based vCenter Server (VCSA) :
2 - Log onto vCenter server using putty.

3 - Navigate to following directory:

     cd etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vdp2-6.1.0.19/plugins/

4 - Make a note of the exact name of vdr-ui-war-*.war file.

5 - Rename and change file extension of the existing vdr-ui*.war to war_

     Example: If existing file is vdr-ui-war-6.1.0.war, then rename existing file as vdr-ui-war-6.1.0.war_

6 - Copy the provided newer vdr-ui-war file at the same location. Provide the same name to this new war file as that of the old war. File extension of this file will be war only (and not war_)

7 - Restart vsphere-client service with the command:

 

8 - service vsphere-client restart


If you are using Windows based vCenter Server :
2 - Log onto vCenter server machine.

3 - Navigate to following directory

     C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity\com.vmware.vdp2-6.1.*\plugins

4 - Make a note of the exact name of vdr-ui-war-*.war file.

5 - Rename and change file extension of the existing vdr-ui*.war to war_

     Example: If existing file is vdr-ui-war-6.1.0.war, then rename existing file as vdr-ui-war-6.1.0.war_

6 - Copy the provided newer vdr-ui-war file at the same location. Provide the same name to this new war file as that of the old war. File extension of this file will be war only (and not war_)

7 - Restart the vSphere Web Client services.

[parapa29]

Hello, I was with this same problem in my VDP 6.1.2.19 environment.

The following solution given by VMWare now working environment.

Hello Ney,

I am Rui Ferreira from VMware support and i will be working with you on this VDP case.

I didn't call you because i picked up this case today and it is Saturday.

By looking at your case description, my understanding is that you are able to install VDP without any problem.
After installation, on vSphere Web Client you select VDP, select one of the appliances and then nothing happens, a watch icon shows, screen gets greyed out and it stays like that forever.

You deploy VDP from web client, right?
Your VDP is running on a distributed switch, right?

If the above are correct, you may be running into a known issue.

In order to fix this issue, please follow this procedure:

1 - Download the attached file vdr-ui-war6.1.2.zip

If you are using Linux based vCenter Server (VCSA) :
2 - Log onto vCenter server using putty.

3 - Navigate to following directory:

     cd etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vdp2-6.1.0.19/plugins/

4 - Make a note of the exact name of vdr-ui-war-*.war file.

5 - Rename and change file extension of the existing vdr-ui*.war to war_

     Example: If existing file is vdr-ui-war-6.1.0.war, then rename existing file as vdr-ui-war-6.1.0.war_

6 - Copy the provided newer vdr-ui-war file at the same location. Provide the same name to this new war file as that of the old war. File extension of this file will be war only (and not war_)

7 - Restart vsphere-client service with the command:

8 - service vsphere-client restart

If you are using Windows based vCenter Server :
2 - Log onto vCenter server machine.

3 - Navigate to following directory

     C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity\com.vmware.vdp2-6.1.*\plugins

4 - Make a note of the exact name of vdr-ui-war-*.war file.

5 - Rename and change file extension of the existing vdr-ui*.war to war_

     Example: If existing file is vdr-ui-war-6.1.0.war, then rename existing file as vdr-ui-war-6.1.0.war_

6 - Copy the provided newer vdr-ui-war file at the same location. Provide the same name to this new war file as that of the old war. File extension of this file will be war only (and not war_)

7 - Restart the vSphere Web Client services.

[ivguimar]

The hotfixes described in kb 2145686  Deploying the vSphere Data Protection 6.1.2 plug-in fails with the error: Type 'com.vmware.vim.binding.vim.dvs.PortConne… solved the issue

[naymar27]

Hey,

there's KB regarding this issue. I tried it and it fixed the problem.

Deploying the vSphere Data Protection 6.1.2 plug-in fails with the error: Type 'com.vmware.vim.binding.vim.dvs.PortConne…

[naymar27]

I have the same issue and there's a KB solving this issue

Deploying the vSphere Data Protection 6.1.2 plug-in fails with the error: Type 'com.vmware.vim.binding.vim.dvs.PortConne…

[pmwurst]

Hi guys,

we had exactly the same issues in our environment and I just want to summarize the gathered information from some blog articles (thank you all!) needed to fix the issues here:

https://communities.vmware.com/thread/417865?start=0&tstart=0

• This describes the missing value in the extended vApp parameter „vm.vmname“ but DID NOT fix our issue. However it may be the cause for other (customer's) problems!

http://www.virtuallypeculiar.com/2016/05/unable-to-connect-vdp-61-to-web-client.html

• This article led us to the „final fix“ – but as you can imagine we won’t take the risk of installing packages from "unreliable sources" in our production environment…

After some more time of searching I found your question / link here:

https://communities.vmware.com/thread/533954?start=0&tstart=0

• It's some kind of unedifying that the discussion around this (imho) major incident was started several months ago and the vmware support is still struggling with advices on that,
  but the customers involved pointed out that the issues are connected to the use of distributed switches (which I couldn’t imagine so far…) - thank you all for that!

Though the title of the linked KB article in the blog replies (29th of July) is rather misleading – and therefore hard to find for customers with that issue – it has done the trick:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2145686

Hopefully the mentioned bug get’s fixed soon in a new VDP / vCenter release or patch and moreover I hope that the support team is able to associate upcoming issues like this with the known bug.

It would be very helpful to have a KB article on this which is not only addressing deployment issues but issues with VDP and the use of distributed switches!

Kind regards, pw

[SavkoorSuhas]

Hi,

Thanks for collating all the documents.

You can certainly open a case with VMware if you would like a fix for it and we will get it patched for you.

The KB article is pulled out by the documentation team. The fix is planned to be included in the next release of VDP.

Suhas

[Madmax01]

Hoping they doing some Optimizations on the Gui,...... as generating VDP's from scratch are painfully.  Nice to see Kind of Input VM List for Backup. and not clicking xxxx Times,.....