June 23, 2016 at 5:36 am
The logs look pretty similar when the service fails to start with the exception of the port
2016-06-22 09:12:27.12 Server Microsoft SQL Server 2014 (SP1-CU6) (KB3144524) - 12.0.4449.0 (X64)
Apr 13 2016 12:41:07
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 <X64> (Build 9600: )
2016-06-22 09:12:27.12 Server UTC adjustment: -5:00
2016-06-22 09:12:27.12 Server (c) Microsoft Corporation.
2016-06-22 09:12:27.12 Server All rights reserved.
2016-06-22 09:12:27.12 Server Server process ID is XXXX.
2016-06-22 09:12:27.12 Server System Manufacturer: 'HP', System Model: 'ProLiant DL380 G6'.
2016-06-22 09:12:27.12 Server Authentication mode is MIXED.
2016-06-22 09:12:27.12 Server Logging SQL Server messages in file 'X:\XXXXXX\XXXXXXXXXXXXXXXX\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2016-06-22 09:12:27.12 Server The service account is 'XX\XXXXXXX'. This is an informational message; no user action is required.
2016-06-22 09:12:27.12 Server Registry startup parameters:
-d X:\XXXXXX\XXXXXXXXXXXXXXXX\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
-e X:\XXXXXX\XXXXXXXXXXXXXXXX\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l X:\XXXXXX\XXXXXXXXXXXXXXXX\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2016-06-22 09:12:27.13 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
2016-06-22 09:12:27.79 Server SQL Server detected 2 sockets with 4 cores per socket and 8 logical processors per socket, 16 total logical processors; using 16 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2016-06-22 09:12:27.79 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-06-22 09:12:27.80 Server Detected 49141 MB of RAM. This is an informational message; no user action is required.
2016-06-22 09:12:27.80 Server Using conventional memory in the memory manager.
2016-06-22 09:12:27.87 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2016-06-22 09:12:27.96 Server The maximum number of dedicated administrator connections for this instance is '1'
2016-06-22 09:12:27.96 Server This instance of SQL Server last reported using a process ID of XXXXX at 6/22/2016 9:05:07 AM (local) 6/22/2016 2:05:07 PM (UTC). This is an informational message only; no user action is required.
2016-06-22 09:12:27.96 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.
2016-06-22 09:12:27.96 Server Node configuration: node 1: CPU mask: 0x000000000000ff00:0 Active CPU mask: 0x000000000000ff00:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2016-06-22 09:12:28.01 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.
2016-06-22 09:12:28.01 Server Lock partitioning is enabled. This is an informational message only. No user action is required.
2016-06-22 09:12:28.04 spid8s Starting up database 'master'.
2016-06-22 09:12:28.09 Server CLR version v4.0.30319 loaded.
2016-06-22 09:12:28.13 spid8s 9 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2016-06-22 09:12:28.14 spid8s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2016-06-22 09:12:28.14 spid8s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2016-06-22 09:12:28.21 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2016-06-22 09:12:28.45 spid8s Resource governor reconfiguration succeeded.
2016-06-22 09:12:28.45 spid8s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2016-06-22 09:12:28.45 spid8s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2016-06-22 09:12:28.49 spid8s SQL Trace ID 1 was started by login "XX".
2016-06-22 09:12:28.49 spid8s Server name is 'XXXXXXXXXXXXXXX'. This is an informational message only. No user action is required.
2016-06-22 09:12:28.49 spid8s The NETBIOS name of the local node that is running the server is 'XXXXXXXXXXXXXX'. This is an informational message only. No user action is required.
2016-06-22 09:12:28.60 spid16s A self-generated certificate was successfully loaded for encryption.
2016-06-22 09:12:28.68 spid17s Error: 9954, Severity: 16, State: 1.
2016-06-22 09:12:28.68 spid17s SQL Server failed to communicate with filter daemon launch service (Windows error: The service did not start due to a logon failure.
). Full-Text filter daemon process failed to start. Full-text search functionality will not be available.
2016-06-22 09:12:28.68 spid20s Starting up database 'XXXXX'.
2016-06-22 09:12:28.68 spid19s Starting up database 'msdb'.
2016-06-22 09:12:28.69 spid12s Starting up database 'mssqlsystemresource'.
2016-06-22 09:12:28.72 spid12s The resource database build version is 12.00.4449. This is an informational message only. No user action is required.
2016-06-22 09:12:28.76 spid16s Server is listening on [ XX.XXX.XXX.XX <ipv4> 51409].
2016-06-22 09:12:28.76 spid16s Started listening on virtual network name 'XXXXXXXXXXXXXXX'. No user action is required.
2016-06-22 09:12:28.76 spid16s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2016-06-22 09:12:28.76 spid16s Server local connection provider is ready to accept connection on [ \\.\pipe\$$\XXXXXXXXXXXXXXX\sql\query ].
2016-06-22 09:12:28.77 spid16s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2016-06-22 09:12:28.77 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2016-06-22 09:12:28.79 spid19s 1 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.
2016-06-22 09:12:28.82 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/XXXXXXXXXXXXXXX.XX.XXX-XXX.com ] for the SQL Server service.
2016-06-22 09:12:28.82 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/XXXXXXXXXXXXXXX.XX.XXXX-XXX.com:51409 ] for the SQL Server service.
2016-06-22 09:12:28.84 spid12s Starting up database 'model'.
2016-06-22 09:12:28.88 spid8s 0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2016-06-22 09:12:28.94 spid12s Clearing tempdb database.
2016-06-22 09:12:29.16 Server Software Usage Metrics is disabled.
2016-06-22 09:12:29.25 spid12s Starting up database 'tempdb'.
2016-06-22 09:12:30.78 spid26s The Service Broker endpoint is in disabled or stopped state.
2016-06-22 09:12:30.78 spid26s The Database Mirroring endpoint is in disabled or stopped state.
2016-06-22 09:12:30.79 spid26s Service Broker manager has started.
2016-06-22 09:12:41.93 spid20s 1 transactions rolled forward in database 'XXXXX' (5:0). This is an informational message only. No user action is required.
2016-06-22 09:12:42.02 spid8s 0 transactions rolled back in database 'XXXXX' (5:0). This is an informational message only. No user action is required.
2016-06-22 09:12:42.54 spid8s Recovery is complete. This is an informational message only. No user action is required.
June 23, 2016 at 5:37 am
Microsoft do not recommend changing the port on a default instance, leave it at 1433.
Why do you want to change it
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 23, 2016 at 5:41 am
The suggestion was made to help improve security since, you know, no one has ever been able to access an environment not using port 1433 :laugh:
June 23, 2016 at 8:31 am
RonMexico (6/23/2016)
The suggestion was made to help improve security since, you know, no one has ever been able to access an environment not using port 1433 :laugh:
Security is not usually a problem if you don't allow every user to be an elevated account.
More info here on using ports for SQL server
https://msdn.microsoft.com/en-gb/library/cc646023.aspx#BKMK_ssde
https://msdn.microsoft.com/en-GB/library/ms177440.aspx
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 24, 2016 at 10:39 am
Perry Whittle (6/23/2016)
Microsoft do not recommend changing the port on a default instance, leave it at 1433.Why do you want to change it
where is that stated Perry (just interested)
---------------------------------------------------------------------
June 27, 2016 at 6:03 am
By having SQL Server listen on a Non Default port it makes it makes it harder for an outsider that compromises your Network to sniff out SQL Servers in your environment.
I have never seen Microsoft state to NOT change the default port it listens on.
Actually I wish they would have that a configurable option when you go to Install SQL Server. Have 1433 setup as the default but allow the person installing it to change it to another port like as we have the ability to change the default drives and folders system files get installed to.
June 27, 2016 at 7:27 am
I cant find the article, As far as I recall a default instance does not support dynamic ports, it is possible to use a static port other than 1433 but there is an amount of configuration required. This link, though a little old, details port requirements.
https://support.microsoft.com/en-us/kb/823938
As I said, it's more important to secure the server so that even if connection attempts are made that they are met with the appropriate security checks from the server. Connecting to instance FRED when SQL Server authentication is enabled with the SA password set to "Smith" is going to cause issues whatever port you listen on!
Having the NTFS file system unsecured will further allow prying eyes to read log files and find port numbers in use too.
Remember, 70% of your attacks will likely come from within your network, just my 2 cents worth
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply