SELECT * FROM SMS_CM_RES_COLL_C90100019 where (ClientType is NULL and EASDeviceID in NULL) OR ClientType != 3
I think that's a typo (EASDviceID in NULL) I know that would never work.
anyway, in smsprov.log,
when you see that for Execute WQL = that line
the very next line will be the Execute SQL =
Take that, and execute that in sql, against your (I'm guessing) cm_C90 database? because the coll_c90100019 in your select statement.. which, hm... c90100019 looks like too make characters for a collectionid. I'm guessing you fudged that for privacy? otherwise that's a problem, too.
maybe try (from your CAS)
select * from v_fullcollectionmembership where collectionid = 'C90100019' (or whatever that collectionid really is) is there anything in that collection?
From: Mark Mears <[email protected]>
To: "[email protected]" <[email protected]>
Sent: Wednesday, October 23, 2013 9:39 AM
Subject: [mssms] RE: Collection Views not populating from CAS
Bump.
|
Thanks,
|
|
|
Mark Mears
Phone: (757) 945-2651
|
 |
|
|
|
|
|
|
From: [email protected] [mailto:[email protected]]
On Behalf Of Mark Mears
Sent: Tuesday, October 22, 2013 12:16 PM
To: [email protected]
Subject: [mssms] Collection Views not populating from CAS
Sent: Tuesday, October 22, 2013 12:16 PM
To: [email protected]
Subject: [mssms] Collection Views not populating from CAS
My customer has a CAS and three Primary sites below the CAS. We have defined several collections from the CAS and have run AD System Discovery from the Primary site (since it does not exist on the CAS) without seeing these collections
being able to display the members of the collections using the “Show Members” functionality. The correct number of clients is displayed in the console but when “Show Members” is selected nothing is returned, looking like the collection is empty. Backing
up to the parent item displays the correct member count.
Further poking around in the SMSProv.LOG indicates that the SQL query being used to populate the collection is:
SELECT * FROM SMS_CM_RES_COLL_C90100019 where (ClientType is NULL and EASDeviceID in NULL) OR ClientType != 3
When I do a normal select on the view above it returns zero rows. Since the console is based on these collection memberships to populate the console collections, returning zero rows effectively shows a “No items found” message for the
collection.
The creation of new collections has been tried and new collections show the same thing. How do the collection views get generated or refreshed? I understand that collection rules and memberships are sent to lower sub-sites using the SQL
Broker service but don’t know where it goes from there.
This same condition exists in all 3 primaries. Looking at the same collection on the Primary site shows the expected results, the proper count and the “Show Members” functionality works.
Has anyone seen this before and how can I get this corrected?
|
Thanks,
|
|
|
Mark Mears
Phone: (757) 945-2651
|
|
|
|
|
|
|
|
