Conductor NT 5.0 server not connecting to ICI
i recently had to change the pc for server. I installed the conductor nt software 5.0 and licenses by the book. I checked all the configurations but it cannot connect to ICI.
Asked 2 years ago
Answers
0
Hi,
Not a lot to go on, if everything is installed and licensed try the following...
Serial ICI - Wind the serial port fifo buffer back to minimum / or turn off. The fifo buffer can interfere with the ICI communications.
SCSI ICI - The SCSI adapter might come with diagnostics. You can usually scan the bus and see the connected slave devices. The ICI will appear as "MCP02" or similar. It should be the only slave device on the bus anyway.
If you think the ICI is visible to Conductor NT, you should have a service running on the server(s) called "DD_nnnn", where "nnnn" is the serial (com1 etc) or SCSI port (S003 etc) as set up by ICICONF. If you have changed the ICI configuration after installation you will need to manually update the service to reflect the ICICONF configuration. The following is snipped from Bailey bulletin TB98049A and was written for Conductor NT 2.0 but a similar procedure applies for later versions.
=======================
TB98049A - Changing ICI Configuration
=======================
With the release of Conductor NT version 2.0 came a new release of semAPI. The version of semAPI released with Conductor uses a service for ICI connections. If you already have version 2.0 installed, you can view this service by going to your Control Panel (in Windows NT, Start - Settings - Control Panel) and open the "Services" portion. You will see a list of services installed on your machine, their startup properties and the their current status. The service used by semAPI is called DD_XXXX, where XXXX is the port you are using for ICI communications (i.e. DD_COM1 is the service you would see for ICI's communicating through COM port 1).
When performing an ICI Configuration (for the sake of changing ports) AFTER Conductor is installed, you must MANUALLY uninstall this service and install the correct one. Follow this procedure to accomplish the task. We will use an example of changing from COM Port 1 to a SCSI Port (S003).
**The EBServerBroker Service must be shut down prior to making these changes.**
Perform a full Conductor NT shutdown
Per the above instructions, go to the services portion of your control panel.
Highlight the EBServerBroker.
Click on the "Stop" Pushbutton. (the service should stop)
If the EBServerBroker did not stop, reboot and sign into the administrator account, then perform the above steps.
1. Obtain the current ICI service by performing the above steps. Change your ICI Configuration through the Conductor Menu (ICICONF).
2. Open a DOS window and run the following commands:
CD \ICI\EXE\WINNT (This will be off of the root in which you installed Conductor NT...usually C:)
deviceasserviceu.exe DD_COM1 -u (This will uninstall the current service) A message should appear stating that the service was removed.
deviceasserviceu.exe DD_S003 -i (This will install the new service) A message should appear stating that the service was installed.
3. Go into the Control Panel, double click "Services" and highlight the DD_S003 service.
4. Click on the "Startup" pushbutton and select the "Automatic" radio button.
5. Click "OK" for the startup option and "Close" the services display.
6. Reboot the machine.
=======================
Server Database
Is the database OK? Is the Infi90 scanner tag configured? Is it the scanner tag reporting that the ICI is not connected?
Cheers,
Alan
Not a lot to go on, if everything is installed and licensed try the following...
Serial ICI - Wind the serial port fifo buffer back to minimum / or turn off. The fifo buffer can interfere with the ICI communications.
SCSI ICI - The SCSI adapter might come with diagnostics. You can usually scan the bus and see the connected slave devices. The ICI will appear as "MCP02" or similar. It should be the only slave device on the bus anyway.
If you think the ICI is visible to Conductor NT, you should have a service running on the server(s) called "DD_nnnn", where "nnnn" is the serial (com1 etc) or SCSI port (S003 etc) as set up by ICICONF. If you have changed the ICI configuration after installation you will need to manually update the service to reflect the ICICONF configuration. The following is snipped from Bailey bulletin TB98049A and was written for Conductor NT 2.0 but a similar procedure applies for later versions.
=======================
TB98049A - Changing ICI Configuration
=======================
With the release of Conductor NT version 2.0 came a new release of semAPI. The version of semAPI released with Conductor uses a service for ICI connections. If you already have version 2.0 installed, you can view this service by going to your Control Panel (in Windows NT, Start - Settings - Control Panel) and open the "Services" portion. You will see a list of services installed on your machine, their startup properties and the their current status. The service used by semAPI is called DD_XXXX, where XXXX is the port you are using for ICI communications (i.e. DD_COM1 is the service you would see for ICI's communicating through COM port 1).
When performing an ICI Configuration (for the sake of changing ports) AFTER Conductor is installed, you must MANUALLY uninstall this service and install the correct one. Follow this procedure to accomplish the task. We will use an example of changing from COM Port 1 to a SCSI Port (S003).
**The EBServerBroker Service must be shut down prior to making these changes.**
Perform a full Conductor NT shutdown
Per the above instructions, go to the services portion of your control panel.
Highlight the EBServerBroker.
Click on the "Stop" Pushbutton. (the service should stop)
If the EBServerBroker did not stop, reboot and sign into the administrator account, then perform the above steps.
1. Obtain the current ICI service by performing the above steps. Change your ICI Configuration through the Conductor Menu (ICICONF).
2. Open a DOS window and run the following commands:
CD \ICI\EXE\WINNT (This will be off of the root in which you installed Conductor NT...usually C:)
deviceasserviceu.exe DD_COM1 -u (This will uninstall the current service) A message should appear stating that the service was removed.
deviceasserviceu.exe DD_S003 -i (This will install the new service) A message should appear stating that the service was installed.
3. Go into the Control Panel, double click "Services" and highlight the DD_S003 service.
4. Click on the "Startup" pushbutton and select the "Automatic" radio button.
5. Click "OK" for the startup option and "Close" the services display.
6. Reboot the machine.
=======================
Server Database
Is the database OK? Is the Infi90 scanner tag configured? Is it the scanner tag reporting that the ICI is not connected?
Cheers,
Alan
Answered 2 years ago
Source: TB98049A
by Stefan Stromqvist
Directed to me, but unfortunately, I have no experience in Conductor NT...
Add new comment