Since 9.3.10.7 (High CPU, Memory and Scanning issue)

[JFK_WEB]

Anybody else gets some issue with new version 9.3.10.7 ?
Scanning not work anymore, computer stay stuck in the Windows computer scanning.
CPU always nears 80-90 % and Memory to 10 Gb.
Database has been optimized from 19 Gb to 4.4 Gb after reducing event log retention.
We have a lot of "1 scanning takes longer than 1 hour, repair wmi on this machine!" but all this machine was OK before.
Any else ?

[Bruce_B · Accepted solution]

We're investigating reports that querying Win32_SystemDrivers can cause a performance impact on the scanning server and the scanned system in some circumstances. If you're experiencing a performance issue on your Lansweeper server, try doing the following:

• Go to Scanning\Scanned Item Interval
  
• Disable the SYSTEMDRIVERS item
  
• Clear the scanning queue via Scanning\Scanning Queue
  
• Restart the Lansweeper Server service to sever any ongoing connections
  

In regards to LsAgent relay connections, there is no known issue with the relay server. Keep in mind that the scanning service checks into the relay to pull assets every hour. If you're seeing an error every hour you may indeed have a connection issue in which case I recommend checking out this article. If you're only seeing error intermittently, this isn't a cause for concern.

[JFK_WEB]

Bruce.B wrote:
We're investigating reports that querying Win32_SystemDrivers can cause a performance impact on the scanning server and the scanned system in some circumstances. If you're experiencing a performance issue on your Lansweeper server, try doing the following:

• Go to Scanning\Scanned Item Interval
  
• Disable the SYSTEMDRIVERS item
  
• Clear the scanning queue via Scanning\Scanning Queue
  
• Restart the Lansweeper Server service to sever any ongoing connections
  

In regards to LsAgent relay connections, there is no known issue with the relay server. Keep in mind that the scanning service checks into the relay to pull assets every hour. If you're seeing an error every hour you may indeed have a connection issue in which case I recommend checking out this article. If you're only seeing error intermittently, this isn't a cause for concern.

Does the new version 9.4.0.8 fix the problem ?

Fixed: LAN-12578 Incorrect saving of data in the tblSystemDriverPnpEntity and tblPrinterDriverDevice database tables used for linking system drivers and PnP drivers, printers and printer drivers

[JFK_WEB]

Bruce.B wrote:
We're investigating reports that querying Win32_SystemDrivers can cause a performance impact on the scanning server and the scanned system in some circumstances. If you're experiencing a performance issue on your Lansweeper server, try doing the following:

• Go to Scanning\Scanned Item Interval
  
• Disable the SYSTEMDRIVERS item
  
• Clear the scanning queue via Scanning\Scanning Queue
  
• Restart the Lansweeper Server service to sever any ongoing connections
  

In regards to LsAgent relay connections, there is no known issue with the relay server. Keep in mind that the scanning service checks into the relay to pull assets every hour. If you're seeing an error every hour you may indeed have a connection issue in which case I recommend checking out this article. If you're only seeing error intermittently, this isn't a cause for concern.

Exactly what I did at first. Working well since I disable it.

Thanks for the confirmation Bruce

[Notonyourradar]

Same with the CPU / Memory. Is anyone also having issues with Cloud relay agents reporting in?

[abetzold]

Notonyourradar wrote:
Same with the CPU / Memory. Is anyone also having issues with Cloud relay agents reporting in?

Yes, this too is in my logs.

[JFK_WEB]

I don't have any error message in the log related to drivers itself. I only got extremely slow scanning and CPU and memory max out.

[abetzold]

JFK wrote:
Anybody else gets some issue with new version 9.3.10.7 ?
Scanning not work anymore, computer stay stuck in the Windows computer scanning.
CPU always nears 80-90 % and Memory to 10 Gb.
Database has been optimized from 19 Gb to 4.4 Gb after reducing event log retention.
We have a lot of "1 scanning takes longer than 1 hour, repair wmi on this machine!" but all this machine was OK before.
Any else ?

I found the webex document loader to be the problematic driver.

[abetzold]

I have been having issues and finally found the bug in the error logs. Yes it has to do with driver scanning:

