Jason942

Found a possible fix...3rd option worked for me. Virtual Composer 2.8.x and above Broker error Solutions to Virtual Composer 2.8.x getting Broker error. If you see a broker error in Composer when attempting to connect to a Virtual Director there may be 2 possible issues: Port 8443: Another program is using the same network port as broker. Wrong libeay32.dll: There may be a bad or duplicate libeay32.dll file that needs to be removed. Bad Driver: There may be a bad driver causing Virtual Director to crash and needs to be removed. Solution 1: Bad Driver in Virtual Director If there is a bad driver in the Virtual Director project it will cause the Virtual Director to keep crashing and starting over and over. This will cause a broker error because broker and Virtual Director cannot talk to each other. Locate directorstate file. Go to windows search type: %appdata% Go to: Control4 Go to your OS version folder: such as 2.8.0 or 2.8.1 Go to: etc Delete all DirectorState files. Restart Composer and connect to Virtual Director Solution 2: Duplicate Network Port Composer connects to the Broker process is using port 8443. It is possible that other programs may also be using that same network port to connect. If this is the case you will need to change the port the alternate software is using. At this time this is not possible with Broker. Before changing the port you will need to contact the Software provider in order to check what ports can be used. If it is not possible with the 3rd party program to change their ports you must remove the 3rd party program before using Composer. ?Know products using port 8443: - Spice Works - Ubiquity Unify Controller In our example below we have found that Spice works will cause this issue but this is not limited to Spice works, Although on setting up Spice works you do get an option to change the ports. Step one we need to open CMD (with administration rights) Run the command “netstat -abf 5 > Control4_Ports.txt”(Figure 2), Once you enter the command you need to hit enter, after around 2-3 Minutes you will need to cancel the command “Ctrl+C”. Next we need to find the logs for the scrip we have just performed, this is loacated at the following “C:\Windows\System32” the file name is “Control4_Ports.txt” Open the File Control4_Ports.txt, if you Search for 8443, you will find out what Program/service is using this port. In this case we can see that Spice works is using the Port 8443. After removing the program that is using the port from the PC, Composer 2.8.0 virtual composer will now work, Solution 3: Remove or rename bad libeay32.dll file The second solution has to do with a libeay32.dll file used by Composer being a bad file or duplicate file of a system directory file. If there is a second file located you must rename the second file to libeay32.old. Download ProcMon from here: https://technet.microsoft.com/en-us/sysinternals/bb896645 Unzip somewhere and run it. Select Filter->Filter... Add two filters, as follows: Process Name is node.exe Include Operation is Load Image Include Click Apply or OK, now you should see a blank list 6. ? Open windows cmd prompt. (search in windows for cmd) Change directory to broker folder For 2.8.0 copy and paste into cmd prompt: cd C:\Program Files (x86)\Control4\ComposerPro280\Broker For 2.8.1 copy and paste into cmd prompt: cd C:\Program Files (x86)\Control4\ComposerPro281\Broker Paste this and hit enter: node.exe broker.js --log_file="" There should be a bunch of output now in the ProcMon program. Edit->Find (or Ctrl-F) the string "libeay" and note the location. If you find any locations that end with libeay32.dll go to those locations and rename the file. Re-launch composer and try to connect again.

3rd option works for me...... Virtual Composer 2.8.x and above Broker error Solutions to Virtual Composer 2.8.x getting Broker error. If you see a broker error in Composer when attempting to connect to a Virtual Director there may be 2 possible issues: Port 8443: Another program is using the same network port as broker. Wrong libeay32.dll: There may be a bad or duplicate libeay32.dll file that needs to be removed. Bad Driver: There may be a bad driver causing Virtual Director to crash and needs to be removed. Solution 1: Bad Driver in Virtual Director If there is a bad driver in the Virtual Director project it will cause the Virtual Director to keep crashing and starting over and over. This will cause a broker error because broker and Virtual Director cannot talk to each other. Locate directorstate file. Go to windows search type: %appdata% Go to: Control4 Go to your OS version folder: such as 2.8.0 or 2.8.1 Go to: etc Delete all DirectorState files. Restart Composer and connect to Virtual Director Solution 2: Duplicate Network Port Composer connects to the Broker process is using port 8443. It is possible that other programs may also be using that same network port to connect. If this is the case you will need to change the port the alternate software is using. At this time this is not possible with Broker. Before changing the port you will need to contact the Software provider in order to check what ports can be used. If it is not possible with the 3rd party program to change their ports you must remove the 3rd party program before using Composer. ?Know products using port 8443: - Spice Works - Ubiquity Unify Controller In our example below we have found that Spice works will cause this issue but this is not limited to Spice works, Although on setting up Spice works you do get an option to change the ports. Step one we need to open CMD (with administration rights) Run the command “netstat -abf 5 > Control4_Ports.txt”(Figure 2), Once you enter the command you need to hit enter, after around 2-3 Minutes you will need to cancel the command “Ctrl+C”. Next we need to find the logs for the scrip we have just performed, this is loacated at the following “C:\Windows\System32” the file name is “Control4_Ports.txt” Open the File Control4_Ports.txt, if you Search for 8443, you will find out what Program/service is using this port. In this case we can see that Spice works is using the Port 8443. After removing the program that is using the port from the PC, Composer 2.8.0 virtual composer will now work, Solution 3: Remove or rename bad libeay32.dll file The second solution has to do with a libeay32.dll file used by Composer being a bad file or duplicate file of a system directory file. If there is a second file located you must rename the second file to libeay32.old. Download ProcMon from here: https://technet.microsoft.com/en-us/sysinternals/bb896645 Unzip somewhere and run it. Select Filter->Filter... Add two filters, as follows: Process Name is node.exe Include Operation is Load Image Include Click Apply or OK, now you should see a blank list 6. ? Open windows cmd prompt. (search in windows for cmd) Change directory to broker folder For 2.8.0 copy and paste into cmd prompt: cd C:\Program Files (x86)\Control4\ComposerPro280\Broker For 2.8.1 copy and paste into cmd prompt: cd C:\Program Files (x86)\Control4\ComposerPro281\Broker Paste this and hit enter: node.exe broker.js --log_file="" There should be a bunch of output now in the ProcMon program. Edit->Find (or Ctrl-F) the string "libeay" and note the location. If you find any locations that end with libeay32.dll go to those locations and rename the file. Re-launch composer and try to connect again.

Try this...3rd one worked for me. Virtual Composer 2.8.x and above Broker error Solutions to Virtual Composer 2.8.x getting Broker error. If you see a broker error in Composer when attempting to connect to a Virtual Director there may be 2 possible issues: Port 8443: Another program is using the same network port as broker. Wrong libeay32.dll: There may be a bad or duplicate libeay32.dll file that needs to be removed. Bad Driver: There may be a bad driver causing Virtual Director to crash and needs to be removed. Solution 1: Bad Driver in Virtual Director If there is a bad driver in the Virtual Director project it will cause the Virtual Director to keep crashing and starting over and over. This will cause a broker error because broker and Virtual Director cannot talk to each other. Locate directorstate file. Go to windows search type: %appdata% Go to: Control4 Go to your OS version folder: such as 2.8.0 or 2.8.1 Go to: etc Delete all DirectorState files. Restart Composer and connect to Virtual Director Solution 2: Duplicate Network Port Composer connects to the Broker process is using port 8443. It is possible that other programs may also be using that same network port to connect. If this is the case you will need to change the port the alternate software is using. At this time this is not possible with Broker. Before changing the port you will need to contact the Software provider in order to check what ports can be used. If it is not possible with the 3rd party program to change their ports you must remove the 3rd party program before using Composer. ?Know products using port 8443: - Spice Works - Ubiquity Unify Controller In our example below we have found that Spice works will cause this issue but this is not limited to Spice works, Although on setting up Spice works you do get an option to change the ports. Step one we need to open CMD (with administration rights) Run the command “netstat -abf 5 > Control4_Ports.txt”(Figure 2), Once you enter the command you need to hit enter, after around 2-3 Minutes you will need to cancel the command “Ctrl+C”. Next we need to find the logs for the scrip we have just performed, this is loacated at the following “C:\Windows\System32” the file name is “Control4_Ports.txt” Open the File Control4_Ports.txt, if you Search for 8443, you will find out what Program/service is using this port. In this case we can see that Spice works is using the Port 8443. After removing the program that is using the port from the PC, Composer 2.8.0 virtual composer will now work, Solution 3: Remove or rename bad libeay32.dll file The second solution has to do with a libeay32.dll file used by Composer being a bad file or duplicate file of a system directory file. If there is a second file located you must rename the second file to libeay32.old. Download ProcMon from here: https://technet.microsoft.com/en-us/sysinternals/bb896645 Unzip somewhere and run it. Select Filter->Filter... Add two filters, as follows: Process Name is node.exe Include Operation is Load Image Include Click Apply or OK, now you should see a blank list 6. ? Open windows cmd prompt. (search in windows for cmd) Change directory to broker folder For 2.8.0 copy and paste into cmd prompt: cd C:\Program Files (x86)\Control4\ComposerPro280\Broker For 2.8.1 copy and paste into cmd prompt: cd C:\Program Files (x86)\Control4\ComposerPro281\Broker Paste this and hit enter: node.exe broker.js --log_file="" There should be a bunch of output now in the ProcMon program. Edit->Find (or Ctrl-F) the string "libeay" and note the location. If you find any locations that end with libeay32.dll go to those locations and rename the file. Re-launch composer and try to connect again.

I just download Composer Pro in a Win 10 Pro machine and I am getting a error message. I am selecting the Virtual System, and I am not able to connect. The Composer firmware is 2.9.0.522736. Below are images of the error messages I am getting. Does any one have a fix for this? Thanks....Jason