search

twright-msft / mssql-node-docker-demo-app

Demonstration application using Microsoft SQL Server on Linux and Node in a Docker container.
MIT License
298 stars 231 forks source link

sa login fails #2

Closed IBMRob closed 7 years ago

IBMRob commented 7 years ago

I'm trying to run this as coded (i.e. I have not updated any passwords so should all just work) and when run I get the following error (Docker on Mac):

Bergkamp:mssql-node-docker-demo-app convery$ docker run -e ACCEPT_EULA=Y -e SA_PASSWORD=Yukon900 -p 1433:1433 -p 8080:8080 -d node-web-app
08ce68c8584e651e2f17c7dc8730b41ef38964664b7ff93a8ecb8e921d9a6472
Bergkamp:mssql-node-docker-demo-app convery$ docker ps -a
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                            NAMES
08ce68c8584e        node-web-app        "/bin/sh -c '/bin/..."   4 seconds ago       Up 1 second         0.0.0.0:1433->1433/tcp, 0.0.0.0:8080->8080/tcp   nostalgic_yonath
B
Bergkamp:mssql-node-docker-demo-app convery$ docker logs nostalgic_yonath
Configuring Microsoft(R) SQL Server(R)...

> mssql-node-docker-demo-app@1.0.1 start /usr/src/app
> node server.js

Listening on port 8080...
Configuration complete.
This is an evaluation version.  There are [146] days left in the evaluation period.
RegQueryValueEx HADR for key "Software\Microsoft\Microsoft SQL Server\MSSQL\MSSQLServer\HADR" failed.
2017-04-18 19:06:49.55 Server      Microsoft SQL Server vNext (CTP1.4) - 14.0.405.198 (X64) 
    Mar 11 2017 01:54:12 
    Copyright (C) 2016 Microsoft Corporation. All rights reserved.
    on Linux (Ubuntu 16.04.1 LTS)
2017-04-18 19:06:49.55 Server      UTC adjustment: 0:00
2017-04-18 19:06:49.55 Server      (c) Microsoft Corporation.
2017-04-18 19:06:49.55 Server      All rights reserved.
2017-04-18 19:06:49.55 Server      Server process ID is 4116.
2017-04-18 19:06:49.55 Server      Logging SQL Server messages in file 'C:\var\opt\mssql\log\errorlog'.
2017-04-18 19:06:49.55 Server      Registry startup parameters: 
     -d C:\var\opt\mssql\data\master.mdf
     -l C:\var\opt\mssql\data\mastlog.ldf
     -e C:\var\opt\mssql\log\errorlog
