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

[jkoebrunner]

Can somebody please share the patch?

We need a solution for this issue right now.

[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.

[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.