Overview
An adviser is experiencing Floating Media Bar (FMB) log outs and silent calls while they are working.
Solution
This issue with FMB log outs and silent calls experienced by the advisor can be caused by another FMB process that is already running and using the same ports on their workstation. To verify and correct this issue please do the following:
- Check the FMB Logs for the following errors:
LOGMS: VoltDelta.OMB.FMB.ClickToDialHandler.ClickToDialEventLoop: Caught Exception: System.Net.Sockets.SocketException (0x80004005): Only one usage of each socket address (protocol/network address/port) is normally permitted at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at System.Net.Sockets.UdpClient..ctor(Int32 port, AddressFamily family) at VoltDelta.OMB.FMB.ClickToDialHandler.ClickToDialEventLoop()
LOGEX: VoltDelta.OMB.FMB.App.createClientServiceHost: ServiceHost.Open [AddressAlreadyInUseException] System.ServiceModel.AddressAlreadyInUseException: Cannot listen on pipe name 'net.pipe://localhost/VoltDelta.OMB.FMB' because another pipe endpoint is already listening on that name. ---> System.IO.PipeException: Cannot listen on pipe name 'net.pipe://localhost/VoltDelta.OMB.FMB' because another pipe endpoint is already listening on that name. --- End of inner exception stack trace --- at System.ServiceModel.Channels.PipeSharedMemory.Create(List`1 allowedSids, Uri pipeUri, String sharedMemoryName) at System.ServiceModel.Channels.PipeConnectionListener.Listen() at System.ServiceModel.Channels.BufferedConnectionListener.Listen() at System.ServiceModel.Channels.ExclusiveNamedPipeTransportManager.OnOpen() at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener) at System.ServiceModel.Channels.TransportManagerContainer.Open(SelectTransportManagersCallback selectTransportManagerCallback) at System.ServiceModel.Channels.TransportChannelListener.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.ConnectionOrientedTransportChannelListener.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.NamedPipeChannelListener`2.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at VoltDelta.OMB.FMB.App.createClientSe
For more information on how to find the FMB log files please refer to the Locating Agent Workstation Logs article. - If you have these errors, please have the advisor reboot their machine and log back in to ensure only a single FMB process instance is running.
Testing
After rebooting the adviser's machine, they no longer experience FMB log-outs and silent calls.
If the system reboot does not resolve the advisor's issue, please create a support ticket and attach the workstation log files from the adviser's workstation. For more information on how to find the workstation log files please refer to the Locating Agent Workstation Logs article.