SAS HTTPD Instance Stopped

[JuanS_OCS]

Sorry, I cannot help you there much, I don;t have the passwords set during your installation (noone does, except who did the installation and to whomever he/she distributed the passwords/documentation).

My suggestions:

- go to SAS Management Console to the SAS Trusted User, check on accounts, on the bottom, if the account is locked, and try to authenticate again once you are sure it is unlocked. 

- try the password from sasadm@saspw. It is possible that during installation you checked in the box to set every internal account with the same password.

- if everything else fails, you can change the password with the SAS Deployment Manager. If you get to this point, be careful and I would advise you to get yourself in contact with SAS Technical Suport and do it together.

[japsas100]

Yes I have check the checked in the box to set every internal account with the same password.

What is default password for the same or which internal user comes fast during configartion?

[JuanS_OCS]

Default would be probably blank.

[japsas100]

Thanks for reply.

Passwordis is not blank in my case.

I am not able to login to smc its throwing error like "application could not log to xxxx" I have check the service is running. 

Please advise?

[JuanS_OCS]

Well, regarding the password, as mentioned, i cannot help you much, but showing you the option you need to review your installation steps, or change the password with the Deployment Manager.

About the SMC, you might have the port 8561 blocked, or just the pasword wrong (if you can log in with other users). Try with an SMC from the server itself, if you can.

Otherwise, please contact SAS Technical Support, because you might need someone to give a look to your environment with you.

[Kurt_Bremser]

If you've managed to forget the sasadm@saspw password, and have no other user with the permissions to reset that password, then maybe SAS TS might be able to help you. But I fear you will have to repeat the whole configuration process anyway, which may mean you have to recreate all your metadata.

[japsas100]

When i am trying to login SMC with sastrust@saspw user its showing below message

Access to this account(sastrust) is locked due to excessive log in failures.

But when i login with sasadmuser its showing below msg

The version of sas management console and version of sas metadata server do not match.

Please advise?

[JuanS_OCS]

The message with sastrust is what we discussed.
The message with sasadm is a warning due to tge fact that the server and you client versions differ.

Although it is not advised to work on this way, just for unblocking sastrust you xan move forward.

When you will update the server, please update (with the same software) the clients as well. And you will be fine.

[japsas100]

Thanks JuanS_OCS

Not fully understood your last message.

Could you please explain in simple steps.

[JuanS_OCS]

Sorry, to be honest, I wrote this message yesterday with the email on my phone. That might explain a lot. Let me rephrase.

You got a message that sastrust is locked, exactly what was discussed on one of our previous communications. Therefore you need to unlock it with an unrestricted account, such as sasadm. This should not be a problem.

You got another message logging in with sasadm. This message is just a warning, but SMC will work. The message means that the versions of software on the server and your client are a bit different (maybe different maintenance, or different hotfixes applied for metadata server and SMC).

If you get this warning, the general recommendation is to not work with different versions, because it might corrupt metadata or even content server, simply because internal components, as public types, or the way to handle a request, might have different code.

But if our aim is just unblocking the sastrust user, we should be able to move forward. 

So, connect to SMC with the sasadm@saspw account, open the properties of the SAS Trusted User, go to the accounts tab, on the bottom of the window, click Edit/Update. You will be prompted with the question if you want to unlock sastrust@saspw, click on Yes/OK, and you should be able to try to connect to SMC again, to check if you ca log in with sastrust@saspw and whatever password you think is the right one. Once you get the password, resume the upgrade of VA to 7.4

PS. As reminder: Not for now, but for the moment when you will finish the update of the VA server to 7.4, please update (with the same software and hotfixes) the clients as well. 

[sewa_bal_gmail_com]

Thanks JuanS_OCS,

When I clicked update under account tab, I did not receive any prompt with the question if you want to unlock sastrust@saspw,

When I clicked on update, a new popup is open to entering the new and confirmed password.

Please advise?

[JuanS_OCS]

Just for my info: @japsas100 == @sewa_bal_gmail_com ?

I think you should not have changed the password there in SMC. I did not provide that instruction, I said just to unlock it.

Really, and thinking on your best interest, this time it is better if you give SAS Technical Support a call, you need real-time support. Happy to continue helping you here, as usual, but I have the feeeling it is not working for this question. Otherwise, it would take several trials and errors.

I suspect SAS Technical Support would suggest to update the password of sastrust@saspw with the SAS Deployment Manager, as initially commented, but we shall see. Please let us know how it goes.

[PaulHomes]

Also consider that if you change the password for the SAS Trusted User using SAS Management Console, without changing all the instances of it's use using SAS Deployment Manager (as Juan suggested), the account is probably going to get locked again as the SAS platform services that use the old sastrust@saspw password continue to provide a now-invalid password to the SAS Metadata Server. 

[japsas100]

Thanks Juan and Paul,

Finally, I have unlocked the user id from SAS Management Console.  Now it's working fine.

Just want to check why does it mean if we clicked this option "Reducing the Number of Password Prompts" during initial installation.

[JuanS_OCS]

If you click that option when you provide the password of sasadm@saspw, every internal account (sastrust@saspw, sasevs@saspw, SharedServices, etc) will have the same password as the password provided for sasadm@saspw.