With Linux based repservers where I work, this problem has been active since repserver 12.6 (up to 15.7.1). As mentioned above, it seems to associated with setting up new connection/subscription.
↧
With Linux based repservers where I work, this problem has been active since repserver 12.6 (up to 15.7.1). As mentioned above, it seems to associated with setting up new connection/subscription.