Home› Configuration Manager Ticker
Options

CM Ticker App Timeout Issue

Thomas_HolzerThomas_Holzer Partner IT Monkey ✭
in Configuration Manager Ticker
Hi everyone,

I installed Config Mgr Ticker app in our environment.
But while generating a new announcement for a Collection a timeout occurs after one minute:


I tried to create announcement on our Primary Site Server (we have no CAS) and with "Full Admin" Rights.

The CM-collection currently has just one member.
Here are the recent contents of the CiresonTickerAdmin.log:

2017-07-11 11:03 contoso\001151489 : ------------ Initializing new instance of Cireson Ticker App --------------
2017-07-11 11:03 contoso\001151489 : ------------ Cireson.TickerAdmin version 1.2.1608.9 --------------
2017-07-11 11:03 contoso\001151489 : ------------ Hosted by System Center Configuration Manager version 5.1702.1035.1002 --------------
2017-07-11 11:03 contoso\001151489 : ------------ Connected to Site PS1 --------------
2017-07-11 11:03 contoso\001151489 : Found custom severity 'Information'. Adding to list
2017-07-11 11:03 contoso\001151489 : Found custom severity 'Warning'. Adding to list
2017-07-11 11:03 contoso\001151489 : Found custom severity 'Critical'. Adding to list
2017-07-11 11:03 contoso\001151489 : Loading color scheme ''.
2017-07-11 11:03 contoso\001151489 : Loading posted announcements. Expired announcements are excluded
2017-07-11 11:03 contoso\001151489 : Previewing announcement
2017-07-11 11:03 contoso\001151489 : Preparing to post announcement.
2017-07-11 11:03 contoso\001151489 : Checking if current user has permissions to initialize client notification for collection 'Test Cireson Ticker App'.
2017-07-11 11:03 contoso\001151489 : Current user has permission to initiate client notification, proceeding.
2017-07-11 11:03 contoso\001151489 : Initiating Client Notification actiontype 8 for collection 'Test Cireson Ticker App'
2017-07-11 11:03 contoso\001151489 : Client Notification method returned operationID 16778658
2017-07-11 11:03 contoso\001151489 : Getting TaskID for currently processed Client Notification.
2017-07-11 11:03 contoso\001151489 : Returned TaskID {7b3ae6b4-bdf2-4b23-93ec-31625b42e0c6}
2017-07-11 11:03 contoso\001151489 : Checking if Inventory Class 'Cireson_Ticker' exists.
2017-07-11 11:03 contoso\001151489 : Inventory Class 'Cireson_Ticker' exist. Setting Announcement details.
2017-07-11 11:03 contoso\001151489 : Altering inventory configuration to hold the Announcement.
2017-07-11 11:03 contoso\001151489 : Mof data retrieved. 874 characters imported
2017-07-11 11:03 contoso\001151489 : Connecting to namespace '\\WIN0011106\root\sms\site_PS1'.
2017-07-11 11:03 contoso\001151489 : Successfully connected to namespace '\\WIN0011106\root\sms\site_PS1'.
2017-07-11 11:03 contoso\001151489 : Importing Mof data into ConfigMgr.
2017-07-11 11:03 contoso\001151489 : Mof data imported into ConfigMgr. The action returned success
2017-07-11 11:03 contoso\001151489 : Committing WMI class data to inventory configuration.
2017-07-11 11:03 contoso\001151489 : Hardware Inventory configuration data committed.
2017-07-11 11:03 contoso\001151489 : Waiting for Policy Provider to complete processing. Max wait time is 60 seconds.


Any ideas what I can try?
Thanks in advance!!

BR Thomas

Comments

  • Options
    Thomas_HolzerThomas_Holzer Partner IT Monkey ✭
    Does anyone have any ideas, still have these troubles with the Ticker App.

    Thanks in advance for any posts!!
  • Options
    wally_meadwally_mead Member Advanced IT Monkey ✭✭✭
    Does it eventually get posted? I know normally it does, and it is just an issue with the site server being busy, and thus Policy Provider not completing in the timeframe we're monitoring. If it doesn't complete in time, we don't stop it, and it usually then posts later when Policy Provider does respond.

    There is a Registry key that you can change to control the time we wait for Policy Provider. It is:
    HKLM\Software\Wow6432Node\Cireson\ConfigMgr Apps\Ticker App\Max Policy Wait Time

    You can set it to a higher number of seconds to see if Policy Provider responds in time then. If not, then check the policypv.log on the site server to see if it reports any issues when you create an announcement.
This discussion has been closed.