June 21, 2016 at 10:45 am
I'm trying to test changing the port on a default instance to something other than 1433. I don't want to create an alias and haven't had any luck changing the global default port within the Client Protocols. I've also tried setting the TCP Port to a different value but the service won't restart after that. Is there another way to go about it?
June 21, 2016 at 10:50 am
Hi RonMexico,
What is the error you're getting when the service does not start ?
June 21, 2016 at 11:33 am
The error I get in SSCM is "The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details."
The one I see in the event logs that might be of help is
"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."
June 21, 2016 at 4:24 pm
OK. What do you see in the FDLAUNCHERRORLOG files in the following default directory ?
Program Files\Microsoft SQL Server\MSSQL12.MSSQLServer\MSSQL\log
You can open them with Notepad.
June 22, 2016 at 5:47 am
Sorry for the delayed response. I'm not seeing anything in those four files that show some kind of error and none have the timestamp of when I tried to restart the service.
2016-03-18 13:41:21.333MSSQLFDLauncher service received control message.
2016-03-18 13:41:21.334MSSQLFDLauncher service successfully started.
2016-03-18 13:41:21.437MSSQLFDLauncher service successfully launched FDHost.exe
2016-03-18 14:10:27.325MSSQLFDLauncher service stopped.
June 22, 2016 at 6:13 am
RonMexico (6/21/2016)
...haven't had any luck changing the global default port within the Client Protocols....
No, that's for client applications on the server. Go to SQL Server Network Configuration -> Protocols for MSSQLSERVER, right-click on TCP/IP, choose Properties and click on the IP Addresses tab. Go to the IPAll section and type the port number in the TCP Port field. You'll need to restart SQL Server (I think it prompts you when you make the change).
John
June 22, 2016 at 7:42 am
I've tried that as well. That's what I do when I get the error message
"The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details."
June 22, 2016 at 7:46 am
From what you quote from the event log, it sounds as if it's only the Fulltext service that isn't starting. Are you saying SQL Server isn't starting as well? Is there anything in the SQL Server errorlog?
John
June 22, 2016 at 7:47 am
Is anything else currently using that port number? Try changing it (the one on your instance that won't start) to something else maybe.
June 22, 2016 at 8:03 am
John - Correct, SQL Server is not starting as well. I don't see anything in the SQL Server errorlog that shows any errors and it even indicates that it is trying to start using the new (non-default) port number I give it.
Beatrix - I've testing with a couple port numbers and have the same result each time.
I failed to mention in my original post that this is on a clustered environment. I don't know if that makes a difference or not.
June 22, 2016 at 8:09 am
Please will you post the contents of the errorlog, then? You can redact the server name and any other details that you don't want the rest of the world to know.
John
June 22, 2016 at 8:31 am
2016-06-22 09:03:03.26 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:03:03.26 Server UTC adjustment: -5:00
2016-06-22 09:03:03.26 Server (c) Microsoft Corporation.
2016-06-22 09:03:03.26 Server All rights reserved.
2016-06-22 09:03:03.26 Server Server process ID is XXXXX.
2016-06-22 09:03:03.26 Server System Manufacturer: 'HP', System Model: 'ProLiant DL380 G6'.
2016-06-22 09:03:03.26 Server Authentication mode is MIXED.
2016-06-22 09:03:03.26 Server Logging SQL Server messages in file 'X:\XXXXXX\XXXXXXXXXXXXXXXX\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2016-06-22 09:03:03.26 Server The service account is 'XX\XXXXXXX'. This is an informational message; no user action is required.
2016-06-22 09:03:03.26 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:03:03.26 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
2016-06-22 09:03:03.86 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:03:03.86 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:03:03.86 Server Detected 49141 MB of RAM. This is an informational message; no user action is required.
2016-06-22 09:03:03.86 Server Using conventional memory in the memory manager.
2016-06-22 09:03:04.18 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2016-06-22 09:03:04.26 Server The maximum number of dedicated administrator connections for this instance is '1'
2016-06-22 09:03:04.26 Server This instance of SQL Server last reported using a process ID of XXXXX at 6/22/2016 9:01:33 AM (local) 6/22/2016 2:01:33 PM (UTC). This is an informational message only; no user action is required.
2016-06-22 09:03:04.26 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:03:04.26 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:03:04.31 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:03:04.31 Server Lock partitioning is enabled. This is an informational message only. No user action is required.
2016-06-22 09:03:04.35 spid8s Starting up database 'master'.
2016-06-22 09:03:04.39 Server CLR version v4.0.30319 loaded.
2016-06-22 09:03:04.43 spid8s 10 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2016-06-22 09:03:04.45 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:03:04.45 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:03:04.51 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:03:04.62 spid8s Resource governor reconfiguration succeeded.
2016-06-22 09:03:04.62 spid8s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2016-06-22 09:03:04.62 spid8s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2016-06-22 09:03:04.66 spid8s SQL Trace ID 1 was started by login "XX".
2016-06-22 09:03:04.66 spid8s Server name is 'XXXXXXXXXXXXXXX'. This is an informational message only. No user action is required.
2016-06-22 09:03:04.66 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:03:04.75 spid16s A self-generated certificate was successfully loaded for encryption.
2016-06-22 09:03:04.82 spid17s Error: 9954, Severity: 16, State: 1.
2016-06-22 09:03:04.82 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:03:04.83 spid20s Starting up database 'XXXXX'.
2016-06-22 09:03:04.83 spid19s Starting up database 'msdb'.
2016-06-22 09:03:04.83 spid12s Starting up database 'mssqlsystemresource'.
2016-06-22 09:03:04.87 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:03:04.90 spid16s Server is listening on [ XX.XXX.XXX.XX <ipv4> 1433].
2016-06-22 09:03:04.90 spid16s Started listening on virtual network name 'XXXXXXXXXXXXXXX'. No user action is required.
2016-06-22 09:03:04.90 spid16s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2016-06-22 09:03:04.90 spid16s Server local connection provider is ready to accept connection on [ \\.\pipe\$$\XXXXXXXXXXXXXXX\sql\query ].
2016-06-22 09:03:04.91 spid16s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2016-06-22 09:03:04.91 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:03:04.96 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/XXXXXXXXXXXXXXX.XX.XXXX-XXX.com ] for the SQL Server service.
2016-06-22 09:03:04.96 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/XXXXXXXXXXXXXXX.XX.XXXX-XXX.com:1433 ] for the SQL Server service.
2016-06-22 09:03:05.00 spid12s Starting up database 'model'.
2016-06-22 09:03:05.02 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:03:05.05 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:03:05.09 spid12s Clearing tempdb database.
2016-06-22 09:03:05.38 spid12s Starting up database 'tempdb'.
2016-06-22 09:03:05.40 Server Software Usage Metrics is disabled.
2016-06-22 09:03:06.88 spid26s The Service Broker endpoint is in disabled or stopped state.
2016-06-22 09:03:06.88 spid26s The Database Mirroring endpoint is in disabled or stopped state.
2016-06-22 09:03:06.89 spid26s Service Broker manager has started.
2016-06-22 09:03:16.46 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:03:16.53 spid8s 0 transactions rolled back in database 'XXXXXX' (5:0). This is an informational message only. No user action is required.
2016-06-22 09:03:16.88 spid8s Recovery is complete. This is an informational message only. No user action is required.
June 22, 2016 at 8:43 am
I notice you're back to 1433. Does it work like that, or does it fail now whatever you do? Since you're on a cluster, is the NETBIOS name the same every time? When SQL Server stops, does it initiate a failover, or does it just stop? I don't really know where I'm going with any of this - I'm afraid I'm running out of ideas!
John
June 22, 2016 at 8:55 am
I appreciate all of the help, John! 1433 works just fine so I went back to that to at least have the instance running. The NETBIOS is the same every time regardless of a failed or successful start of SQL Server. SQL Server will attempt a failover after it stops on the primary, but then also fails on the secondary since it is trying to use the port I changed it to on the primary. I'm at a complete loss so I'm just fishing for any ideas that might help.
June 23, 2016 at 2:02 am
Is it possible that it's failing because the LooksAlive and IsAlive checks can't connect? Please will you post the errorlog for when it doesn't start properly? The SQL Server Browser service isn't going to be any help here because you have a default instance.
John
Edit - changed "hearbeat" to "LooksAlive and IsAlive checks".
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply