Skip to main content

How to change password for sasevdb user?

Question:
We have installed SAS 9.4 M4 Visual Analytics (VA) on a single Windows 2008 server.

We need to change the password for the sasevdb user. How to change password?

Should this be done using the SAS Deployment Manager (SDM)? How can we reset the Postgres password ?

Answer:
All the SAS account password should be changed with the SAS Deployment Manager. Password can be changed using Deployment manager for every single component that is part of the deployment. Once you use SAS Deployment Manager to reset the password, you need to restart the environment.

This is the general rule in SAS. Eventually, there could be some additional configuration file missing from this change. Therefore you may need to use grep utility. File handled by each maintanance differes and there are more files handled by the SAS Deployment Manger Change password tool.

So for your need just with the SDM should be enough for putting the system to be working again. However I would suggest you to use grep utility to focus in long term actions like for migrations and other big changes on the deployment, and it is being required less and less.

You can refer the below documentation if you have more doubts:

http://documentation.sas.com/?docsetId=bisecag&docsetTarget=p13mipjyz9eh9bn14mqtjgrd2lia.htm&docsetVersion=9.4&locale=en#n0u47qmwa1ebk2n1ffiwsx6ftauh

Comments

Post a Comment

Popular posts from this blog

Starting Gemfire in SAS

Gemfire is available in both Compute and Mid. The default port is 41415. If you have many gemfire, you may have port numbers incremented by 1, for example: 41416. Gemfire is located under Web. <SASCONFIG>/Web/gemfire. To Start: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh start To check Status: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh status To stop: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh stop If it doesn;t start check port number is occupied by any other process. lsof -i tcp:41415 If you only have one instance then 41415 will be default. If you have Lev2 then it will be 41416
Post a Comment
Read more

SAS 9.4 server startup order

In Linux / Unix OS we normally use sas.servers to start the services. The script in the background follows an order to start the services. It is important to follow the order to run the services correctly. In this post we can see what is the order to start / stop and to generate the sas.servers script. It is not really required to memorize the order because SAS provide an utility to create the sas.servers script automatically which will start / stop the service in order. Starting order SAS Metadata server Olap server SAS object spawner SAS / SHARE server SAS / connect spawner SAP table server SAP remote services SAS deployment tester server Stopping will be the same in reverse. How to create sas.server script? We can create sas.server script by using generate_boot_script.sh. if you have made any changes to your environment like adding a new server or spawner we can use the script to generate new sas.server. You can use the script even if you have removed the spanner o...
Post a Comment
Read more

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps.   Open SMC -> Expand Servers -> Expand   In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...
2 comments
Read more