Author Topic: Verint Impact 360 Screen Capture Blue Screen  (Read 1932 times)

Offline mikemcquaid

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Verint Impact 360 Screen Capture Blue Screen
« on: February 11, 2017, 02:34:51 AM »
Screen capture in admin portal only showing as blue screen, any ideas on a fix?

Offline sureshcitece

  • Jr. Member
  • **
  • Posts: 68
  • Karma: 0
Re: Verint Impact 360 Screen Capture Blue Screen
« Reply #1 on: February 11, 2017, 05:36:44 AM »
check if user machine has screen capture module service running. Don't remember the service name exactly as worked on it long time back.
Also check if extension and workstation mapping is proper or not. Will check the doc and post the right service name to be checked in user's workstation.

Offline n3vek7

  • Full Member
  • ***
  • Posts: 114
  • Karma: 3
    • ITKB
Re: Verint Impact 360 Screen Capture Blue Screen
« Reply #2 on: February 20, 2017, 03:57:22 AM »
version 10 or 11, look for ILALoginApp.exe and RFBAgent.exe to run.
Also, from the server running the screen acquisition module you can run a service a connect to the IP of the workstation.

Offline Ricky

  • Newbie
  • *
  • Posts: 17
  • Karma: 0
Re: Verint Impact 360 Screen Capture Blue Screen
« Reply #3 on: December 04, 2017, 03:39:08 PM »
I am also facing the same issue. Any suggestion ?


Offline n3vek7

  • Full Member
  • ***
  • Posts: 114
  • Karma: 3
    • ITKB
Re: Verint Impact 360 Screen Capture Blue Screen
« Reply #4 on: December 19, 2017, 04:09:59 AM »
I am also facing the same issue. Any suggestion ?

What version?
What have you tried so far?
Are screen capture services running on workstation?
Can you connect to the service from the screen capture server?

Offline CGB

  • Newbie
  • *
  • Posts: 13
  • Karma: 0
Re: Verint Impact 360 Screen Capture Blue Screen
« Reply #5 on: January 24, 2018, 07:43:09 AM »
I've faced that recently, it was a comms issue, some ports weren't opened on the firewalls. Check your udp ports for rtp traffic, 5060 upd and tcp, 29522 tcp and 4001 and 4002 tcp inbound way on the user machine.  Post your screen software logs (from the user machine)

Regards