SummarySometimes after a factory reset, adding new network objects fails because they are claimed to already exist.
OverviewIn rare scenarios, trying to add a new network object will fail and an error message will claim that the network object is currently in use by something which appears completely unrelated.
CauseThis can be caused by the factory reset process not completing correctly. In this situation, the ID counter for the network objects will be reset to default, but the network objects may still exist in the Exinda's configuration. So, when you try to generate the network object, it will attempt to start at the default ID number, but that ID will already be in use by another network object which was not fully removed in the factory reset.
WorkaroundThe ID number which the network object is trying to use will increase every time you press the Add New Network Object button. If the button is pressed repeatedly (and fails each time), the ID counter will keep increasing each click. Eventually, it will find an ID number which isn't used.
ResolutionExOS version 7.4.1 was released which contains the fix for this issue. It also resolves the underlying issue which caused the factory reset to not finish correctly in the first place.