In the event of failed communications, controls whether or not there will be a driver failover to a backup.
- If set to 1 (true), then the drivers do not switch to backup on failed communications (default).
- If set to 0 (false), then the drivers do switch to backup on failed communications.
If you have two servers, both of which are on the same network/subnet, then the likelihood of the backup being able to reach the equipment when the primary cannot is slim. The problem is most likely a device or communications-chain issue. In this case, there is no need to have the servers failing back and forth.
As a general rule, it is better to set NoSoftDriverFailure to 1 (true) unless the servers are on completely different networks with separate paths to the devices.
For legacy OEM applications (12.0.0.6 or older) default = 0
Section: System
Default: NoSoftDriverFailure = 1
*No restart required (Settings.Dynamic property)
