Endpoint Management and Virtualization Trusted Advisors Community merge into SED TA Community

Hello all,
We've been seeing the following error in the NS log for quite some time, and haven't really worried much about it...but now it seems to be impacting functionality of one of our Workflows that manages collection memberships and causing them to fail.

Log File Name: F:\Program Files\Altiris\Notification Server\Logs\a.log
Priority: 1
Date: 8/23/2010 10:03:04 AM
Tick Count: -2098997328
Host Name: xxxxxxxxx
Process: w3wp.exe (18976)
Thread ID: 21768
Module: AltirisNativeHelper.dll
Source: Altiris.Agent.Unix.ComputersCollection.FindComputerSuspectedForDoubleEntry
Description: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

We do have the UNIX Agent installed and are using it to manage a few hundred UNIX boxes (inventory mostly, which admittedly we are not current on).  Not having any luck finding out what this "FindComputerSuspectedForDoubleEntry" error is all about, or even where it is coming from.  I suspect something to do with AD import (as we have some sort of app that integrates the UNIX systems into Active Directory), so maybe something is breaking from that...Has anyone else seen this or have any ideas? 

but it looks like a duplicate computer merge process, but for UNIX. Haven't seen it before, sorry. I know UNIX handles the duplicate names\guids a bit differently than Windows, but probably only Doug knows for sure.

https://kb.altiris.com/article.asp?article=32719&p=1

Point 22. If Unix Inventory is installed on the NS, you may consider running the sp_FindComputerSuspected for DoubleEntry. The attached stored procedure cleans up the stored procedure installed by unix inventory solution that is susceptible to deadlocks. Be sure to rename the existing stored procedure before running this query.

Nice find Jim...I guess it didn't turn up in my search since it has spaces in the "Suspected for DoubleEntry" part...I think that "fix" is still not all that great since it uses a lot of calls to the SQL LOWER() function which as I understand it shouldn't be necessary, since the Altiris DB should be case-insensitive.  From conversations I had with some NS engineering guys a while back, when you use functions on a column it loses the benefit of any indexes on that data (I think I have that right).  I updated it with the following and we have not seen the "DoubleEntry" errors in the last two days since making the change!

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO
ALTER PROCEDURE [dbo].[sp_FindComputerSuspectedForDoubleEntry]
@IPAddress nvarchar(32) = '',
@Name nvarchar(512) = '',

@Domain nvarchar(512) = ''

AS

SELECT distinct cr.Guid from vComputerResource cr

join Inv_AeX_AC_Identification acid on cr.Guid = acid._ResourceGuid

join Inv_AeX_AC_TCPIP tcp on cr.Guid = tcp._ResourceGuid

where [IP Address] = @IPAddress and

([IP Address] = Name and (isnull(Domain, N'') = '') or

(

[Name] = @Name AND

isnull([Domain], N'') = @Domain AND

(Name = @Name OR Domain=@Domain)

)

)

GO

SET ANSI_NULLS OFF

GO

SET QUOTED_IDENTIFIER OFF

GO