Errors in errorlog.txt with active scanning enabled

[gsvarney]

Hi,
I have upgraded to 3.5 and now when I start the service with active scanning enabled, I am seeing errors. First for the server itself I see:

3/11/2009 10:35:42 AM: <LS Server> String or binary data would be truncated.
The statement has been terminated.
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.sweeperthread.UpdateIP(clsComputer mycomputer, SqlConnection& sqlcon)

Followed by these. It ends after a total of 4 computers, including above:

3/11/2009 10:35:44 AM: <computer 1> String or binary data would be truncated.
The statement has been terminated.
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.sweeperthread.UpdateIP(clsComputer mycomputer, SqlConnection& sqlcon)

3/11/2009 10:36:05 AM: <computer 2> Critical error
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementPath.GetManagementPath(IWbemClassObjectFreeThreaded wbemObject)
at System.Management.ManagementObject.GetManagementObject(IWbemClassObjectFreeThreaded wbemObject, ManagementScope scope)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.get_Current()
at LansweeperService.MdlWmi.GetWMI(String Querystr, String Table, clsComputer& mycomputer, String section, SqlConnection& sqlcon)

I have seen other posts with the truncated error in validating the license key, but that went fine for me.

Thanks,
Geoff

[gsvarney]

Yes, as far as I can tell it's working. In fact, after leaving it alone for a few hours, it appears that I've actually gotten new audits done. However, there are several of these errors in the errorlog.txt, some truncated, some critical errors. I'm assuming the "remote procedure call failed" that I see would be computers that are offline. I do see a failure (String or binary data would be truncated) for a Vista 64 machine that I know was online. So I think I can ignore RPC errors in errorlog as far as looking for problems. These must be computers in AD that resolve, then can't be found, right?

I'm really liking the new features you've added and LS continues to be one of our most valuable network tools. Keep up the great work.

Thanks,
Geoff

[Hemoco]

gsvarney wrote:
Yes, as far as I can tell it's working. In fact, after leaving it alone for a few hours, it appears that I've actually gotten new audits done. However, there are several of these errors in the errorlog.txt, some truncated, some critical errors. I'm assuming the "remote procedure call failed" that I see would be computers that are offline. I do see a failure (String or binary data would be truncated) for a Vista 64 machine that I know was online. So I think I can ignore RPC errors in errorlog as far as looking for problems. These must be computers in AD that resolve, then can't be found, right?

I'm really liking the new features you've added and LS continues to be one of our most valuable network tools. Keep up the great work.

Thanks,
Geoff

I'm worried about the "String or binary data would be truncated." in UpdateIP because this just updates the computers IP address in table tblcomputers.

[Hemoco]

Is everything else working fine (except for these errors)
Are you using IPv4 or IPv6?