Situation: The client is running Windows 10 on her computer. This is Windows 10 PC. After a Windows update, the Microsoft Print to PDF is missing. If trying to enable Microsoft Print to PDF, I get error code: 0x800f0922.
Resolution: 1. Stop spooler service.
2. Go back Windows features to enable the Microsoft Print to PDF
3. Start the spooler service.
Situation: The client attempts to install SCOM Agent on a n untrusted computer and runs MOMCertImport, but gets an error.
MOMCertImport /SubjectName %computername%
UpdateRegistry(): CRegKey.Create failed: Access is denied.
Error code: 80070005
FindExistingCertBySubjectName(): UpdateRegistry Failed: Access is denied.
Error code: 80070005
FindExistingCertBySubjectName failed: Access is denied.
Error code: 80070005Troubleshooting: He needs to run command prompt as administrator.
Situation: The client following this how to to create a new rule: Configure a policy for DMZ accessing Trust. However, it doesn’t work and PA firewall Monitor shows policy deny.
Troubleshooting: From the policy status we can see the new policy is grayed out meaning it is disabled. For example # 25 DMZ 172.16.80.3 port 5721.
Click Enable and commit that fixes the problem.
The Operations Manager Server could not execute WMI Query “Select * from Win32_OperatingSystem” on computer Server name.
Operation: Agent Install
Error Code: 800706BA
Error Description: The RPC server is unavailable.
Troubleshooting: 1. Make sure Remote Registry service is running
2. It could be the firewall issue. Turn off the Firewall on the client for a test.
3. Make sure all these services are running: Netlogon, Windows Installer, Windows Updates.
4. Make sure these port are opens:javascript:window[“$iceContent”]
4. Install the Agent manually.
Situation: The client attempts to create a new rule to move all email from Wish.com to Deleted Item folder. However, it doesn’t work.
Problem 1: wish.com email keep changing their ender email address so that you mat not be able to move the new email to Delete Item folder.
Problem 2: use *@mail.wish.com doesn’t work.
Resolution: You should create a rule based on domain name or sub-Outlook move email rule doesn’t work name , for example mail.wish.com. Please reer to this post for more details:
How to setup a Rule to move an email to a folder automatically
Situation: When install SCOM Agent on an untrusted computer, you may receive this event:
Log Name: Operations Manager
Source: OpsMgr Connector
Event ID: 21016
Description: OpsMgr was unable to set up a communications channel to FQDN and there are no failover hosts. Communication will resume when FQDN is available and communication from this computer is allowed.
Troubleshooting: If you just imported CA and untrusted client certificates on the untrusted computer, restart al SCOM service on SCOM Server. That should fix the problem and the Event Viewer will show Event ID: 21019
Description:
OpsMgr has returned to communicating with it’s primary host FQDN.
Situation: When install SCOM Agent on an untrusted computer, you may receive this event:
Log Name: Operations Manager
Source: OpsMgr Connector
Event ID: 20070
Description: The OpsMgr Connector connected to FQND, but the connection was closed immediately after authentication occurred. The most likely cause of this error is that the agent is not authorized to communicate with the server, or the server has not received configuration. Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.
Troubleshooting: If you just imported CA and untrusted client certificates on the untrusted computer, restart al SCOM service on SCOM Server. That should fix the problem and the Event Viewer will show Event ID: 21019
Description:
OpsMgr has returned to communicating with it’s primary host FQDN.
Situation: When install SCOM Agent on an untrusted computer, you may receive this event:
Log Name: Operations Manager
Source: OpsMgr Connector
Event ID: 20070
Description: The OpsMgr Connector connected to FQND, but the connection was closed immediately after authentication occurred. The most likely cause of this error is that the agent is not authorized to communicate with the server, or the server has not received configuration. Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.
Troubleshooting: If you just imported CA and untrusted client certificates on the untrusted computer, restart al SCOM service on SCOM Server. That should fix the problem and the Event Viewer will show Event ID: 21019
Description:
OpsMgr has returned to communicating with it’s primary host FQDN.
Situation: When install SCOM Agent on an untrusted computer, you may receive these events:
Log Name: Operations Manager
Source: OpsMgr Connector
Event ID: 20070
Description: The OpsMgr Connector connected to FQND, but the connection was closed immediately after authentication occurred. The most likely cause of this error is that the agent is not authorized to communicate with the server, or the server has not received configuration. Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.
Event ID: 21016
Description: OpsMgr was unable to set up a communications channel to FQDN and there are no failover hosts. Communication will resume when FQDN is available and communication from this computer is allowed.
Troubleshooting: If you just imported CA and untrusted client certificates on the untrusted computer, restart al SCOM service on SCOM Server. That should fix the problem and the Event Viewer will show Event ID: 21019
Description:
OpsMgr has returned to communicating with it’s primary host FQDN.
problem: We are running SCOM 2019. We have a problem to setup email Notification Channel with Failed to save the Notification Channel error.
Note: The following information was gathered when the operation was attempted. The information may appear cryptic but provides context for the error. The application will continue to run.
System.InvalidOperationException: The endpoint could not be inserted. See inner exception for details. —> Microsoft.EnterpriseManagement.Common.ManagementPackException: Database error. MPInfra_p_ManagementPackInstall failed with exception:
Database error. MPInfra_p_ManagementPackInstall failed with exception:
[SQL Error Code: -2146232060][MP ID: dcfdedc4-68bd-42b4-1e9a-ba94b1577732][MP Version: 10.19.10050.0][MP PKT: ] Procedure or function p_MPImportXML has too many arguments specified.
at Microsoft.EnterpriseManagement.Common.Internal.ServiceProxy.HandleFault(String methodName, Message message)
at Microsoft.EnterpriseManagement.Common.Internal.MonitoringNotificationServiceProxy.UpsertNotificationEndpoint(String name, String displayName, String description, String languageCode, String endpointImplementation, Int32 innerNotificationEndpoint, Boolean isUpdate)
at Microsoft.EnterpriseManagement.MonitoringNotificationManagement.UpsertNotificationEndpoint(NotificationEndpoint notificationEndpoint, ManagementGroup managementGroup, Boolean isUpdate)
at Microsoft.EnterpriseManagement.MonitoringNotificationManagement.UpdateNotificationEndpoint(NotificationEndpoint notificationEndpoint)
at Microsoft.EnterpriseManagement.Administration.NotificationEndpoint.Update()
— End of inner exception stack trace —
at Microsoft.EnterpriseManagement.Administration.NotificationEndpoint.Update()
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Notification.ChannelCompletionPage.CommitChanges(Object sender, DoWorkEventArgs e)
: Database error. MPInfra_p_ManagementPackInstall failed with exception:
Database error. MPInfra_p_ManagementPackInstall failed with exception:
[SQL Error Code: -2146232060][MP ID: dcfdedc4-68bd-42b4-1e9a-ba94b1577732][MP Version: 10.19.10050.0][MP PKT: ] Procedure or function p_MPImportXML has too many arguments specified.
I have try to restart all System center services and restart the server, but that doesn’t fix the problem.
Possible causes: upgrading to UR2 of SCOM 2019 or database or the table structure changing.
Resolution: Install KB4558752 update. That fixes the problem.