Answered by:
SCOM 2019 Deployment - APM Account not created

Question
-
Hello,
during SCOM 2019 setup execution (operationsManager), some accounts are supposed to be created automatically (see : https://docs.microsoft.com/en-us/system-center/scom/plan-security-runas-accounts-profiles?view=sc-om-2019)
After deployment, they can be found in SCOM console , under Administration > Run As Configuration > Accounts
In my case, setup execution has created all accounts described in linked page except APM account
See picture :
Should i perform deployment again ? Is there any workaround for creating this missing account after setup execution ?
Thank you for your help
- Edited by Ivan Renoud-Grappin Wednesday, July 15, 2020 4:27 PM
Wednesday, July 15, 2020 4:26 PM
Answers
-
Yes the "APM Account" is created after you've created the first .NET Application Performance Monitor.
I think your setup should be OK in this case, nothing to be worried about.
Blog:
https://thesystemcenterblog.com LinkedIn:
- Marked as answer by Ivan Renoud-Grappin Wednesday, July 22, 2020 7:48 AM
Thursday, July 16, 2020 4:48 PM
All replies
-
Hi,
Yes the "APM Account" is a default Run As Account which should be created when installing SCOM.
Did you wait long enough after the installation to make sure there wasen't a simple delay in the Operations Console?
You could also try clearing the cache of the SCOM management servers & the Operations Console:
How and When to Clear the CacheCan you also verify if the installation of SCOM 2019 was really successful? You'll find the installation log here:
%LocalAppData%\SCOM\LOGS\OpsMgrSetupWizard.logA few things to make sure when installing:
- Local administrator access on the servers
- Sysadmin on the SQL Server(s)
- Make sure the service accounts have sufficient permissions
(https://kevinholman.com/2019/03/08/scom-2016-security-account-matrix)
Can you also provide some details about your SCOM environment? Windows Server version, SQL Server version, SQL Server Reporting Server version etc..
Best regards,
LeonBlog:
https://thesystemcenterblog.com LinkedIn:
Wednesday, July 15, 2020 6:28 PM -
Hello,
thank you for your quick reply
restarting cache on scom console or management server has not solved the issue.
I have checked permissions and it seems ok
Here are the details about SCOM environment :
- 2 management servers running on Windows Server 2019
- 1 web/ reporting server running on Windows server 2019 executing SSRS 2017
- 1 Database server running on Windows Server 2016, executing SQL Server 2017
I have found following errors in setup logs :
[13:35:57]: Error: :RemoveVssExpressWriter failed with the following exception: : Threw Exception.Type: System.Reflection.TargetInvocationException, Exception Error Code: 0x80131604, Exception.Message: Exception has been thrown by the target of an invocation.
[13:35:57]: Error: :StackTrace: at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at Microsoft.EnterpriseManagement.SetupFramework.ActionEngine.Action.Run(String displayStringNamespace, ProgressData progressData, Func`2 progressDelegate)
at Microsoft.EnterpriseManagement.SetupFramework.ActionEngine.InstallStep.Run(String displayStringNamespace, ProgressData progressData, Func`2 progressDelegate)
[13:35:57]: Error: :Inner Exception.Type: System.UnauthorizedAccessException, Exception Error Code: 0x80131604, Exception.Message: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
[13:35:57]: Error: :InnerException.StackTrace: at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.VssApi.CreateVssExpressWriter()
at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.OMServerProcessor.RemoveVssExpressWriter()
[13:35:57]: Info: :RemoveVssExpressWriter failed but is not fatal. Setup will continue.
[13:35:57]: Always: :Current Action: RegisterVssExpressWriter
[13:35:57]: Always: :Registering VSS express writer.
[13:35:57]: Error: :RegisterVssExpressWriter failed with the following exception: : Threw Exception.Type: System.Reflection.TargetInvocationException, Exception Error Code: 0x80131604, Exception.Message: Exception has been thrown by the target of an invocation.
[13:35:57]: Error: :StackTrace: at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at Microsoft.EnterpriseManagement.SetupFramework.ActionEngine.Action.Run(String displayStringNamespace, ProgressData progressData, Func`2 progressDelegate)
at Microsoft.EnterpriseManagement.SetupFramework.ActionEngine.InstallStep.Run(String displayStringNamespace, ProgressData progressData, Func`2 progressDelegate)
[13:35:57]: Error: :Inner Exception.Type: System.Reflection.TargetInvocationException, Exception Error Code: 0x80131604, Exception.Message: Exception has been thrown by the target of an invocation.
[13:35:57]: Error: :InnerException.StackTrace: at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at Microsoft.EnterpriseManagement.SetupFramework.ActionEngine.Action.Run(String displayStringNamespace, ProgressData progressData, Func`2 progressDelegate)
at Microsoft.EnterpriseManagement.SetupFramework.ActionEngine.InstallStep.Run(String displayStringNamespace, ProgressData progressData, Func`2 progressDelegate)
at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.VssApi.CreateVssExpressWriter()
at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.OMServerProcessor.RegisterVssExpressWriter()
[13:35:57]: Error: :Inner Exception.Type: System.UnauthorizedAccessException, Exception Error Code: 0x80131604, Exception.Message: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
[13:35:57]: Error: :InnerException.StackTrace: at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.VssApi.CreateVssExpressWriter()
at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.OMServerProcessor.RemoveVssExpressWriter()- Edited by Ivan Renoud-Grappin Thursday, July 16, 2020 9:44 AM
Thursday, July 16, 2020 9:43 AM -
It doesn’t look related, I found the following blog post with the same error:
Can you verify if all the default management packs got successfully imported after the installation of SCOM 2019?
Management packs installed with Operations Manager
Here’s a list of all the default management packs:
https://docs.microsoft.com/en-us/system-center/scom/manage-mp-installed-during-seutp?view=sc-om-2019Blog:
https://thesystemcenterblog.com LinkedIn:
Thursday, July 16, 2020 9:55 AM -
Hello,
I have checked and it seems following Management packs listed in https://docs.microsoft.com/en-us/system-center/scom/manage-mp-installed-during-seutp?view=sc-om-2019 are missing :
- Operations Manager APM Library Resources (enu)
- Web Application Availability Monitoring Solutions Base LibraryAfter a check to https://social.microsoft.com/Forums/fr-FR/13bec69f-4307-4d01-9540-5b6d612f80dc/accidentally-deleted-apm-run-as-account?forum=scomapm, it seems that APM Account is created when first .NET application is added to monitoring. Can you please confirm ?
Thursday, July 16, 2020 4:24 PM -
Yes the "APM Account" is created after you've created the first .NET Application Performance Monitor.
I think your setup should be OK in this case, nothing to be worried about.
Blog:
https://thesystemcenterblog.com LinkedIn:
- Marked as answer by Ivan Renoud-Grappin Wednesday, July 22, 2020 7:48 AM
Thursday, July 16, 2020 4:48 PM