Has anyone gotten the following error in the conductor.err file:
Error: Host Communications - Invalid Message Identifier Error (ID: M_CONFIGURE_PLAYER_RSP)
What seem to be happening is that the conductor freezes while it is trying to synchronizing the users.
I am running 14 player machines plus a conductor.
It appears that if a drop a random player machine the conductor does not hang...
I have been working with support for 3 days making little progress..except proving that I can recreate the issue going to google taking the application out of the
I can swap in and out different players and same result happens elliminating the players as the issue.
I am on 5.9 websync 4 ...
as an asside I just upgraded from websync 2 to websync 4 and the transfering files portion on the conductor was significantly slower(WOW).
I haven't used that many players with 5.9 - haven't seen that error before. If there wasn't something that WS4 fixed you could always go back to WS2. But hopefully MF will pick it up as a bug to fix for WS5 first. [img]/images/graemlins/tongue.gif[/img]
A problem is a difference between what is perceived and what is desired, that
we want to reduce (Dewey 1933)
Update to this issue. The error occurs when running the scripts as a thread. The workaround is run the script as process but that uses more player resources. The issue will not be corrected by MicroFocus as a bug fix. Microfocus recommends running as a process or moving to Silk Performer.