On one particular subscriber (out of 40+), an error was throw that there were no available identity ranges. In debugging, it was found that this particular subscriber had allocated ranges for all articles 800+ times over the course of a few days by examining msmerge_identity_range_allocations thereby using all int values.
I'm trying to figure out why this happened. Perhaps since all articles for this publication exhibited this issue, the subscription was marked for reinitialization and it was never able to complete but allocated new ranges for the articles and didn't remove those allocations upon not being able to complete all actions. There do not seem to be any hints in the SQL Error logs to help my debugging process.
Has anyone else seen an issue like this? If so, how did you correct it or at least determine root cause?