Error log continues to grow

[Ingraham2]

Installed a clean install and went to the latest 3.5 service build.

The service errorlog.txt grows to over 50MB in a day.

When I try to access reports (ie SOFTWARE) for a PC no data is displayed. The errors for the PC are below.

These are the same errors in the log file for possible every PC it tries to contact.


Services Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated. 23/04/2009 7:37:51 AM
Network Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. 23/04/2009 7:36:54 AM

From Errolog.txt
23/04/2009 10:52:50 AM: SPW7516 Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at LansweeperService.MdlWmi.GetWMI(String Querystr, String Table, clsComputer& mycomputer, String section, SqlConnection& sqlcon)



Also: Why does the new version create a profile for the account used by the Lansweeper Service on every PC?

Thanks

[Hemoco]

Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

This means that the database server times out on these requests.
Make sure your hardware can follow or lower the amount of simultaneous scans.

Also:  Why does the new version create a profile for the account used by the Lansweeper Service on every PC?

The previous version used the remote registry service to access the registry, version 3.5 also uses wmi for this.
The advantage is that you don't need the service dependency anymore, the disadvantage is that it creates a profile the first time it's scanned.