CAF Won't start, CAMSTAT -a returns an error and no cam commands work.

Products

• CA Client Automation - IT Client Manager
• CA Client Automation

Issue/Introduction

This document details a situation where CAF Won't start, CAMSTAT -a returns an error and no cam commands work and 

the steps to take to resolve the timeout message caused by a conflict with a non standard adapter like a 1394 adaptor.

To confirm a possible conflict with a non-standard adapter like a 1394 adapter in your binding order,

you can first perform a simple test to see if CAM will start when the port multiplexor is not used:

If you remove APPF-GLOBAL and APPF-GLOBAL-4105 from %CSAM_SOCKADAPTER%\cfg

(save them somewhere so they can be restored later) and restart CAM it will begin working but without the required port multiplexor integration.

CAF will start but functions that require TCP communication over CAM will fail (Staging Packages for example will no longer work).

(Replace the files removed for the above test before implementing the solution listed)

Also, if you check CAM debug and trace logs you may observe Socket error 10022 or 10048 as in the below example:

11:39:57.532 1 fd 748 (TCP_LISTEN), events 01, revents 01
11:39:57.532 1(0) active(queued messages)/0 inactive queues 
11:39:57.532 event_handler() TCP CONNECT 
11:39:57.532 accept_connection() called for TCP 
11:39:57.532 accept() failed: socket error 10022 
11:40:03.533 1 fd 748 (TCP_LISTEN), events 01, revents 01 
11:40:03.533 1(0) active(queued messages)/0 inactive queues 
11:40:03.533 event_handler() TCP CONNECT 
11:40:03.533 accept_connection() called for TCP 
11:40:03.533 accept() failed: socket error 10048 
11:40:03.533 1 fd 748 (TCP_LISTEN), events 01, revents 01 
11:40:03.533 1(0) active(queued messages)/0 inactive queues 
11:40:03.533 event_handler() TCP CONNECT 
11:40:03.533 accept_connection() called for TCP 
11:40:03.533 accept() failed: socket error 10048

Environment

CA Client Automation- All Versions

Cause

The non standard 1394 adapter for example is bound first in the operating systems binding order

cause issues with cam and changing binding order will resolve the issue. 

Resolution

Check the network binding order for all Network Interface Cards (NIC):

Make sure the Functional NICs are at the top of the list and not the '1394 adapter'.

If the Firewire adapter (1394 adapter) listed above any of the functional network adapters, it can break CAM/PMUX functionality.

If you find this situation, click on the 1394 item to highlight it and then use the 'down arrow' at right to lower it to the bottom of the list.

Now click OK and you are done. Run 'camclose & cam start -c' to restart CAM. CAM will now start and the Port 

Multiplexor (CSAMPMUX.EXE) will work properly without a reboot. (Start CAF now and it should work as expected)