Docker Community Forums

Share and learn in the Docker community.

Docker stuck at Using 'xplog70.dll' version '2017.140.3192' to execute extended stored procedure 'xp_msver'

Hi Team,
When dockerisng image for sqlserver on windows docker in linux container mode. I get the following messages. below is the docker-compose and messages

version: ‘3.4’

services:

authentication:

    image: authentication
    build:
      context: server\Authentication
      dockerfile: Dockerfile
    ports:
        - "8089:80"
    depends_on:
        - newsdatabase
    environment:
        "AuthDbConst": "Data Source=newsdatabase;database=AuthDB;user id=sa;password=********;"

server:

    image: server
    build:
      context: server\server
      dockerfile: Dockerfile
    ports:
        - "8082:80"
    depends_on:
        - newsdatabase
    environment:
        "FavDbConst": "Data Source=newsdatabase;database=FavouritesDB;user id=sa;password=********;"
       
frontend:
   
    image: frontend
    build:
       context: frontend
       dockerfile: Dockerfile
    
    ports:
        - "4200:4200"
    
newsdatabase:
    image: mcr.microsoft.com/mssql/server:2017-latest
    ports:
        - "1433:1433"
    environment:
        - ACCEPT_EULA=Y
        - SA_PASSWORD=*******

networks:
default:
driver: custom-driver-1

