Jump to content
Dataton Forum
esambell

secActivate Error

Recommended Posts

We're having an issue where we're getting a secActivate error, which Watchout reports as a network error, but reviewing the communications between the production and display computer in Wireshark indicates that the network messages are being passed with out issues (at least on the basic TCP connection). Does anyone know what the secActivate command does and why it might throw an error? We've gone through all the typical troubleshooting steps, such as simplifying the network, changing between computer name and IP address display specifications and starting a new show files (error happens even on a blank show).

 

Thanks!

Watchout secActivate Screenshot.jpg

Share this post


Link to post
Share on other sites

It very much looks like a network issue and probably it is not WATCHPOINT generating the issue but the underlying Windows OS.

I found some hints on SSL on the web which does not make sense here, but you should check whether you only use one NIC on both the production side and the display computer. Are both computers running Windows 10? Have you been able to use the computer(s) with WATCHOUT before?

Is the firewall turned off on both ends? We have seen cases with Windows 10 where you'd need to turn the firewall on at first, then connect WATCHOUT (online) and tell the firewall that you want those ports to be open and then turn the firewall off again. It wouldn't work when the firewall was off right from the beginning.

 

Share this post


Link to post
Share on other sites

Thanks for the info. The production computer only has a single NIC, and we've tested the display computer with the second NIC disabled, but it didn't change the issue. Windows firewall is turned off at the service level, not just disabled, so it's unlikely that's the problem.

In the Wireshark traces I do see a multicast packet go out as soon as the secActivate command is sent, but the multicast packed doesn't show up in the traces on the display computer end. I suspect though that this is simply because the display software hasn't joined the multicast group.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×