Nice Screen logging

[mikeyb123]

Hi All

Just a quick question about Nice secreen logging....

We are seeing this in the sams log files - anyone know what it means? As we are unable to record anyscreen

19/03/2013 08:52:26.408: Event: SA: <22.10.37.202:2102>, Report: <Online >, Message <CapControlHandler : PerformCaptureControlMaintanace Open new connection and Sent Registration to 10.52.208.30:201
0 on ChannelId 65536.>
19/03/2013 08:52:26.408: Bug: SA: <22.10.37.202:2102>, Report: <Online >, Message <IncCommandsHandler - CaptureSrvrCommPoint::HandleCmdRecieving: Channel(65536) recieved opcode(162) and extension !=
NULL. Going to delete it..>
19/03/2013 08:52:26.611: Fatal: SA: <22.10.37.202:2102>, Report: <Online >, Message <IncCommandsHandler - MMLChannel::HandleHeaderReceiving: Failed to handle the header reception on the MML channel
- Point=03D71548,ChannelId=0, RxTransactionId=4, MMSequence=1, Error=Failed to extract the relevant transaction from the waiting queue. Error Code(8)>19/03/2013 08:52:26.892: Fatal: SA: <22.10.37.202:2102>, Report: <Online >, Message <IncCommandsHandler - MMLChannel::HandleHeaderReceiving: CRC error in MMHeader. Going to Disconnect. Point=03D7154
8, ChannelId=0.>
19/03/2013 08:52:27.002: Fatal: SA: <22.10.37.202:2102>, Report: <Online >, Message <IncCommandsHandler - MMLChannel::HandleHeaderReceiving: Incomplete MM header recieved for channel(0), Bytes recei
ved (9). Msg will be ignored.. Error Code(7)>19/03/2013 08:52:31.392: Fatal: SA: <22.10.37.202:2102>, Report: <Online >, Message <CapControlHandler : SendKeepAlive Failed on ChannelId 65536.>
19/03/2013 08:53:26.409: Event: SA: <22.10.37.202:2102>, Report: <Online >, Message <CapControlHandler : PerformCaptureControlMaintanace Open new connection and Sent Registration to 10.52.208.30:201
0 on ChannelId 131072.>

It's not getting any smarter out there. You have to come to terms with stupidity, and make it work for you.

 

[nice12345]

hi what version of Perform is it?
have you consulted the troubleshooting doc on extranice.
Check RCM logs to ensure mapping is ok. Check local screen agent logs for as to why there is a disconnect. ensure all ports are open between interaction center screen logger and client.
you can also run the Screen ETA tool (enhanced test agent) this will provide more information. if its system wide then its more likely a configuration issue, check certified servers guide and workstation setup guides to ensure all is in place.check screen agent version and ensure latest UP packs are loaded