"Failed to download and/or install client side AOP stack" error in Authoring Environment

Resolving The Problem

You get "java.lang.RuntimeException: Failed to download and/or install client side AOP stack" error after login to Authoring Environment and connection icon in right bottom corner with Process Center hostname becomes amber.


Two most common reasons for this error to appear in AE or in ae.log are:

1. Network configuration problem.

2. Blocked by firewall or assigned to a different network interface port problem.

Let's review both of the above items one by one:

Network configuration problem

This error suggests that AOP stack binding to network interface was not performed correctly. Most likely because of the network configuration problem on Process Center server.

Ping Process Center server from any computer that will run AE. Remember server's IP address.

On Process Center Server open hosts file in text editor:

• /etc/hosts on UNIX-like OSs
• %WINDIR%\system32\drivers\etc\hosts on Windows OS

<p class="MsoNormal">and check the correctness of IP addresses associations with hostnames.
There is one more case for this issue. If Process Center server has multiple network interfaces and it's not clear which one should be resolved into Process Center server hostname.Solution for this problem is to add Process Center server host entry directly into hosts file specifying the IP address. Hostname should be exactly the same as it was specified during Teamworks setup.

//For example:172.27.20.27    processcenterservername.domain.com

You should also check for any other entries with hostname of Process Center server and comment them out.

Also ensure that the DNS entry for the Process Center correctly resolves the hostname to the IP address. If the hostname doesn't resolve, the Process Center can be reinstalled using the IP address instead of the hostname but it's preferable that you add a DNS entry instead and use FQDN.

IMPORTANT NOTES:

• Some OSs resolves host name into ipv6 address if it's enabled, so, make sure you know the correct IPV4 address in this case to use
• On Windows if Process Center host name matches hostname in My Computer properties, settings in %WINDIR%\system32\drivers\etc\hosts may be ignored. So hostname may be resolved randomly into IP of any active network interface (I.e. it can resolve correctly until VPN connection established or VmWare Machine start, and then, after Process Center restart AOP error will appear). In case of such collision Process Server host name should be changed so it will not match Windows PC name. In this case the new host name should also be added to DNS, so clients running AE could know server address.
• The correct loopback association should be (fully qualified host name should NOT point to loopback device):

  127.0.0.1    localhost

  </li>
  
  

  Blocked by firewall or assigned to another network interface port problem

  
  
  You might see the same error if one of the ports that required to be opened by Authoring Environment are blocked by firewall. Most likely in this case you will not see this error pop'd-up in AE but you will still notice the amber light in the right bottom corner and you will see this error in ae.log
  
  If you have more than one NIC installed on your server then you should check that all corresponding ports are binded to correct interface (IP address).
  
  You may check this using netstat command.
  
  Example:
  
  netstat -aon | find "4458"
  
  (above command will output IP address that port 4458 is listening on)
  
  If you see that one or some of the ports are not binded to the interface you would expect them to bind then you can change the bind ordering in Windows OS's.
  
  To do that read the following articles:
  
  http://support.microsoft.com/kb/894564 http://theregime.wordpress.com/2008/03/04/how-to-setview-the-nic-bind-order-in-windows/

  Binding to IPv4 addresses

  Another reason you can get this problem is binding to an ipv6 address instead of ipv4. Here is how I solved this. In the server's wrapper.conf make sure the --host value is using the correct hostname (thus binding to the correct ip). In my case, my hostname is dpthinkpad so mine looks like this: wrapper.app.parameter.5=--host=dpthinkpad Then add a value telling the server to use ipv4 (your number may not be .8, use the next number available) wrapper.app.parameter.8=-Djava.net.preferIPv4Stack=true In your eclipse.ini, add the following: -Djava.net.preferIPv4Stack=true Restart the process center and try again to login