none
Fehler bei Installation Express 2017 RRS feed

Alle Antworten

  • Hallo Markus,

    da gibt es viele mögliche Ursachen. Poste bitte mal den Inhalt des Installationslogs.

      SQL SERVER – Install Error – Could not Find the Database Engine Startup Handle

      SQL Server Troubleshooting: Could Not Find Database Engine Startup Handle Error During installation

      ...


    Gruß, Stefan
    Microsoft MVP - Visual Developer ASP/ASP.NET (2001-2018)
    https://www.asp-solutions.de/ - IT Beratung, Softwareentwicklung, Remotesupport

    Sonntag, 13. Oktober 2019 11:07
    Moderator
  • Hallo Stefan, danke für deine Antwort.

    die Datei SQLServerErrorlog... hat folgenden Inhalt. 

    2019-10-12 21:24:54.24 Server      Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64) 
    Aug 22 2017 17:04:49 
    Copyright (C) 2017 Microsoft Corporation
    Express Edition (64-bit) on Windows 10 Pro for Workstations 10.0 <X64> (Build 18362: )

    2019-10-12 21:24:54.24 Server      UTC adjustment: 2:00
    2019-10-12 21:24:54.24 Server      (c) Microsoft Corporation.
    2019-10-12 21:24:54.24 Server      All rights reserved.
    2019-10-12 21:24:54.24 Server      Server process ID is 6852.
    2019-10-12 21:24:54.24 Server      System Manufacturer: 'System manufacturer', System Model: 'System Product Name'.
    2019-10-12 21:24:54.24 Server      Authentication mode is WINDOWS-ONLY.
    2019-10-12 21:24:54.24 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
    2019-10-12 21:24:54.24 Server      The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
    2019-10-12 21:24:54.24 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
    2019-10-12 21:24:54.25 Server      Command Line Startup Parameters:
    -s "SQLEXPRESS"
    -m "SqlSetup"
    -Q
    -q "Latin1_General_CI_AS"
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    -T 8015
    -d "C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Template Data\master.mdf"
    -l "C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Template Data\mastlog.ldf"
    2019-10-12 21:24:54.25 Server      SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
    2019-10-12 21:24:54.25 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2019-10-12 21:24:54.25 Server      Detected 14266 MB of RAM. This is an informational message; no user action is required.
    2019-10-12 21:24:54.25 Server      Using conventional memory in the memory manager.
    2019-10-12 21:24:54.27 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2019-10-12 21:24:54.30 Server      Buffer pool extension is already disabled. No action is necessary. 
    2019-10-12 21:24:54.32 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2019-10-12 21:24:54.33 Server      InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
    2019-10-12 21:24:54.33 Server      Implied authentication manager initialization failed. Implied authentication will be disabled.
    2019-10-12 21:24:54.34 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2019-10-12 21:24:54.34 Server      This instance of SQL Server last reported using a process ID of 5816 at 12.10.2019 21:21:53 (local) 12.10.2019 19:21:53 (UTC). This is an informational message only; no user action is required.
    2019-10-12 21:24:54.34 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2019-10-12 21:24:54.34 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2019-10-12 21:24:54.35 Server      In-Memory OLTP initialized on standard machine.
    2019-10-12 21:24:54.36 Server      Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
    2019-10-12 21:24:54.36 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2019-10-12 21:24:54.36 spid5s      Warning ******************
    2019-10-12 21:24:54.36 Server      Query Store settings initialized with enabled = 1, 
    2019-10-12 21:24:54.36 spid5s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2019-10-12 21:24:54.36 Server      Software Usage Metrics is disabled.
    2019-10-12 21:24:54.36 spid5s      Starting up database 'master'.
    2019-10-12 21:24:54.38 spid5s      2 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
    2019-10-12 21:24:54.38 spid5s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
    2019-10-12 21:24:54.43 spid5s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2019-10-12 21:24:54.43 spid5s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2019-10-12 21:24:54.44 spid5s      SQL Trace ID 1 was started by login "sa".
    2019-10-12 21:24:54.44 spid5s      Server name is 'DESKTOP-K0145BV\SQLEXPRESS'. This is an informational message only. No user action is required.
    2019-10-12 21:24:54.45 spid5s      Starting up database 'msdb'.
    2019-10-12 21:24:54.45 spid9s      Starting up database 'mssqlsystemresource'.
    2019-10-12 21:24:54.45 Server      CLR version v4.0.30319 loaded.
    2019-10-12 21:24:54.45 spid9s      The resource database build version is 14.00.1000. This is an informational message only. No user action is required.
    2019-10-12 21:24:54.45 spid16s     Error: 17190, Severity: 16, State: 1.
    2019-10-12 21:24:54.45 spid16s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2019-10-12 21:24:54.45 spid16s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2019-10-12 21:24:54.45 spid16s     Error: 17182, Severity: 16, State: 1.
    2019-10-12 21:24:54.45 spid16s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. 
    2019-10-12 21:24:54.45 spid16s     Error: 17182, Severity: 16, State: 1.
    2019-10-12 21:24:54.45 spid16s     TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. 
    2019-10-12 21:24:54.45 spid16s     Error: 17826, Severity: 18, State: 3.
    2019-10-12 21:24:54.45 spid16s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2019-10-12 21:24:54.45 spid16s     Error: 17120, Severity: 16, State: 1.
    2019-10-12 21:24:54.45 spid16s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the operating system error log for information about possible related problems.


    Markus

    Sonntag, 13. Oktober 2019 15:41
  • Hi,
    welches Konto nutzt Du als Dienstkonto? Hat das Konto ausreichend Rechte? Schau auch mal hier.

    --
    Best Regards / Viele Grüße
    Peter Fleischer (former MVP for Developer Technologies)
    Homepage, Tipps, Tricks

    Sonntag, 13. Oktober 2019 15:54