Problem:

We had Enterprise Server running prior to the network reconnection, but now that the machine is reconnected to the network the server fails to start. We checked the console log and found message CASCS5007I Communications interface 01 termination started just after it was started. We also checked the log.html which recorded communication received a CCITC32-0003E error An invalid parameter was passed to CCI. In checking the task manager all CAS processes were running; casmgr, cassi’s cascd casjcp but no mfcs.

Resolution:

The server is in a state between started and stopped, and this may require the ending the process CASMGR which will end the other processes. Create a new server generic with no special options and start the new server. Review the IP address that show on the Enterprise Server Administration page. Are they the same or different? The IP address may change after the reconnection; this is because the machine was reconfigured so this is expected. The communication process listener was hard coded to a signal IP address so that it could be monitored. Therefore, correcting the hard coded IP address will resolve the problem so that the region will be able to start.

An example of the log.HTML is below.

2009-10-17 03:26:30.621 [1] MFCS running in directory C:\\WINDOWS\\system32, in Enterprise Server mode

2009-10-17 03:26:30.621 [1] MFCS server "PROD" running as process 14004

2009-10-17 03:26:30.753 [1] COMMS: communications component error when starting listener "PROD"

2009-10-17 03:26:30.753 [1] CCI error 6 when starting endpoint PROD: CCITC32-0003E An invalid parameter was passed to CCI.

2009-10-17 03:26:30.753 [1] Unable to open MFDS control channel at tcp:10.10.10.01:7001 - exiting

2009-10-17 03:26:32.000 [1] MFCS process 14004 started Saturday, October 17, 2009 3:26:30 AM:

Incident Number: 2358259