Hi,
We recently got the following Alert error in SCOM from GSM. Anybody have any ideas? I am thinking ACS was down last night for some time but not sure.
Global Service Monitor Modules: Failed to discover Global Service Monitor locations.
Description: |
Global Service Monitor Modules: Failed to discover Global Service Monitor locations. Failure step: 'Couldn't get the ACS endpoint from discovery service. SubscriptionId: 'cb5852a1-3478-4841-a753-1ba72d25b0c4', OutsideInServiceBaseUri: 'https://gsm-prod.systemcenter.microsoft.com/'' Message: 'There was no endpoint listening at https://gsm-prod.systemcenter.microsoft.com/DiscoveryService/cb5852a1-3478-4841-a753-1ba72d25b0c4/Endpoints that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.' Details: 'System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at https://gsm-prod.systemcenter.microsoft.com/DiscoveryService/cb5852a1-3478-4841-a753-1ba72d25b0c4/Endpoints that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: The remote name could not be resolved: 'gsm-prod.systemcenter.microsoft.com' at System.Net.HttpWebRequest.GetResponse() at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) --- End of inner exception stack trace --- Server stack trace: at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason) at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.SystemCenter.Cloud.SharedLibrary.Discovery.IDiscovery.GetEndpoints(String subscriptionId) at Microsoft.SystemCenter.Cloud.SharedLibrary.Discovery.DiscoveryHelper.<>c__DisplayClass1.<DiscoverAcsEndpoint>b__0(IDiscovery service) at Microsoft.SystemCenter.Cloud.SharedLibrary.RestCallHelper.ExecuteRestCall[TContract](Uri endpointUri, WebProxy webProxy, String accessToken, RestMethod`1 method) at Microsoft.SystemCenter.Cloud.SharedLibrary.Discovery.DiscoveryHelper.DiscoverAcsEndpoint(String subscriptionId, Uri outsideInServiceBaseUri, WebProxy proxy) at Microsoft.SystemCenter.Cloud.OutsideInUnitModule.DiscoveryWriteActionModule.Execute()' One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.Omonline.OutsideIn.Discovery.DiscoveryRule Instance name: Global Service Monitor Instance ID: {298CB0DA-4453-EFD2-A7AC-C2E8F2F7100D} Management group: XYZ Management Group |
Thanks Lance