Updated LsAgent failing The remote server returned an error: (500)

[kjstech]

Hello,

Was cleaning up some servers we have on DMZ or not on domain that use the LsAgent. These haven't been updating in our patch Tuesday reports for some time. Discovered there is a new LsAgent version so I installed that.

I have LsAgent 7.2.110.18 installed and in the log file its still failing connection.

Here is the excerpt from the failure in the log:
DEBUG Created RelayCommunicationSender to URL https://lsagentrelay.lansweeper.com/EchoService.svc
2020-11-10 11:42:21,832 [7] DEBUG Attach ServerCertificateValidationCallback
2020-11-10 11:42:21,834 [7] DEBUG CreateFactoryInstance for endpoint https://lsagentrelay.lansweeper.com/EchoService.svc, EchoService
2020-11-10 11:42:21,923 [7] DEBUG ServicePointManager.ServerCertificateValidationCallback
2020-11-10 11:46:11,957 [7] ERROR A communication error occurred.
System.ServiceModel.ProtocolException: An HTTP Content-Type header is required for SOAP messaging and none was found. ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
--- End of inner exception stack trace ---

Server stack trace:
at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory, WebException responseException, ChannelBinding channelBinding)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Dispatcher.RequestChannelBinder.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 Lansweeper.Echo.Server.IService.IEchoService.GetAssetStatus(Guid agentKey, Guid assetId)
at Lansweeper.Echo.Client.SA.AssetServiceAgent..(IEchoService )
at Lansweeper.Echo.Client.SA.Wcf.WcfServiceInvoker.InvokeService[T,R](Func`2 invokeHandler)
at Lansweeper.Echo.Client.SA.AssetServiceAgent.GetAssetStatus(Guid agentKey, Guid assetId)
at Lansweeper.Echo.Client.SA.RelayCommunicationSender.GetAssetStatus()
at Lansweeper.Echo.Client.BL.ScanningManager.ExecuteScan(IAppSettingsClient appSettings, EchoIniInfo iniSettings, IIniFileManager iniFileManager)
at Lansweeper.Echo.Client.WindowsService.ServiceStart.StartCore()


If I visit the server that is listed in the log file at https://lsagentrelay.lansweeper.com/EchoService.svc, I get a Windows Communication Foundation Service IIS page. No security errors, looks like the cert is good until 6/2/2021.

Any ideas?

[Notonyourradar]

I'm also seeing clients throwing errors, but then a scan will suddenly be successful later. Is something wrong with the relay service?

2020-11-13 10:14:33,333 [7] DEBUG Created RelayCommunicationSender to URL https://lsagentrelay.lansweeper.com/EchoService.svc
2020-11-13 10:14:33,458 [7] DEBUG ServicePointManager.ServerCertificateValidationCallback
2020-11-13 10:15:35,271 [7] DEBUG Asset is enabled.
2020-11-13 10:15:35,271 [7] DEBUG Retrieving configuration...
2020-11-13 10:19:35,391 [7] ERROR A communication error occurred.
System.ServiceModel.ProtocolException: The remote server returned an unexpected response: (502) Bad Gateway. ---> System.Net.WebException: The remote server returned an error: (502) Bad Gateway.
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory, WebException responseException, ChannelBinding channelBinding)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Dispatcher.RequestChannelBinder.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 Lansweeper.Echo.Server.IService.IEchoService.GetAssetGroupConfig(Guid agentKey, Guid assetId, OperatingSystemFamily operatingSystem)
at Lansweeper.Echo.Client.SA.AssetServiceAgent..(IEchoService )
at Lansweeper.Echo.Client.SA.Wcf.WcfServiceInvoker.InvokeService[T,R](Func`2 invokeHandler)
at Lansweeper.Echo.Client.SA.RelayCommunicationSender.GetConfigFile()
at Lansweeper.Echo.Client.BL.ScanningManager.ExecuteScan(IAppSettingsClient appSettings, EchoIniInfo iniSettings, IIniFileManager iniFileManager)
at Lansweeper.Echo.Client.WindowsService.ServiceStart.StartCore()

[kjstech]

After some time, this cleared itself with no further intervention from me.

[majinsgudy]

kjstech wrote:
After some time, this cleared itself with no further intervention from me.

Hi, How are you?

Do you remember how much time to cleared itself? And after cleared did work fine?

I'm having the same problem in some PCs and others PCs in the same room behind the same FW are working.