SqlException Errors:
-> Number 242: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.
Following properties may have cause the implications:
- Property: "DriverDate", Type: Nullable<DateTime>, Value: "01/01/1601 00:00:00"
- Property: "LastChanged", Type: DateTime, Value: "01/01/0001 00:00:00"
---> System.Data.Entity.Infrastructure.DbUpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.Entity.Core.UpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.SqlClient.SqlException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.
The statement has been terminated.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target, Func`3 operation, TInterceptionContext interceptionContext, Action`3 executing, Action`3 executed)
at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command, DbCommandInterceptionContext interceptionContext)
at System.Data.Entity.Core.Mapping.Update.Internal.DynamicUpdateCommand.Execute(Dictionary`2 identifierValues, List`1 generatedValues)
at System.Data.Entity.Core.Mapping.Update.Internal.UpdateTranslator.Update()
--- End of inner exception stack trace ---
at System.Data.Entity.Core.Mapping.Update.Internal.UpdateTranslator.Update()
at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction(Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)
at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesToStore(SaveOptions options, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction)
at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesInternal(SaveOptions options, Boolean executeInExistingTransaction)
at System.Data.Entity.Internal.InternalContext.SaveChanges()
--- End of inner exception stack trace ---
at System.Data.Entity.Internal.InternalContext.SaveChanges()
at Lansweeper.EF.Toolkit.DbContextBase`1.SaveChanges()
--- End of inner exception stack trace ---
at Lansweeper.EF.Toolkit.DbContextBase`1.SaveChanges()
at Lansweeper.EF.Toolkit.GenericRepository`1.AddRange(IEnumerable`1 entity, IDbContext context)
at Lansweeper.Service.BL.DriverScanning.DriverScanningManager.SavePrinterDrivers(IList`1 printerDrivers, IDbContext dbContext)
2022-03-24 08:28:27,118 [43] ERROR SavePrinterDrivers: Error occurred saving printer drivers.
System.Data.Entity.Infrastructure.DbUpdateException: Entity of type "PrinterDriver" in state "Added" has caused a DbUpdateException.

So I have a printer driver out there and the developer didn't put a date in so 1601 is returned and is crashing during the table update for every device with this driver.

[abetzold]

abetzold wrote:
I have been having issues and finally found the bug in the error logs. Yes it has to do with driver scanning:

SqlException Errors:
-> Number 242: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.
Following properties may have cause the implications:
- Property: "DriverDate", Type: Nullable<DateTime>, Value: "01/01/1601 00:00:00"
- Property: "LastChanged", Type: DateTime, Value: "01/01/0001 00:00:00"
---> System.Data.Entity.Infrastructure.DbUpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.Entity.Core.UpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.SqlClient.SqlException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.
The statement has been terminated.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target, Func`3 operation, TInterceptionContext interceptionContext, Action`3 executing, Action`3 executed)
at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command, DbCommandInterceptionContext interceptionContext)
at System.Data.Entity.Core.Mapping.Update.Internal.DynamicUpdateCommand.Execute(Dictionary`2 identifierValues, List`1 generatedValues)
at System.Data.Entity.Core.Mapping.Update.Internal.UpdateTranslator.Update()
--- End of inner exception stack trace ---
at System.Data.Entity.Core.Mapping.Update.Internal.UpdateTranslator.Update()
at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction(Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)
at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesToStore(SaveOptions options, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction)
at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesInternal(SaveOptions options, Boolean executeInExistingTransaction)
at System.Data.Entity.Internal.InternalContext.SaveChanges()
--- End of inner exception stack trace ---
at System.Data.Entity.Internal.InternalContext.SaveChanges()
at Lansweeper.EF.Toolkit.DbContextBase`1.SaveChanges()
--- End of inner exception stack trace ---
at Lansweeper.EF.Toolkit.DbContextBase`1.SaveChanges()
at Lansweeper.EF.Toolkit.GenericRepository`1.AddRange(IEnumerable`1 entity, IDbContext context)
at Lansweeper.Service.BL.DriverScanning.DriverScanningManager.SavePrinterDrivers(IList`1 printerDrivers, IDbContext dbContext)
2022-03-24 08:28:27,118 [43] ERROR SavePrinterDrivers: Error occurred saving printer drivers.
System.Data.Entity.Infrastructure.DbUpdateException: Entity of type "PrinterDriver" in state "Added" has caused a DbUpdateException.

So I have a printer driver out there and the developer didn't put a date in so 1601 is returned and is crashing during the table update for every device with this driver.

I have disabled printerdriver scanning in my deployment and restarted my scanning. Once LS assigns a bug here and notifies me of the fix, I'll then re-enable this highly desirable feature.