UCA Intialization error

[plee61]

Hi,
After I launched and logged in to UCA, I get an Initialization error:
"Unified Communicator Advanced has failed to connect to the server at xxx.xxx.xxx.
Unified Communicator Advanced will startup in Offline mode. Do you wish to continue?"

But I am able to ping to the server and log in to UCA on another PC with the same login account.

Please advise.
Cheers

[Mattmayn]

Is Windows Firewall running?

[jheinrichs79]

Did this ever get resolved? I am experiencing the same thing. It works most of the time but it happens frequently enough that's becoming a pain.

[Christopp]

I'm seeing sporadic issues as well and it's occurring enough now to become a problem.  Has this been resolved?  I've uninstalled and re-installed successfully on one user's workstation.  But now have one user that this has not worked for.  Restarting the UCA works but then a few days later the initialization error occurs.  Of course the user is the managing partner of the company I work for so it is of higher priority to fix.

Windows 7 64-bit
8GB RAM
Uninstalled and re-installed UCA.
No firewall.
Verified it is pointing to the correct server.
Currently, just one user having the issue.

Thanks in advance.

[akuhn]

From a networking perspective, can you validate that the Client PC running UCA and the MAS Server running the UC Service are on the same subnet?  Pinging is one thing.  That's just a port.

There are dozens, if not hundreds of ports that must be open between these two endpoints if they are NOT in the same subnet.  I think I've posted them on this site at least twice. 

So: 

Step one:  Same Subnet?
Step two:  if not, look at the firewall and compare the ports open between the two and the list on this site.

I know that this is a sometimes it works sometimes it doesn't situation, so we don't know if it's a network issue or not, but you should start with that.

 - Adam in DC

[akuhn]

One more thing, if the UC Server is publicly facing, and it sounds like it, make sure you have an internal DNS entry that directs the client to the correct internal IP address.  You don't want them going out to the internet and coming back in to make this connection.

[disasterjake29]

I had this same issue.  After verifying the Windows Firewall was disabled, I started to check the log file located in C:\Users\<username>\AppData\Roaming\Mitel\UC\ucc.log.  In review of the log compared to a good working system, I found the issue to be caused by a virtual OS adapter being bridged with the internal NIC adapter.  Initially, you will need to break this bridge and restart the UCA Desktop Client.  After the initial client setup, you may recreate the bridge.  Also, make sure that no adapter uses the same network connection that your MAS server and UCA Server.  This may affect your issue too.  I have tested on the 2 affected systems and it worked just fine.

2013-01-04 14:14:44.407 Msg [MainThread]: FastBootManager: Booting Web Services Service
2013-01-04 14:14:44.412 Msg [MainThread]: NetworkMonitoringAgent: Network Address Changed!!!
2013-01-04 14:14:44.416 Inf [MainThread]: NetworkMonitoringAgent: Existing Network Adapter: TeamViewer VPN Adapter, IP=0.0.0.0, IfIndex=19, MAC=00ff25767957
2013-01-04 14:14:44.416 Inf [MainThread]: NetworkMonitoringAgent: Existing Network Adapter: MAC Bridge Miniport, IP=172.x.x.x, IfIndex=15, MAC=xxxxxxxxxxxxx
2013-01-04 14:14:44.416 Inf [MainThread]: NetworkMonitoringAgent: Existing Network Adapter: VirtualBox Host-Only Ethernet Adapter #2, IP=192.168.x.x, IfIndex=18, MAC=xxxxxxxxxxxxx
2013-01-04 14:14:44.416 Msg [MainThread]: NetworkMonitoringAgent: Network adapter added: MAC Bridge Miniport, IP=172.x.x.x, IfIndex=15, MAC=xxxxxxxxxxxxx
2013-01-04 14:14:44.416 Msg [MainThread]: NetworkMonitoringAgent: Network adapter added: VirtualBox Host-Only Ethernet Adapter #2, IP=192.168.x.x, IfIndex=18, MAC=xxxxxxxxxxxxx