3.06 Admin Password

You set the administrative user as admin and not something different?  I assume you're following the password specifications on the right side of the screen?  And there are no messages saying the password doesn't meet the specifications or that they don't match?  After you enter the password but before you click Log on as admin, click the Password Reveal button and confirm you are entering a password that meets the specifications.

We left the username set to "admin" during the installation.  I can redeploy and change it if you think it might have something to do with what's going on.  The password does meet the requirements and I do not get any error messages when I try to set it.

Have you tried a different browser like Firefox or Chrome?

Yes.  I have tried this in IE11 (with and without compatibility mode), Chrome, and Firefox.  Also tried it on another computer just in case it was an issue with my PC.

Can you email me this log file:

/var/log/esrs/provisioning/provisioning.log

james.williams@emc.com

Sent.

I have exactly the same issue.

Hi, same issue here. My browser throws a JavaScript error (expected Expression, got '<'), likely as something was not found. Unfortunately, even the CLI alternative to reset the password does not work, as it tells me to use the gui for initial password setup.

Have you found out a solution to this issue?

Our solution: Tightly stick to the Install & Operations guide when going through the "YaST2 firstboot" screens. So we used on the interface a hostname with less than 8 characters, no hyphen, and put emc.com as search domain etc.

That magically helped. I cannot pinpoint exactly which of the fields was messing with the "Admin Password" routine....but for us, the cause was somewhere in these settings.

Hi Guys,

I Have the same issue with ESRSVE 3.04. Am following the steps and able to login into Webui using root but no response after entering admin password. Tried redploying it many times. Tried different versions of ESRS like 3.04, 3.06, 3.08 and 3.10 using different browsers but getting same error.

Not able to figure out what the exact issue is ?

/beginvent

I have had this same issue, and others as well.  I have used the many flavors of ESRS over the years, and to be honest managing ESRS/VE is the worst.  EMC needs to grab a decent software engineer from the VMWare staff, and a QA engineer (I'll do it for you, because I can make ESRS/VE break any day, any time, and in any environment apparently, and stick them in a room until they can figure out a simple, reliable way to deploy this thing. 

In various deployments, I have received the "Use Long Complex Passwords" problem multiple times.  I also have come across the issue that if your support account doesn't have the correct privleges, the admin account doesn't get properly created, and you end up in an endless "bad password" loop, and the script to change it via SSH either says "Failed to reset password for the user :admin.[Could not open file for writing] [-9]" or it says "This Util is used to reset the password of Configured Users.User admin hasn't been set with password for the first time.

Kindly use the WebUI to set the password."

I have done several ESRS/VE deployments.  None have gone well.  "yast2"?  Really guys?  Spend some time to write a script like boxmgmt for RecoverPoint.  That works solidly.

/endvent

In any case, my advice is to open a ticket with EMC.  You will get bounced around for a few days, but eventually a (very busy) field engineer will be able to get on a webex and finish it for you.

Thanks Storagetalk,

This thing is solved. thanks to the FSS . I have redeployed it on the webex. There were some changes to be made on configuration settings like maintaining the consistent server name and it was validated using FSS's username and passcode.

I can confirm the behavior.

The only solution was to redeploy the appliance, and to follow strictly the steps.

In my case, the NTP server configuration missed during setup, resulting on this bug on admin password initialization.

I too have the same issue, after the license agreement accept page, its not taking any password.

In my case EMC installed the ESRS

Log showing as below:

INFO  [2015-03-03 12:20:14,706] com.emc.esrs.provisioning.service.PVSServiceImpl: Inside getConfigurations in PVSServiceImpl

ERROR [2015-03-03 12:20:14,763] com.emc.esrs.provisioning.dao.ProvisioningDaoImpl: Connection to DB failed org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.

ERROR [2015-03-03 12:20:14,763] com.emc.esrs.provisioning.dao.ProvisioningDaoImpl: Error in getting Configuration details java.lang.NullPointerException

ERROR [2015-03-03 12:20:14,763] com.emc.esrs.provisioning.service.PVSServiceImpl: ProvisioningServiceException :com.emc.esrs.provisioning.exception.ProvisioningServiceException: Error occured in getting the Configuration

WARN  [2015-03-03 12:20:14,787] com.yammer.dropwizard.config.ServerFactory:

I had the same problem and I fixed it. Its simple but it took me some time.

Change the hostname BEFORE the system is initialized.  At 1st boot, in yast, insert your network config and dont forget to change the hostname.

If you change the hostname after the system has been initialized, you will get your error.

The default hostname is linux. If you configure your ip, and then connect with ssh to finish the rest, you will break the system.

Thats what I did..   1st boot..  provide IP, then log with ssh.  Working in the vmware console sucks, si I wanted to use putty.  This is what triggered my problem

Once i logged with ssh, I started yast and i finished the config..  hostname, ntp, dns, etc.. andthen I was not able to log on the webUI.

After some digging, I have found out this entry in /var/log/esrs/usermanagement.log:

3381 The system hostname key is missing from the Lockbox. : File : /etc/esrsve/auth/cstdir/csp.clb

3382 ERROR [2016-11-16 20:42:40,380] com.yammer.dropwizard.jersey.LoggingExceptionMapper: Error handling a request: 47c4cf1dfcacb170

So I went and changed the hostname back to  linux and was able to initialise the admin account.

Hope this helps.