IT Monkey:    
Effective January 30, 2018 this app has been retired by Cireson. Cireson will no longer provide future feature updates, security patches, or support. However, the functionality you know and love has been enhanced and integrated into the new True Control Center.

To get the most of out of your System Center investment and to ensure compatibility with other software applications and systems, we recommend you take advantage of the True Control Center. Take it for a test drive in our online demo lab or request a free 30-day trial.

Received new Announcement, however this on is not targeted to tthis computer, ignoring

I am getting this message, basically, the computer is in a test collection and is not getting the announcements, this is happening to a few different PC's that are in the collection.

08/22/2016 11:25:53 AM COB\broberts : ------------ Initializing new instance of Cireson Ticker App --------------
08/22/2016 11:25:53 AM COB\broberts : ------------ ConfigMgr.TickerClient version 1.0.2016.5 --------------
08/22/2016 11:25:53 AM COB\broberts : WMI query will be performed every 30 seconds.
08/22/2016 11:25:53 AM COB\broberts : WMI query will also be performed whenever the CCM Notification Agent appends text to the log.
08/22/2016 11:25:53 AM COB\broberts : Start monitoring.
08/22/2016 11:26:23 AM COB\broberts : Checking if Announcement with ID 1c7d001f6e65f6cf1d17ec515 has been processed.
08/22/2016 11:26:23 AM COB\broberts : Checking if Announcement with ID 1c7d001f6e65f6cf1d17ec515 has been processed.
08/22/2016 11:26:23 AM COB\broberts : Announcement with ID 1c7d001f6e65f6cf1d17ec515 has not yet been processed.
08/22/2016 11:26:23 AM COB\broberts : Announcement with ID 1c7d001f6e65f6cf1d17ec515 has not yet been processed.
08/22/2016 11:26:23 AM COB\broberts : Received new Announcement, however this on is not targeted to this computer, ignoring
08/22/2016 11:26:23 AM COB\broberts : Received new Announcement, however this on is not targeted to this computer, ignoring
08/22/2016 11:27:23 AM COB\broberts : Checking if Announcement with ID 174408d8420607cf1d1290a62 has been processed.
08/22/2016 11:27:23 AM COB\broberts : Announcement with ID 174408d8420607cf1d1290a62 has not yet been processed.
08/22/2016 11:27:23 AM COB\broberts : Received new Announcement, however this on is not targeted to this computer, ignoring
08/22/2016 2:02:23 PM COB\broberts : Checking if Announcement with ID 12390840489758cf1d177c1b8 has been processed.
08/22/2016 2:02:23 PM COB\broberts : Announcement with ID 12390840489758cf1d177c1b8 has not yet been processed.
08/22/2016 2:02:23 PM COB\broberts : Received new Announcement, however this on is not targeted to this computer, ignoring
08/22/2016 2:13:14 PM COB\broberts : ------------ Initializing new instance of Cireson Ticker App --------------
08/22/2016 2:13:14 PM COB\broberts : ------------ ConfigMgr.TickerClient version 1.0.2016.5 --------------
08/22/2016 2:13:14 PM COB\broberts : WMI query will be performed every 30 seconds.
08/22/2016 2:13:14 PM COB\broberts : WMI query will also be performed whenever the CCM Notification Agent appends text to the log.
08/22/2016 2:13:14 PM COB\broberts : Start monitoring.
08/22/2016 2:13:44 PM COB\broberts : Checking if Announcement with ID 12390840489758cf1d177c1b8 has been processed.
08/22/2016 2:13:44 PM COB\broberts : Announcement with ID 12390840489758cf1d177c1b8 has not yet been processed.
08/22/2016 2:13:44 PM COB\broberts : Received new Announcement, however this on is not targeted to this computer, ignoring
08/22/2016 2:17:14 PM COB\broberts : Checking if Announcement with ID 129008495a2a78cf1d171ab13 has been processed.
08/22/2016 2:17:14 PM COB\broberts : Announcement with ID 129008495a2a78cf1d171ab13 has not yet been processed.
08/22/2016 2:17:14 PM COB\broberts : Received new Announcement, however this on is not targeted to this computer, ignoring
08/22/2016 2:22:14 PM COB\broberts : Checking if Announcement with ID 1e6a089d3e2388cf1d15caa14 has been processed.
08/22/2016 2:22:14 PM COB\broberts : Announcement with ID 1e6a089d3e2388cf1d15caa14 has not yet been processed.
08/22/2016 2:22:14 PM COB\broberts : Received new Announcement, however this on is not targeted to this computer, ignoring
08/22/2016 2:27:14 PM COB\broberts : Checking if Announcement with ID 13bf08e98bb598cf1d1370f16 has been processed.
08/22/2016 2:27:14 PM COB\broberts : Announcement with ID 13bf08e98bb598cf1d1370f16 has not yet been processed.
08/22/2016 2:27:14 PM COB\broberts : Received new Announcement, however this on is not targeted to this computer, ignoring

