Bob Lin, Chicagotech-MVP, MCSE & CNE
Data recovery, Windows OS Recovery, Networking, and Computer Troubleshooting on
http://www.ChicagoTech.net
How to Install and Configure Windows, VMware, Virtualization and Cisco on
http://www.HowToNetworking.com
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.
Situation: The client has Paloalto Firewall running GloablProtect VPN and Site-to-site VPN to AWS tunnel. The user on office can’t access the AWS tunnel but VPN user.
Troubleshooting: 1. Monitor shows aged-out.
2. The detail view shows, bytes received is 0.
Conclusion: AWS blocks VPN IP addresses. Have AWS configure their route for VPN IP addresses.
Situation: The client configured Paloalto Firewall to allow VPN users accessing AWS Tunnel. However, the VPN home users can’t access the AWS tunnel and Monitor doesn’t show any traffics.
Situation: The client setup a new WiFi printer. The printer has a good IP address but no one can send the printer job.
Troubleshooting: They have two WiFi, staff and guest. Both use the same IP range but can’t see each other. The WiFi printer was setup using Guest IP address so that no staff can’t send the print job. Re-set printer to use staff WiFi that works.
