Skip to main content
Kofax

Unable to write data to the transport connection AcLicClnt 7001 in License Utility

9495

QAID # 9495 Published

Question / Problem:

I am receiving the following error in the License Utility:

"7001 AcLicClnt unable to connect to license server
the license server may be down or the network may have problems
unable to write data to the transport connection"

How can I resolve this?

Answer / Solution:

Per QAID 555, you must have:

TCP port 2424, UDP port 1434, and a dynamically-assigned TCP port (see below) open.

The dynamically-assigned TCP port can be found and even edited in the System Registry under the following Registry Key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\AscentCapture\MSSQLServer\SuperSocketNetLib\Tcp\TcpPort

Check the ACConfig.xml file to ensure validity for the XML file.

You may test if the port is open by opening Internet Explorer and entering:

http://<Machine Name>:2424

(where <Machine Name> is replaced by the actual Machine Name).

This must be done on the machine that is running the licensing service (Ascent Capture Service service). If the returned values are similar to:

System.ArgumentNullException: No message was deserialized prior to calling the DispatchChannelSink. Parameter name:
requestMsg at System.Runtime.Remoting.Channels.DispatchChannelSink.ProcessMessage(IServerChannelSinkStack
sinkStack, IMessage requestMsg, ITransportHeaders requestHeaders, Stream requestStream, IMessage& responseMsg,
ITransportHeaders& responseHeaders, Stream& responseStream) at System.Runtime.Remoting.Channels.BinaryServerFormatterSink.ProcessMessage(IServerChannelSinkStack sinkStack,
IMessage requestMsg, ITransportHeaders requestHeaders, Stream requestStream, IMessage& responseMsg,
ITransportHeaders& responseHeaders, Stream& responseStream) at System.Runtime.Remoting.Channels.SoapServerFormatterSink.ProcessMessage(IServerChannelSinkStack sinkStack,
IMessage requestMsg, ITransportHeaders requestHeaders, Stream requestStream, IMessage& responseMsg,
ITransportHeaders& responseHeaders, Stream& responseStream) at
System.Runtime.Remoting.Channels.Http.HttpServerTransportSink.ServiceRequest(Object state) at
System.Runtime.Remoting.Channels.SocketHandler.ProcessRequestNow() 

then licensing and the port should be functioning fine. If not, the port needs to be opened.

Double-check Windows Firewall and/or other firewalls/security devices/routers that may be blocking the port.

Applies To:

Product Version
CAPTURE 10.0
  10.1
  10.2
  11.0
  • Was this article helpful?