When a driver is exchanged with a new driver, the driver configuration of the new driver is opened automatically. With some drivers that use TCP communication, the connections that are created in the driver configuration during the exchange of the driver, are stored in an intermediate file and are not taken over. When the driver configuration is closed to complete the driver exchange, and reopened again, the driver uses the final configuration file, in which the connections are not existing.
When a driver is exchanged with a new driver, the driver configuration of the new driver is opened automatically. With some drivers that use TCP communication, the connections that are created in the driver configuration during the exchange of the driver, are stored in an intermediate file and are not taken over. When the driver configuration is closed to complete the driver exchange, and reopened again, the driver uses the final configuration file, in which the connections are not existing.
An issue was addressed in the handling of driver configuration files during driver exchange. Now the driver no longer uses an intermediate file during the exchange, and the connections are stored correctly.
As a workaround, on driver exchange close the driver configuration, then reopen the driver configuration to enter the connections.