Problem

CFT Multinode Copilot as a Windows service

The copilot starts when using copsmng but not when copstart is used

Error in copui.trc :
MSG ALL 3860 Copilot starting... (c\src\copui\copui.c:474) [initSrv]
MSG ALL 3860 Copilot server successfully started on port 1766
ERR HTTP 4200 HttpSendFile : failure code:200 filename:C:\Axway\Transfer_CFT\home\distrib\copilot\applets\CopilotApplet.jar
ERR HTTP 4404 HttpSendFile : failure code:200 filename:C:\Axway\Transfer_CFT\home\distrib\copilot\applets\plugin.jar
ERR HTTP 4536 HttpSendFile : failure code:200 filename:C:\Axway\Transfer_CFT\home\distrib\copilot\applets\plugin.jar
ERR HTTP 4404 HttpSendFile : failure code:200 filename:C:\Axway\Transfer_CFT\home\distrib\copilot\applets\CopilotApplet.jar
MSG ALL 3860 Copilot is shutting down

Resolution

Usually, the root cause for such an issue where the the copilot starts when using copsmng but not when as a Windows Service (or when copstart is used as itself launch the Service if Service is set in the UCONF for Copilot), is an issue with access to the shared drive.

Remember that Windows Service do not have access to the UNC server without doing some configuration, even if launched using a specific user known to have access to the UNC server.

Can you start to check with the customer if they managed that the Service can have access to the mapped drive you are using for the share.

There are some information into that KB: https://support.axway.com/kb/178999 (The copilot starts when using copsmng but not when copstart is used)

Also, several methods exists to grant a Windows Service to an UNC server.

This other KB article: https://support.axway.com/kb/177229, is not specific to Copilot as a Service but can also help the understanding of the needed steps so a Windows Service can have access to a UNC mapped drive.