We can’t pursue this without more details. Are there messages? What’s in the errorLog?
Also, 3.7.14 isn’t current, so there’s nothing to be done unless you can reproduce the problem with the current release, which is 3.7.18.
We can’t pursue this without more details. Are there messages? What’s in the errorLog?
Also, 3.7.14 isn’t current, so there’s nothing to be done unless you can reproduce the problem with the current release, which is 3.7.18.