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.

Error message: Ungültiges Fensterhandle means "Invalid window handle"

A client doesn't show the banner, so I look in the 'Cireson TickerApp.log':
26.06.2017 17:01:13 DOM\hoda : Hiding ticker banner.
26.06.2017 17:01:13 DOM\hoda : Marking Announcement as processed.
26.06.2017 17:01:13 DOM\hoda : Error: Error enumerating Announcements.
26.06.2017 17:01:13 DOM\hoda : Error message: Ungültiges Fensterhandle

Do you know this error, a reason or a solution?

Answers

  • F_ChristiansenF_Christiansen Cireson Dev Advanced IT Monkey ✭✭✭
    Hi Daniel,

    I have seen that before and it seems like a timing issue.
    In the log, at 16:39:42 it first shows the ticker, then tries to display it again.
    This is where the "fun" starts, but not sure if this is the cause throughout the rest.
    It does try to hide the banner on several occasions, but if the banner is not displaying, it will get the invalid window handle error, since there is no banner (window) to hide.

    Do you see this on a single client only?
    Is it a normal Windows client? 
    Could the computer have been locked?

    Best regards
    Flemming Appelon Christiansen
  • Daniel_HoenigDaniel_Hoenig Member IT Monkey ✭
    Hi Flemming,

    yes, that client was the only one. It is a "normal" Windows7-Client, but it is that one, with the narrator software. But before there was no error with showing the banner.  Connecting to the locked-question I had to say that a domain user test account of me was locked in. There was no screensaver lock or so in the testing time.  

    Best regards,
    Daniel
This discussion has been closed.