Hi,
I am facing a very annoying issue. SQL Server 2014 SP1 fails to start after a server reboot with a strange "login failed" Error 1069
Here the details:
I have build a Windows 2008R2 SP1 domain with a domain controller.
I built second Windows 2008R2 SP1 server and made it member of the domain.
I installed the MSDN image SQL Server 2014 SP1 Enterprise edition, installing the "Database services" and the "replication", "management tools complete". All other settings remained to the standards offered by the installation procedure.
Installation proceeds - quite slow - after about 15 minutes.
SQL server is operational, I configured a domain admin account to act as "sysadm" role inside of the service.
I added some databases, imported data, configured a replication and did other things for software testing.
BUT - here the trouble starts - it doesn't survive a restart. The "SQL Server" called service was installed with invalid credential information in the OS services panel, the account with the name "NT Service\MSSQLSERVER" can't start the service due to a login failure.... Error 1069 - very strange with a programmatically created account. That never happend to me before and I installed houndreds of SQL servers in the older versions. As MCP for SQL server I am supposed to know how to do that...
The behavior can be reproduced consistently, happened 10 or 11 times to me within 2 days.
Am I doing something wrong?
Or is that a special issue running on Windows 2008R1 SP1?
The workaround is to choose the "local system account", with that the server works without any issue.
IT architect - Terminal servers, virtualizations, SQL servers, file servers, WAN networks and closely related to software devleopment (8 years + experience in VB, C++ and script langugaes), MCP for SQL server and CCAA for Xenapp 6.5