When running docker-compose up got the following as result
2019-07-24 07:56:52.28 Server Setup step is copying system data file ‘C:\templatedata\msdblog.ldf’ to ‘/var/opt/mssql/data/msdblog.ldf’.
2019-07-24 07:56:52.65 Server Microsoft SQL Server 2017 (RTM-CU15-GDR) (KB4505225) - 14.0.3192.2 (X64)
Jun 15 2019 00:45:05
Copyright © 2017 Microsoft Corporation
Developer Edition (64-bit) on Linux (Ubuntu 16.04.6 LTS)
2019-07-24 07:56:52.70 Server UTC adjustment: 0:00
2019-07-24 07:56:52.73 Server © Microsoft Corporation.
2019-07-24 07:56:52.74 Server All rights reserved.
2019-07-24 07:56:52.76 Server Server process ID is 28.
2019-07-24 07:56:52.76 Server Logging SQL Server messages in file ‘/var/opt/mssql/log/errorlog’.
2019-07-24 07:56:52.78 Server Registry startup parameters:
-d /var/opt/mssql/data/master.mdf
-l /var/opt/mssql/data/mastlog.ldf
-e /var/opt/mssql/log/errorlog
2019-07-24 07:56:52.85 Server SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2019-07-24 07:56:52.92 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-07-24 07:56:52.92 Server Detected 1584 MB of RAM. This is an informational message; no user action is required.
2019-07-24 07:56:52.93 Server Using conventional memory in the memory manager.
2019-07-24 07:56:55.15 Server Buffer pool extension is already disabled. No action is necessary.
2019-07-24 07:56:55.64 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2019-07-24 07:56:55.65 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2019-07-24 07:56:55.66 Server Successfully initialized the TLS configuration. Allowed TLS protocol versions are [‘1.0 1.1 1.2’]. Allowed TLS ciphers are [‘ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:!DHE-RSA-AES256-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES256-SHA:!DHE-RSA-AES128-SHA’].
2019-07-24 07:56:55.82 Server The maximum number of dedicated administrator connections for this instance is ‘1’
2019-07-24 07:56:55.83 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003: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-07-24 07:56:55.85 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-07-24 07:56:55.87 Server In-Memory OLTP initialized on lowend machine.
2019-07-24 07:56:55.99 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.
ForceFlush is enabled for this instance.
2019-07-24 07:56:56.01 Server Query Store settings initialized with enabled = 1,
2019-07-24 07:56:56.05 spid7s Starting up database ‘master’.
2019-07-24 07:56:56.05 Server Software Usage Metrics is disabled.
ForceFlush feature is enabled for log durability.
2019-07-24 07:56:56.52 spid7s The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes. 3072 bytes at offset 418816 in file /var/opt/mssql/data/mastlog.ldf will be written.
2019-07-24 07:56:57.63 spid7s Converting database ‘master’ from version 862 to the current version 869.
2019-07-24 07:56:57.63 spid7s Database ‘master’ running the upgrade step from version 862 to version 863.
2019-07-24 07:56:57.86 spid7s Database ‘master’ running the upgrade step from version 863 to version 864.
2019-07-24 07:56:58.44 spid7s Database ‘master’ running the upgrade step from version 864 to version 865.
2019-07-24 07:56:58.63 spid7s Database ‘master’ running the upgrade step from version 865 to version 866.
2019-07-24 07:56:58.83 spid7s Database ‘master’ running the upgrade step from version 866 to version 867.
2019-07-24 07:56:59.13 spid7s Database ‘master’ running the upgrade step from version 867 to version 868.
2019-07-24 07:56:59.32 spid7s Database ‘master’ running the upgrade step from version 868 to version 869.
2019-07-24 07:56:59.81 Server Failed to verify the Authenticode signature of ‘C:\binn\secforwarder.dll’. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2019-07-24 07:57:00.04 spid7s Resource governor reconfiguration succeeded.
2019-07-24 07:57:00.08 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2019-07-24 07:57:00.10 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2019-07-24 07:57:00.28 spid7s SQL Trace ID 1 was started by login “sa”.
2019-07-24 07:57:00.49 spid7s Server name is ‘2d76c9429c92’. This is an informational message only. No user action is required.
2019-07-24 07:57:00.54 spid21s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2019-07-24 07:57:00.56 spid9s Starting up database ‘mssqlsystemresource’.
2019-07-24 07:57:00.58 spid7s Starting up database ‘msdb’.
2019-07-24 07:57:00.59 spid19s Password policy update was successful.
2019-07-24 07:57:00.61 spid21s Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2019-07-24 07:57:00.65 spid9s The resource database build version is 14.00.3192. This is an informational message only. No user action is required.
2019-07-24 07:57:00.82 spid9s Starting up database ‘model’.
2019-07-24 07:57:01.01 spid7s The tail of the log for database msdb is being rewritten to match the new sector size of 4096 bytes. 512 bytes at offset 306688 in file /var/opt/mssql/data/MSDBLog.ldf will be written.
2019-07-24 07:57:01.11 spid7s Converting database ‘msdb’ from version 862 to the current version 869.
2019-07-24 07:57:01.12 spid7s Database ‘msdb’ running the upgrade step from version 862 to version 863.
2019-07-24 07:57:01.23 spid9s The tail of the log for database model is being rewritten to match the new sector size of 4096 bytes. 2048 bytes at offset 75776 in file /var/opt/mssql/data/modellog.ldf will be written.
2019-07-24 07:57:01.29 spid9s Converting database ‘model’ from version 862 to the current version 869.
2019-07-24 07:57:01.30 spid9s Database ‘model’ running the upgrade step from version 862 to version 863.
2019-07-24 07:57:01.44 spid7s Database ‘msdb’ running the upgrade step from version 863 to version 864.
2019-07-24 07:57:01.50 spid19s A self-generated certificate was successfully loaded for encryption.
2019-07-24 07:57:01.51 spid19s Server is listening on [ ‘any’ 1433].
2019-07-24 07:57:01.52 spid19s Server is listening on [ ‘any’ 1433].
2019-07-24 07:57:01.53 Server Server is listening on [ ::1 1434].
2019-07-24 07:57:01.54 spid9s Database ‘model’ running the upgrade step from version 863 to version 864.
2019-07-24 07:57:01.55 Server Server is listening on [ 127.0.0.1 1434].
2019-07-24 07:57:01.55 Server Dedicated admin connection support was established for listening locally on port 1434.
2019-07-24 07:57:01.57 spid19s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-07-24 07:57:01.63 spid7s Database ‘msdb’ running the upgrade step from version 864 to version 865.
2019-07-24 07:57:01.65 spid9s Database ‘model’ running the upgrade step from version 864 to version 865.
2019-07-24 07:57:01.70 spid7s Database ‘msdb’ running the upgrade step from version 865 to version 866.
2019-07-24 07:57:01.72 spid9s Database ‘model’ running the upgrade step from version 865 to version 866.
2019-07-24 07:57:01.80 spid9s Database ‘model’ running the upgrade step from version 866 to version 867.
2019-07-24 07:57:01.80 spid7s Database ‘msdb’ running the upgrade step from version 866 to version 867.
2019-07-24 07:57:01.89 spid9s Database ‘model’ running the upgrade step from version 867 to version 868.
2019-07-24 07:57:01.91 spid7s Database ‘msdb’ running the upgrade step from version 867 to version 868.
2019-07-24 07:57:02.00 spid7s Database ‘msdb’ running the upgrade step from version 868 to version 869.
2019-07-24 07:57:02.07 spid9s Database ‘model’ running the upgrade step from version 868 to version 869.
2019-07-24 07:57:02.43 spid9s Polybase feature disabled.
2019-07-24 07:57:02.43 spid9s Clearing tempdb database.
2019-07-24 07:57:03.63 spid9s Starting up database ‘tempdb’.
2019-07-24 07:57:03.92 spid9s The tempdb database has 1 data file(s).
2019-07-24 07:57:04.10 spid21s The Service Broker endpoint is in disabled or stopped state.
2019-07-24 07:57:04.11 spid21s The Database Mirroring endpoint is in disabled or stopped state.
2019-07-24 07:57:04.16 spid21s Service Broker manager has started.
2019-07-24 07:57:04.44 spid7s Recovery is complete. This is an informational message only. No user action is required.
2019-07-24 07:57:04.78 spid20s The default language (LCID 0) has been set for engine and full-text services.
2019-07-24 08:01:54.20 spid51 Using ‘dbghelp.dll’ version ‘4.0.5’
2019-07-24 08:01:58.49 spid51 Attempting to load library ‘xplog70.dll’ into memory. This is an informational message only. No user action is required.
2019-07-24 08:01:58.65 spid51 Using ‘xplog70.dll’ version ‘2017.140.3192’ to execute extended stored procedure ‘xp_msver’. This is an informational message only; no user action is required.

Please help me to find a solution?