'sqladmin_cv' reset without workflow

Last post 05-10-2019, 10:30 AM by ThomasB. 1 replies.
Sort Posts: Previous Next
  • 'sqladmin_cv' reset without workflow
    Posted: 05-10-2019, 8:32 AM

    We've twice encountered sqladmin_cv issues where a SQL loging failed, once during a CommServe DR test and once during a hardware refresh installation based on the previous dumps.

    Assuming you can connect to the SQL instance to reset its password, how do you properly generate the registry secure strings for the sqladmin_cv account that Commvault / the installer uses?

    I'm talking about HKLM\SOFTWARE\Commvault Systems\Galaxy\Instance001\Database, for the following strings:

    - pACCESS
    - pCLOUDACCESS
    - pDM2ACCESS
    - pWFACCESS

    Perhaps something as simple as the following?

    "P@ssword1" | ConvertTo-SecureString -AsPlainText -Force | ConvertFrom-SecureString

    I don't care about the workflow, and there is no sign of the CV10 Windows Resource Pack in CV11. I need to be able to quickly reset this when a CommServe is down / HW refresh installation is in progress, not requiring me to jump through support hoops. It looks to be extremely easy if you have the correct procedure, yet made complex for no apparent reason.

    Kind regards,
    Thomas

  • Re: 'sqladmin_cv' reset without workflow
    Posted: 05-10-2019, 10:30 AM
    For future reference, cfr. http://kb.commvault.com/article/CS0035. sqlexec_cv is not the only one with a password... You can use the following to change any of those mentioned accounts' passwords to a random string:
     
    DBMaintenance.exe -cslogin sqladmin_cv -cspwd  -CreateSQLLogin -SetRegistry
     
    This wiill update the registry and the SQL user. You can use "-cspwd <password>" to specify your own password, this allows you to test SQL connectivity through SQL Management Studio for example.
     
     
    Now, for installation issues: Commvault's installation wizard (based on CV11_SP14) uses a separate registry key in:
     
    HKLM\SOFTWARE\Commvault Systems\Galaxy\Instance001\Installer\ConfigureClient\ (pAccess & pDM2Access strings).

    You can change your sqladmin_cv account with the above command, then stop the installation, re-start the installation and resume. It should now be able to connect to SQL. In our case we had to go one step further:
     
    Change the SQL 'sa' account, use SQL-based authentication to reset sqladmin_cv, but specify your own password, then use SQL Management Studio to verify this login.  After copying the registry key to the installer strings, stopping and resuming the installer, the installer then asked us for the SQL sa's password. After that it was able to properly connect to SQL!
The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy