"Connection error!" while starting System Analyzer Live in CCS 5.1.0.0900 with EVMC6678

Greetings, 

I am having difficulties launching System Analyzer --> Live while trying to run System Analyzer Tutorial 4C (and other test programs based off of it). It sometimes works, but most of the time I run into some problems while trying to run it. Live will fail to run even when the multi-core application itself appears to be functioning (i.e., I can ping the EVM board). When Live fails to connect, I will get a pop-up dialog with one of the following messages:

• Please check the configuration and restart UIA.
  Unable to open Event Transport 10.0.0.33:1235: address already in use 
• Please check the configuration and restart UIA.
  Unable to open Message Transport 10.0.0.33:1234: connection refused
• Please check the configuration and restart UIA.
  Unable to open Message Transport 10.0.0.33:1234: connection timed out

I pretty sure that there aren't any problems with my connection, since the same configuration does occasionally succeed. In addition, I usually follow the same general sequence setting up System Analyzer as follows:

1. Launch the target configuration 
2. Select all 8 cores in the debug view, right-click and "Group Core(s)"
3. Right-click on the top-level group and select "Connect Target"
4. Select the processor group, then go to_ Run->Load->Load Programs menu and select the .out image
5. Click on the first processor in the group, then click on the down-arrow next to the "CPU Reset" button ( ) and select "Reset System" from the toolbar
6. Click on the processor group and click on the "CPU Reset" button to reset all CPU
7. Click on the Restart button on toolbar ( ) to return each core to the main() function in a suspended state
   • Note: sometimes all cores do not suspend at main(), I try to click the Suspend () and  Restart ( ) buttons again while the group is selected, but a different set of cores fail to suspend at main(). This is likely an unrelated defect. In the end, I sometimes have to manual click on each running core and manually suspend and restart it before I can proceed.
8. Click on the processor group and click on the "Resume" button ( ) to run the application on all of the cores
   • Note: sometimes I may need to click the resume button one more time because not all of the 8 cores running
9. I see "Start test" reported 8 times within the console window once each core has started
   At this point, I always get the "An internal error has occurred." as reported in http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/148140/535577.aspx#535577.
   It appears to be an eclipse failure while opening the MCSA Welcome tab, so I assume it is unrelated to my problem.  
10. Eventually it reports the IP address it is using (in my case, I have it set up to use a static IP of 10.0.0.33)
11. To verify that it is indeed connected to the network, I ping it from a terminal on my desktop
12. Next, I start System Analyzer Live from the menu
13. I load my DefaultSession.usmxml configuration, which I know works (sometimes)
14. Finally I click the Run button

At this point, the System Analyzer Live Session: Logs window appears and one of the following occurs:

• System Analyzer fails to connect as described above 
  • This tends to happen more often after subsequent connection attempts
  • Either previous invocations of System Analyzer fail to release the network handle 
  • or UIA running on the target fails to properly shut down the connection when System Analyzer disconnects (or fails to connect properly)
• System Analyzer connects, but the tab remains blank (i.e., no error dialogs, but no logs reported either)
  • I really don't know what is going on here. Ping still works so I assume the target is running
• System Analyzer connects and functions correctly (if I am lucky)

I find that System Analyzer is a little more reliable if I shut down CCS completely and restart it. Unfortunately, I spend most of my time repeating the process until it works, which isn't an effective use of my time.

If you have any suggestions or work arounds, please let me know. If you require any additional information or project files, I'd be happy to forward them to you.