O R G A N I C / F E R T I L I Z E R: sms: sms collection evaluator message id 620

May 22, 2007

sms: sms collection evaluator message id 620

if you find these populating your collection evaluator status messages, it's probably because of a mismatch in your query somewhere. here's a sample status message:
Microsoft SQL Server reported SQL message 245, severity 16: [22018][245][Microsoft][ODBC SQL Server Driver][SQL Server]Conversion failed when converting the varchar value 'myMachineName' to data type int.
doesn't really give you much to go on. to get more details, open up colleval.log. the easiest way to spot where to pinpoint the problem is to look by the date/time in the status message. look for that... or something close to that in your logs. in the log file, the error message shows up. it looks like this:
*** [22018][245][Microsoft][ODBC SQL Server Driver][SQL Server]Conversion failed when converting the varchar value 'myMachineName' to data type int.
following pretty closely, you'll see another line that might look something like this:
Could not refresh collection XYZ00012. Will retry later.
now we're getting somewhere. now we have a collection id that we can go interrogate to see what it is in the query that's quite possibly not right. in my case, extremely possible. :)just as a fyi, looking into the collection, it was discovered that in a subselect query, resource id was being used to check a list of values where system name was being used. since resource id and system name are different data types (varchar and int), the comparisons would fail.