Might be worth throwing this on uservoice to be added to the docs? RIP smsdocs.
Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of JONES, RICK J Sent: Wednesday, January 4, 2017 7:22 PM To: [email protected] Subject: [mssms] RE: SOLVED! SQL Server Tcp is enabled and set to Static port Don’t you just hate it when you step on your own shoelaces! Rick J. Jones Wireless from AT&T Domestic Desktop Application Management (206) 419-1104 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Duncan McAlynn Sent: Wednesday, January 04, 2017 4:15 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: SOLVED! SQL Server Tcp is enabled and set to Static port It pains me to admit this publicly, but I did solve the riddle earlier today. In my haste, I had apparently mounted the wrong ISO image for my VM and accidently installed SQL Server 2014 *32-bit* edition, which SCCM obviously doesn’t like, but also doesn’t give any indication that it’s the cause of the problems either. #smh Duncan McAlynn, Solutions Director, Americas HEAT Software M: +1.512.391.9111 | [email protected]<mailto:[email protected]> HEAT Software | 490 N McCarthy Blvd. Suite 100 | Milpitas, CA 95035 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kamerman, Sol Sent: Wednesday, January 04, 2017 13:38 To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: SQL Server Tcp is enabled and set to Static port Is the ‘Listen All’ option set to ‘Yes’ Under SQL SERVER NETWORK CONFIG -> Protocols FOR ***** Change to NO if it is. I looked through my old notes and that is one of the settings I had to change because I had multiple NICS and the comms were messed up. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of s kissel Sent: Wednesday, January 4, 2017 2:25 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Re: SQL Server Tcp is enabled and set to Static port Is the SQL Browser service started? ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Duncan McAlynn <[email protected]<mailto:[email protected]>> Sent: Wednesday, January 4, 2017 12:55:28 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: SQL Server Tcp is enabled and set to Static port See my last bullet item in the Configuration. Duncan McAlynn, Solutions Director, Americas HEAT Software M: +1.512.391.9111 | [email protected]<mailto:[email protected]> HEAT Software | 490 N McCarthy Blvd. Suite 100 | Milpitas, CA 95035 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kamerman, Sol Sent: Wednesday, January 04, 2017 12:51 To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: SQL Server Tcp is enabled and set to Static port One more thing… When I had this setup, I had to make the SCCM server object an ADMINISTRATOR on the SQL box. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Duncan McAlynn Sent: Wednesday, January 4, 2017 12:32 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] SQL Server Tcp is enabled and set to Static port I’m about to go mental over this one! Any help would be greatly appreciated, y’all! Thanks in advance. Configuration: ? New CB1606 site installation on CM01 ? Remote SQL 2014 default instance on SQL01 ? Both servers are Windows Server 2012 R2. (Fully patched) ? *ALL* SQL IPs are enabled and configured for port 1433 ? Setup executed as a Domain Admin ? CM01$ is local admin on SQL01 and SysAdmin in SQL Issue: This prerequisite checker fails on the SQL validation. The exact error message is: “Configuration Manager primary site and central administration site require SQL Server Tcp is enabled and set to Static port.” Relative Log Entries from ConfigMgrPreReq.log: <01-04-2017 10:47:35> SQL01.patchlink.corp; SQL Server version; Passed <01-04-2017 10:47:35> ERROR:Can not get sql instance regkey. <01-04-2017 10:47:35> ERROR:Failed to get Sql edition, Sql Server:SQL01.patchlink.corp, instance:. <01-04-2017 10:47:35> SQL01.patchlink.corp; SQL Server Edition; Passed <01-04-2017 10:47:35> INFO: Checking Tcp is enabled to Static port, SQL Server:SQL01.patchlink.corp, Instance:. <01-04-2017 10:47:35> ERROR: SQL TCP is not enabled. <01-04-2017 10:47:35> SQL01.patchlink.corp; SQL Server Tcp Port; Error; Configuration Manager primary site and central administration site require SQL Server Tcp is enabled and set to Static port. <01-04-2017 10:47:35> INFO: Checking if SQL Server memory is limited. <01-04-2017 10:47:35> WARN: SQL Server memory is set to unlimited. <01-04-2017 10:47:35> SQL01.patchlink.corp; Configuration for SQL Server memory usage; Warning; SQL Server is configured for unlimited memory usage. You should configure SQL Server memory to have a maximum limit. <01-04-2017 10:47:35> INFO: Checking if SQL Server memory is configured to reserve minimum memory. <01-04-2017 10:47:35> INFO: Installing the central administration site or primary site, requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory. <01-04-2017 10:47:35> WARN: SQL Server minimum memory is 8 MB. <01-04-2017 10:47:35> SQL01.patchlink.corp; SQL Server process memory allocation; Warning; Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see http://go.microsoft.com/fwlink/p/?LinkId=233759. <01-04-2017 10:47:35> SQL01.patchlink.corp; Case-insensitive collation on SQL Server; Passed <01-04-2017 10:47:35> INFO: Check Machine FQDN: <SQL01.patchlink.corp>. <01-04-2017 10:47:35> INFO: getaddrinfo returned success. <01-04-2017 10:47:35> SQL01.patchlink.corp; Validate FQDN of SQL Server Computer; Passed <01-04-2017 10:47:35> INFO:CheckSupportedFQDNFormat <SQL01.patchlink.corp> <01-04-2017 10:47:35> INFO: NetBIOS <SQL01> <01-04-2017 10:47:35> SQL01.patchlink.corp; Primary FQDN; Passed Duncan McAlynn, Solutions Director, Americas HEAT Software M: +1.512.391.9111 | [email protected]<mailto:[email protected]> HEAT Software | 490 N McCarthy Blvd. Suite 100 | Milpitas, CA 95035 The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
