Difference between revisions of "Information Systems:Information Systems: Move the Kofax License"
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
*Lastly, move the physical License dongle to the NEWLY installed KC workstation and activate it. |
*Lastly, move the physical License dongle to the NEWLY installed KC workstation and activate it. |
||
| + | *Once activated, check the firewall rules by going to Control Panel\System and Security\Windows Defender Firewall and selecting "Advanced Settings" |
||
| − | ===Move the Kofax License to the server=== |
||
| + | * In Inbound rules, Create a new rule. Select the rule type as "Port". For protocol and ports, add "2424" and then Allow the connection and name it Kofax Licensing. |
||
| − | ****STILL WAITING FOR THE STEPS |
||
| + | * Do the same for the outbound rule. |
||
| + | |||
| + | ==To test the connection, go to the web browser, type the workstationName:2424 and check if the connection works or not. |
||
| + | |||
| + | 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() \ |
||
| + | |||
| + | It should display the above message. |
||
[[Category: Gauss]] |
[[Category: Gauss]] |
||
Revision as of 09:04, 19 July 2023
Move the Kofax License to another Workstation
If you want to move the license to another KC workstation, see below:
- Install the KC workstation from the CaptureSV\wrkinst folder
- Next, disable licensing on the existing KC workstation by running:
aclicsrvcfg.exe /d
- Then go to the newly install KC workstation and enable the licensing service by running:
aclicsrvcfg.exe
- Lastly, move the physical License dongle to the NEWLY installed KC workstation and activate it.
- Once activated, check the firewall rules by going to Control Panel\System and Security\Windows Defender Firewall and selecting "Advanced Settings"
- In Inbound rules, Create a new rule. Select the rule type as "Port". For protocol and ports, add "2424" and then Allow the connection and name it Kofax Licensing.
- Do the same for the outbound rule.
==To test the connection, go to the web browser, type the workstationName:2424 and check if the connection works or not.
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() \
It should display the above message.