Change the userid that Harvest will use to access the database in SQL Server

Products

• CA Harvest Software Change Manager
• CA Harvest Software Change Manager - OpenMake Meister

Issue/Introduction

The following instructions describe how to change the default userid that Harvest uses to access the DB.

Environment

Release : 13.0.3 and higher

Component : CA Harvest Software Change Manager

Resolution

1. Login to SQL Server Management Server using the “sa” account
2. Expand the Security node, right click on “Logins” and select “New Login…”

3. On the “Login – New” window, provide the username of the new user.  Make sure to select “SQL Server authentication”.  Provide the password you want to use in the “Password” field and again in the “Confirm password” field, and at the bottom make sure the default database is set to the Harvest database.  For purposes of example, we will use a login name of "cascm".


4. On the “User Mapping” tab make sure this new userid is mapped to the Harvest database, and in the Database Role Membership list below make sure that “db_owner”, “harvest_group” and “harvest_rep” groups are selected. 



5. On the Status tab, make sure that permission to connect is granted and the login is enabled.  Click OK when done.  



6. Navigate to the Harvest database, expand Security and Users.  Make sure the new userid is listed among the users.  Right click and go to Properties



7. On the General tab make sure the default schema is “dbo” 



8. On the Owned Schemas” tab make sure db_owner, harvest_group and harvest_rep are selected. 



9. The same should be true on the Membership tab.  Click OK to save the changes. 



10. Disconnect from the database engine and connect again using the new userid.  This is needed because SQL Server will prompt to change your password on the first time login.  





11. Once password has been changed and connection is successful, open a command prompt window and execute the svrenc command to update the encrypted password file Harvest will use to connect to the database: 



12. After this the broker and hservers should be able to start normally.