Skip to main content
NetApp Knowledge Base

SnapCenter Run-As account gets locked in the Active Directory

  1. Last updated
  2. Save as PDF
Views:
357
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

  • SnapCenter 4.1

Issue

After upgrading SnapCenter to version 4.1 and while updating SCSQL plug-in, the specified run-as account gets locked in the Active directory. The following messages are seen in the SnapManagerWeb*.log

2018-08-29T09:43:10.4149996-04:00 DEBUG SnapManagerWeb PID=[20492] TID=[61] Logged in user is <Snapcenter Admin account>
2018-08-29T09:43:10.4149996-04:00 DEBUG SnapManagerWeb PID=[20492] TID=[61] Logged in domain is <Domain>
2018-08-29T09:43:10.4149996-04:00 DEBUG SnapManagerWeb PID=[20492] TID=[61] validate credentails with user
....
2018-08-29T09:43:10.7275256-04:00 DEBUG SnapManagerWeb PID=[20492] TID=[61] Resolving host name using WMI
2018-08-29T09:43:10.8993731-04:00 ERROR SnapManagerWeb PID=[20492] TID=[61] Cannot get FQDN using WMI, exception: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.