cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
RAFF37817
Engaged Sweeper
Hi,

We have just installed LanSweeper in our production environment and I am monitoring the LanSweeper error log.

I have noted some error messages and would like to better understand what they mean.


Here are some of the messages:


ERROR 1:
5/20/2009 4:45:31 PM: MACHINE 2 Transaction (Process ID 75) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

ERROR 2:
5/21/2009 1:50:47 AM: MACHINE1 Out of memory


Any information on these errors is greatly appreciated.

Thanks,
Raf
7 REPLIES 7
Hemoco
Lansweeper Alumni
Did you lower the amount of threads?
Lansweeper wrote:
Did you lower the amount of threads?


Yes from 35 down to 25. The issue still persists but it is not as frequent.
RAFF37817
Engaged Sweeper
After letting the service run all weekend, we are still seeing these SQL errors.

I will followup with our SQL team and see if they have any idea why this may be happening.

If anyone else has encountered this any know of a root cause - please add to this thread.

Thanks!
RAFF37817
Engaged Sweeper
We are running SQL Server 2005 on Windows Server 2003 SP2

Microsoft SQL Server Management Studio 9.00.4035.00
Microsoft Analysis Services Client Tools 2005.090.4035.00
Microsoft Data Access Components (MDAC) 2000.086.3959.00 (srv03_sp2_rtm.070216-1710)
Microsoft MSXML 2.6 3.0 4.0 6.0
Microsoft Internet Explorer 6.0.3790.3959
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790


I will lower the concurrent threads to see if this helps (from 35 to 25).
Hemoco
Lansweeper Alumni
The error seems to be related to SQL server and not to the scanning process.
Which version/service pack of SQL are you using?
RAFF37817
Engaged Sweeper
Both Machines are Windows XP with SP2 which is our current standard OS. Currently we have dozens of machines showing this in the error log (out of 5000+ machines).


We have a fresh new install of 3.5.1.

Here is a full example of the error:

5/21/2009 12:00:05 PM: Machine1 Transaction (Process ID 75) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.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, LS_Computer& mycomputer, String section, SqlConnection& sqlcon)
Hemoco
Lansweeper Alumni
As far as I can find both errors were never reported before.

Which OS/service pack are both machines running?
How many machines are affected by this?
Are you running 3.5.1?