2017-04-18 19:06:49.56 Server      SQL Server detected 4 sockets with 1 cores per socket and 1 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2017-04-18 19:06:49.56 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2017-04-18 19:06:49.56 Server      Detected 3158 MB of RAM. This is an informational message; no user action is required.
2017-04-18 19:06:49.57 Server      Using conventional memory in the memory manager.
2017-04-18 19:06:49.60 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2017-04-18 19:06:49.67 Server      Buffer pool extension is already disabled. No action is necessary. 
2017-04-18 19:06:49.73 Server      InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2017-04-18 19:06:49.73 Server      Implied authentication manager initialization failed. Implied authentication will be disabled.
2017-04-18 19:06:49.75 Server      The maximum number of dedicated administrator connections for this instance is '1'
2017-04-18 19:06:49.75 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2017-04-18 19:06:49.76 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.
2017-04-18 19:06:49.77 Server      In-Memory OLTP initialized on lowend machine.
2017-04-18 19:06:49.79 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.
2017-04-18 19:06:49.80 Server      Query Store settings initialized with enabled = 1, 
2017-04-18 19:06:49.81 spid6s      Starting up database 'master'.
2017-04-18 19:06:49.81 Server      Software Usage Metrics is disabled.
2017-04-18 19:06:49.90 spid6s      9 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2017-04-18 19:06:49.94 spid6s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2017-04-18 19:06:49.94 spid6s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2017-04-18 19:06:50.02 spid6s      Buffer pool extension is already disabled. No action is necessary. 
2017-04-18 19:06:50.02 spid6s      Resource governor reconfiguration succeeded.
2017-04-18 19:06:50.02 spid6s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2017-04-18 19:06:50.02 spid6s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2017-04-18 19:06:50.05 spid6s      SQL Trace ID 1 was started by login "sa".
2017-04-18 19:06:50.07 spid6s      Server name is '08ce68c8584e'. This is an informational message only. No user action is required.
2017-04-18 19:06:50.07 spid6s      The NETBIOS name of the local node that is running the server is '08ce68c8584e'. This is an informational message only. No user action is required.
2017-04-18 19:06:50.08 spid16s     Password policy update was successful.
2017-04-18 19:06:50.09 spid19s     Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2017-04-18 19:06:50.09 spid6s      Starting up database 'msdb'.
2017-04-18 19:06:50.09 spid19s     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.
2017-04-18 19:06:50.09 spid7s      Starting up database 'mssqlsystemresource'.
2017-04-18 19:06:50.10 spid7s      The resource database build version is 14.00.405. This is an informational message only. No user action is required.
2017-04-18 19:06:50.11 spid7s      Starting up database 'model'.
2017-04-18 19:06:50.36 spid6s      6 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.
2017-04-18 19:06:50.38 spid6s      0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2017-04-18 19:06:50.38 spid7s      Polybase feature disabled.
2017-04-18 19:06:50.38 spid7s      Clearing tempdb database.
2017-04-18 19:06:50.41 spid16s     A self-generated certificate was successfully loaded for encryption.
2017-04-18 19:06:50.42 spid16s     Server is listening on [ 0.0.0.0 <ipv4> 1433].
2017-04-18 19:06:50.42 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2017-04-18 19:06:50.42 Server      Dedicated admin connection support was established for listening locally on port 1434.
2017-04-18 19:06:50.43 spid16s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2017-04-18 19:06:50.67 spid7s      Starting up database 'tempdb'.
2017-04-18 19:06:50.85 spid7s      The tempdb database has 1 data file(s).
2017-04-18 19:06:50.85 spid19s     The Service Broker endpoint is in disabled or stopped state.
2017-04-18 19:06:50.85 spid19s     The Database Mirroring endpoint is in disabled or stopped state.
2017-04-18 19:06:50.86 spid19s     Service Broker manager has started.
2017-04-18 19:06:50.87 spid6s      Recovery is complete. This is an informational message only. No user action is required.
2017-04-18 19:07:04.04 Logon       Error: 18456, Severity: 14, State: 38.
2017-04-18 19:07:04.04 Logon       Login failed for user 'sa'. Reason: Failed to open the explicitly specified database 'DemoData'. [CLIENT: 127.0.0.1]
{ ConnectionError: Login failed for user 'sa'.
    at ConnectionError (/node_modules/tedious/lib/errors.js:12:12)
    at Parser.<anonymous> (/node_modules/tedious/lib/connection.js:373:38)
    at emitOne (events.js:96:13)
    at Parser.emit (events.js:188:7)
    at Parser.<anonymous> (/node_modules/tedious/lib/token/token-stream-parser.js:54:15)
    at emitOne (events.js:96:13)
    at Parser.emit (events.js:188:7)
    at readableAddChunk (/node_modules/readable-stream/lib/_stream_readable.js:212:18)
    at Parser.Readable.push (/node_modules/readable-stream/lib/_stream_readable.js:171:10)
    at Parser.Transform.push (/node_modules/readable-stream/lib/_stream_transform.js:123:32) message: 'Login failed for user \'sa\'.', code: 'ELOGIN' }

The passwords look to be consistent throughout

IBMRob commented 7 years ago

Looks like i was just being impatient. Even though there is this error after a while everything got loaded in.