All other services (Agent, Integration, Analysis, etc.) run OK using a regular domain user account, but the SQL Server service uses the managed service account.
INSTALL SQL SERVER 2014 WITHOUT DOMAIN WINDOWS
Since we are at functional level Windows Server 2008 R2, I set up a managed service account for SQL Server according to guidelines in and related articles like. While searching I learned about "Managed Service Accounts" as an alternative. For the SQL Server service itself, I had to leave it with the default virtual account "NT Service\MSSQL$" in order to connect to the server in SSMS. Step 15 Select service account names and. Step 14 Click Next on the above screen and the following screen appears. Step 13 Enter the named instance (here I used TestInstance) and click Next. Step 12 Select Database engine services checkbox and click Next. Then I fiddled later with attempting to change them to domain accounts. Step 11 Select SQL Server feature installation option and click Next.
I finally succeeded in installing SQL Server 2014 leaving the default service accounts in place. I took the advice to enable TLS 1.0 and 1.1 among others on our DCs along with some weaker ciphers.
INSTALL SQL SERVER 2014 WITHOUT DOMAIN INSTALL
For example, do we need to install a certificate on our DCs? Can it be a self-signed certificate, since we are making connections to SQL Server only on our LAN? Can we use something like OpenSSL? I am not sure where to start diagnosing and correcting this setup error. We have no connections to the SQL Server outside our LAN and are not running IIS or any web services on the servers. Our existing DC runs Windows Server 2008 R2 and SQL Server 2005 Standard. The error help link displayed after this just takes me to a main Microsoft page, not any help text. (provider: SSL Provider, error: 0 - The token supplied to the function is invalid) Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.Ĭomponent name: SQL Server Database Engine Services Instance FeaturesĮrror description: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. Reason for failure: An error occurred during the setup process of the feature. SQL Server Setup gets near the end and throws this error as shown in the Summary Setup Log: Service accounts are set to domain user accounts with sufficient privileges. Performance has been fine on our small LAN.) All prerequisite checks pass except for the warning about installing on a DC. (I know it's not recommended, but we are a small operation and have combined Windows Server domain controllers and SQL Server without problem for years.
I am attempting to install SQL Server 2014 Standard edition on a new Windows Server 2016 set up as a domain controller that replaces a retired DC.