Looks a little bit, based on the names (??) that you have some collection 
queries that are using, in it's mind anyway, columns that don't exist.
You *could* check in sql mgmt. studio, connect to your cm_xxx database looking 
for something like this:select c.collectionid, c.name, crq.queryexpression, 
crq.rulenamefrom v_collectionrulequery crqjoin v_collection c on 
c.collectionid=crq.collectionidwhere crq.queryexpression like 
'%Resource_Domain_OR_Workgr0%'
If I've guessed correctly, that will show you exactly which collection(s) and 
which collection rule names in those collections have a crazy collection query. 
 You'll have to decide then whether to delete those collection, recreate them, 
fix them, whatever the right answer is for that (or those) collections.




 


     On Thursday, August 20, 2015 2:25 PM, "[email protected]" 
<[email protected]> wrote:
   

 I have a influx of messages on the SMS_Collection_Evaluator  Message ID 620   
Microsoft SQL Server reported SQL message 207, severity 16: 
[42S22][207][Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 
'Client0'.
Microsoft SQL Server reported SQL message 207, severity 16: 
[42S22][207][Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 
'Name0'. 
Microsoft SQL Server reported SQL message 207, severity 16: 
[42S22][207][Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 
'Resource_Domain_OR_Workgr0'.  
Does anyone have any experience resolving these messages.
Thanks
Stefanie




  


Reply via email to