In Umbraco 6.1.6, we've been able to successfully use ActiveDirectory for our BackOffice login (by adding the connection string in web.config and modifying umbracoSettings.config). Works great for maybe a few days or weeks. Then we'll get a "server is not operational" YSOD after trying to login, with the text shown below. A stackoverflow article has several suggestions, and within that article, the "Connection pooling" answer seems a good bet, but I don't know how to apply that answer. The only "solution" so far has been to kill the IIS process (or restart the server), then things work fine again. We'd love a better solution. (We use the same type of LDAP connection both on that server and other websites and it works fine.)
YSOD using ActiveDirectory for BackOffice login
In Umbraco 6.1.6, we've been able to successfully use ActiveDirectory for our BackOffice login (by adding the connection string in web.config and modifying umbracoSettings.config). Works great for maybe a few days or weeks. Then we'll get a "server is not operational" YSOD after trying to login, with the text shown below. A stackoverflow article has several suggestions, and within that article, the "Connection pooling" answer seems a good bet, but I don't know how to apply that answer. The only "solution" so far has been to kill the IIS process (or restart the server), then things work fine again. We'd love a better solution. (We use the same type of LDAP connection both on that server and other websites and it works fine.)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.