Folks,
Not sure if anyone has a definitive fix for this yet, but have been using the workaround for some time. I originally had a standalone Openfire install with the embedded DB, and eventually moved to SQL Server and AD integration using LDAP, using OpenFire as a service. This worked for a few revisions until 3.8.x (not sure which revision it started in), where on a reboot of the machine running OpenFire will lose connectivity to Active Directory and not allow users to sign in, nor admins using the OpenFire Server Admin screen.
The only workaround I know of is to first stop the OpenFire service, navigate to the installation directory's conf/Openfire.xml, find the <setup>true</setup> property at the bottom, set it to <setup>false</setup>, save, restart the service and open the Admin page, which you can then guide through the setup again - once you put in the same setup details as you had before, admin and user logins once again work until the next reboot. The same behavior seems to occur on any update as well to Openfire itself, needing the same workaround.
I'd REALLY love not having to do this anymore - has there been any resolution to this scenario? I have two installations exhibiting the behavior, with basically the same setup. No difference between using Windows Server 2012 or 2012 R2 as the Domain Controller or OpenFire host, nor using SQL erver Express 2008 up through 2014. One installation has been updated since the 3.8.0 days, and the other was brand new as of 3.9.3, same behavior.