Best Answer

Answers

  • blroberts228blroberts228 Member IT Monkey ✭
    Here is the Cireson TickerAdmin.log
  • blroberts228blroberts228 Member IT Monkey ✭
    I'm still attempting to resolve this issue to no avail
  • james_kleinschnitzjames_kleinschnitz Cireson Dev, Product Owner Advanced IT Monkey ✭✭✭
    edited August 2016
    I have notified the Product Owner (who is at SCU) & the Developer about this thread.


  • F_ChristiansenF_Christiansen Cireson Dev Advanced IT Monkey ✭✭✭
    According to the Ticker Admin log, you post multiple announcements to the same collection just a few seconds after each other. please be noted that announcements are not queued, but will be overwritten by the latest.

    The Ticker Admin send an initial Client Notification request to ConfigMgr, record the ID of that Client Notification, stores that into the actual announcement data package and sends yet another Client Notification.

    When the Ticker Client receives an announcement, it looks for previously received Client Notification requests.
    If the announcements packages hold that Client Notification ID, the Ticker Client processes the announcement and display the banner or schedule the announcement for later.

    What I think happens in your case is that ConfigMgr either had too many similar Client Notification requests send too close to each other.

    Try waiting a few minutes between each announcement request to let ConfigMgr process the Client Notification requests and let them flow down to the client. Each request should be processed by the client within one minute.

    Please let us know if that make a difference.

    Best regards
    Flemming Appelon Christiansen
  • blroberts228blroberts228 Member IT Monkey ✭
    Thanks for the reply, I did try today after reinstalling both the admin and app softwares, on totally different machines. The log files say the same messages, that the computer is not part of the targeted collection, when in fact it is.
  • F_ChristiansenF_Christiansen Cireson Dev Advanced IT Monkey ✭✭✭
    Sorry to hear that it's still an issue. Could you please attach TickerAdmin.log and the Cireson TickerApp.log from a client and I'll see what I can do.
  • wally_meadwally_mead Member Advanced IT Monkey ✭✭✭
    This is the first time I've ever seen this being an issue. Sorry to hear that it is. I just demoed the Ticker app to the audience at SCU in Berlin this morning and it worked as expected (and usually at a conference when trying to demo to people is when a demo will usually fail if it is going to ever do so :-)

    I'm sure if you attach current logs for Flemming, he'll get you sorted out. Otherwise, if not, then next week when I'm back in the office, we can do a Skype session if you want to show me the process and we can see if we can figure out something together.
  • blroberts228blroberts228 Member IT Monkey ✭
    Thanks Wally and here are the logs.
  • F_ChristiansenF_Christiansen Cireson Dev Advanced IT Monkey ✭✭✭
    Hmm, still strange. Would you mind sending the CcmNotificationAgent.log from your client located in %windir%\CCM\Logs
  • blroberts228blroberts228 Member IT Monkey ✭
    Here you go.
  • blroberts228blroberts228 Member IT Monkey ✭
    In looking at that log, I believe it is linked to the notification service not being installed correctly, I'm birddogging this right now.
  • wally_meadwally_mead Member Advanced IT Monkey ✭✭✭
    Very happy that you got it working. Very interesting that it was an issue due to the ConfigMgr installation folder. That's very surprising, as I know the vast majority of people do install ConfigMgr on other drives than C:. If that really was the issue, I'd certainly raise a ticket with Microsoft support on it to get them to have the product group fix that. That would mean that none of the other Client Notification features would be working either, as that is what we're using.
  • wally_meadwally_mead Member Advanced IT Monkey ✭✭✭
    On further reading, you may be implying the client installation was on drive E instead of C, rather than the site installation (which is what I was thinking that you were implying). There certainly are people who install the client on drives other than C, but that is not as prevalent as is the site installation on a different drive.

    If it is a client installation issue, then I'd verify that it is affecting other clients that are installed on other drives, and those on drive C are fine. I'd still suggest opening a case with Microsoft support if you can validate/reproduce that scenario.
  • blroberts228blroberts228 Member IT Monkey ✭
    I was referring to the site installation. It is on the E: drive of my server, here is a link to what was happeneing.

    https://www.windows-noob.com/forums/topic/7401-sms-notification-server-failed-critical-sccm-sp1-sql-2012-sp1/

  • wally_meadwally_mead Member Advanced IT Monkey ✭✭✭
    Very interesting. I would assume, given that this article really references ConfigMgr 2012 SP1, that Microsoft has resolved this issue in Configuration Manager current branch. However, I had not even ever heard of the issue. I'd certainly open a case with MS, or use Connect to file a bug, to ensure that the product group is aware of the issue and has a fix for it instead of requiring that you all manually edits those files to get things working with your BGB Server component (which our Ticker app uses to send messages to clients).
This discussion has been closed.