LsAgent not sending AssetID?

[sgoff]

I've run into an issue getting new LsAgent scans to show up on our server. It picks up scans for already existing assets, but not for new ones.

The client logs say the scans are sending fine, but the server never receives them. The server log says this:

2020-09-24 09:35:50,972 [271] INFO WORKGROUP\[AssetName]\1: Could not retrieve AssetID from Assetunique
2020-09-24 09:35:51,003 [271] WARN ProcessScanXml: AssetId is not filled in.

Then some time later, this:

2020-09-24 11:36:25,735 [250] ERROR could not sync asset scans from Relay
System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at https://lsagentrelay.lansweeper.com/EchoConfigurationService.svc?wsdl 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 server returned an error: (404) Not Found.
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.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
at System.ServiceModel.Channels.HttpChannelFactory`1.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 Lansweeper.Service.SA.Connected_Services.EchoConfigurationServiceReference.IEchoConfigurationService.DeleteAssetScanData(Guid relayKey, List`1 assetDataIds)
at Lansweeper.Service.SA.Connected_Services.EchoConfigurationServiceReference.EchoConfigurationServiceClient.DeleteAssetScanData(Guid relayKey, List`1 assetDataIds)
at Lansweeper.Service.SA.EchoConfigurationServiceAgent.DeleteAssetScanData(Guid relayKey, List`1 assetDataIds)
at Lansweeper.Service.BL.ScanFileManager.ProcessScans(Guid relayKey, Boolean aboveAssetLimit, Func`4 saveScan)

Has anyone else seen this before? I have a ticket in with support, but they seem to be swamped and I haven't heard back. These laptops are a high-priority project and I need to get them deployed asap.

[djboge]

I thought that that would just exclude local scanning of that range, but not stop an agent from sending it's scan down too. Strange the way that's setup, but many thanks for the fix!

I just stumbled upon this thread and was experiencing a similar problem. I have LsAgent running on all my PCs, and they were happily sending scan results to the scan server (no relay or anything) but the assets weren't showing up or being updated.

In the log I saw:

LSpush skipping MACHINENAME, 172.26.39.99, excluded by IP: 172.26.32.1-172.26.39.254

Sure enough, I had that IP range excluded from scanning, but that shouldn't prevent the agents from pushing scan results, only the scan servers from scanning them via IP.

[user123445]

Hi,

I'm seeing this problem too. Has anyone found a fix? The ini file on the server has a an asset ID, yet the Scanning server complains that there is no asset ID
2022-02-18 08:14:44,017 [52] INFO WORKGROUP\SERVERX\1: Could not retrieve AssetID from Assetunique
2022-02-18 08:14:44,017 [52] WARN ProcessScanXml: AssetId is not filled in.

On the server it was not attempting to connect to the relay:
2022-02-18 09:34:37,767 [7] WARN Connection to Relay is skipped because no AgentKey is present

Restarted Lansweeper Agent Service on Server, then it connects to relay, but no scan is sent and no asset comes into Lansweeper.

2022-02-18 09:41:36,548 [7] DEBUG Created RelayCommunicationSender to URL https://lsagentrelay.lansweeper.com/EchoService.svc
2022-02-18 09:41:36,549 [7] DEBUG Getting asset status
2022-02-18 09:41:36,577 [7] DEBUG Attach ServerCertificateValidationCallback
2022-02-18 09:41:36,603 [7] DEBUG CreateFactoryInstance for endpoint https://lsagentrelay.lansweeper.com/EchoService.svc, EchoService
2022-02-18 09:41:37,237 [7] DEBUG ServicePointManager.ServerCertificateValidationCallback
2022-02-18 09:41:37,559 [7] DEBUG Asset is enabled
2022-02-18 09:41:37,561 [7] DEBUG Retrieving configuration
2022-02-18 09:41:38,824 [7] DEBUG Updating local config
2022-02-18 09:41:38,830 [7] DEBUG Checking version. Latest Version: 9.1.0.8. Current Version: 9.1.0.8
2022-02-18 09:41:38,831 [7] DEBUG Waiting for schedule...
2022-02-18 09:41:38,842 [7] DEBUG Saving ini settings
2022-02-18 09:41:38,849 [7] DEBUG Creating ini backup.
2022-02-18 09:41:38,856 [7] DEBUG Waiting 60 minutes until next iteration


@RayPamps23 - Perhaps a re-install (of the latest version) of lsagent would work, but this is not a feasible workaround as i'm seeing this error in errorlog.txt on the scan server for quite a few servers. I would rather understand what the root cause is...

Sarah Goff wrote:
I've run into an issue getting new LsAgent scans to show up on our server. It picks up scans for already existing assets, but not for new ones.

The client logs say the scans are sending fine, but the server never receives them. The server log says this:

2020-09-24 09:35:50,972 [271] INFO WORKGROUP\[AssetName]\1: Could not retrieve AssetID from Assetunique
2020-09-24 09:35:51,003 [271] WARN ProcessScanXml: AssetId is not filled in.

Then some time later, this:

2020-09-24 11:36:25,735 [250] ERROR could not sync asset scans from Relay
System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at https://lsagentrelay.lansweeper.com/EchoConfigurationService.svc?wsdl 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 server returned an error: (404) Not Found.
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.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
at System.ServiceModel.Channels.HttpChannelFactory`1.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 Lansweeper.Service.SA.Connected_Services.EchoConfigurationServiceReference.IEchoConfigurationService.DeleteAssetScanData(Guid relayKey, List`1 assetDataIds)
at Lansweeper.Service.SA.Connected_Services.EchoConfigurationServiceReference.EchoConfigurationServiceClient.DeleteAssetScanData(Guid relayKey, List`1 assetDataIds)
at Lansweeper.Service.SA.EchoConfigurationServiceAgent.DeleteAssetScanData(Guid relayKey, List`1 assetDataIds)
at Lansweeper.Service.BL.ScanFileManager.ProcessScans(Guid relayKey, Boolean aboveAssetLimit, Func`4 saveScan)

Has anyone else seen this before? I have a ticket in with support, but they seem to be swamped and I haven't heard back. These laptops are a high-priority project and I need to get them deployed asap.

[sgoff]

For me, it turned out to be that the devices were on an IP range that was set as a scanning exception, so it wouldn't pick them up, even with the agent installed.

Have you put in a support ticket?

[user123445]

Hey Sarah,

That's great! looks like that was what it was all along. Even though the IP ranges I was excluding were on a different scanning server, I thought that that would just exclude local scanning of that range, but not stop an agent from sending it's scan down too. Strange the way that's setup, but many thanks for the fix!

The bigger issue I have that's effecting more machines is the TLS 1.2 error in the logs (TLS is not the issue as I've checked versions etc) and agents not checking in. I've logged a support ticket too.

https://www.lansweeper.com/forum/yaf_postst17203_lsagent-not-scanning-sending-when-using-relay.aspx
https://www.lansweeper.com/forum/yaf_postst20820_LSAGENT-Error-TLS-1-2-with-cloud-relay.aspx

Sarah Goff wrote:
For me, it turned out to be that the devices were on an IP range that was set as a scanning exception, so it wouldn't pick them up, even with the agent installed.

Have you put in a support ticket?

[RayPamps23]

have you tried to reinstall the LsAgent and make sure to double-check the Cloud Relay Authentication Key is what you input in LsAgent during installation

on my end, I use 'Deployment' and created a new package when I want to install LsAgent to my endpoints. so far no issues when installing with that method.