Cannot connect to VBA after MS hotfixes.

Everytime I try to open that link, either by clicking on your link or searching through the portal, I get a salesforce.com error.  I get this a lot through the EMC portal.

Login Error
Your login attempt using single sign-on with an identity provider certificate has failed. Please contact your salesforce.com administrator for more information.

Hello,

Following KB article contains solution for it -

https://support.emc.com/kb/195277

Regards,

Pawan

Well, I'd love to do that, except the cert on this appliance is STILL insecure and now after the hotfixes, even IE won't connect to it.  I've tried FF, Chrome, safari, and IE and none of them will connect to the appliance due to an insecure cert.

Issue -

The NetWorker VMware Protection integration is configured in the environment and scheduled backups were working successfully.  The policies started encountering a failed state and the policy message shows:

Unable to connect to VBA [EBR_APPLIANCE], error Cannot establish session to VBA.

When you log into the EMC Backup & Recovery (EBR) Virtual Backup Appliance the "dpnctl status" command indicates that the mcs service is down. The EBR web configuration screen only shows that the backup scheduler service is down.  Attempting to start the mcs service with "dpnctl start mcs" fails to properly start the mcs service.

The dpnctl.log, under the /usr/local/avamar/var/log/ directory, shows:

YYYY/MM/DD-HH:MM:SS Starting Administrator Server...
YYYY/MM/DD-HH:MM:SS Started
YYYY/MM/DD-HH:MM:SS Caught Fault -
YYYY/MM/DD-HH:MM:SS  Type : com.vmware.vim25.InvalidLogin
YYYY/MM/DD-HH:MM:SS  Actor : null
YYYY/MM/DD-HH:MM:SS  Code : null
YYYY/MM/DD-HH:MM:SS  Reason : Cannot complete login due to an incorrect user name or password.
YYYY/MM/DD-HH:MM:SS  Fault String : Cannot complete login due to an incorrect user name or password.
YYYY/MM/DD-HH:MM:SS Exception running : VMWare
YYYY/MM/DD-HH:MM:SS - - - - - - - - - - - - - - - END
YYYY/MM/DD-HH:MM:SS dpnctl: ERROR: error return from "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --start" -exit status 1

Resolution

Update the vCenter registration information under the EBR configuration screen.  If the vCenter server registration fails to save with the SSO username and password, ensure the password has not expired.  If expired, update the SSO password via the vSphere Web client interface.  Once the vCenter registration information is updated, the EBR appliance needs to be restarted.

Maybe a better question is, Does the 8.2.1 VBA upgrade work with 8.1.3 server?  And does it fix all the ssl stuff?

Alright, I found a desktop with an unpatched IE and got into the admin interface.  But this did not fix the issue.  I updated both the VMWare and NetWorker configs.

Hi,

uninstall of KB3061518 clear the issue for me

the registry hack/tweak doesn´t work (maybe you have another workaround)

thanks

br

Harri

Windows 2008 R2, Networker 8.2.1, VBA 1.1.1.46

ok, not good to hear that you have new issues...

i´ve opened a ticket by our networker partner, maybe the provide a permanent fix

I didn't try the registry tweak, was just copying the info EMC support sent me.  Unfortunately, I now have a whole new set of issues with VBA backups. 

Hi HyperV Guy,

thanks fr providing me with this update (my supporter also send me this info)

this registry tweak works without uninstalling the KB

thx

br

Harri

ok.

shutdown EBR;

in my case, Networker 8.1.1.2 in installed on a Windows server 2012 and there i was removed KB by uninstalling them

remember that this KB on Windows 2012 don't create any registry key, as mentioned from Microsoft in https://support.microsoft.com/en-us/kb/3061518  Security update deployment information

then, create this DWORD ClientMinKeyBitLength with this value 00000200 in this path of registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangeAlgorithms\Diffie-Hellman

then go to networker management console, go to device tab, and enable VBA device (vmware internal storage target);

restart Networker Server

restart VBA (ebr);

thats work for me.

Just to be clear (and I'm taking an educated guess here), performing the registry tweak is likely identical to the patch.  I preferred deferring the patch so that when EMC fixes it, I'll be able to re-apply rather than having a permanent registry hack I'll likely forget about.  Just my preference, YMMV.

Hello,

I Just Uninstall of KB3061518 and issue has been solved.

I am using Windows 2012 R2, Networker 8.2.1, VBA 1.1.1.50

BR

A,Q