No luck.  These are all clean installs with nothing other than SQL 2012 
(11.0.5343).  Trying CU8 now as well.  Otherwise will try different ideas this 
weekend.

Sent from Mail for Windows 10



From: Kelley, Matthew
Sent: Friday, November 13, 2015 9:08 AM
To: [email protected]
Subject: RE: [mssms] Tcp is enabled and set to Static port.
Try to flip them to dynamic (0) and then restart sql server service, then set 
back to static and cycle the service again. 

From: [email protected] [mailto:[email protected]] On 
Behalf Of Jay Parekh
Sent: Friday, November 13, 2015 9:45 AM
To: [email protected]
Subject: FW: [mssms] Tcp is enabled and set to Static port.

Just got back to try this again this AM after 2 week break (from lab) and still 
experiencing this issue if anyone has any insight.  Log file attached.
 

To: [email protected]
From: [email protected]
Subject: [mssms] Tcp is enabled and set to Static port.
Date: Mon, 2 Nov 2015 16:27:13 -0600
I am going nuts and think it’s something simple that I’m missing.  Done this 
several times on my home lab and clients with no issues but now on my newly 
build lab environment having this issue.  I am installing vNext TP3.  I tried 
the CM2012 R2 Pre-Req and same issue.
 
Every pre-req fails around the SQL TCP Port check “Configuration Manager 
primary site and central administration site require SQL Server Tcp is enabled 
and set to Static port.”
 
I have Server 2012 R2 and SQL 2012 SP2 Standard installed.  This is a very 
clean environment (not building from VM templates, copied other VMs, etc.) and 
only the required roles & features are installed on the VM (Bit, SUS, etc.).
 
Just for sanity check, I started again with a clean VM (fresh off the ISO) and 
only installed what I need as pre-reqs in roles/features and then lastly SQL 
2012.  Then I have attempted CM VNExT TP3 install with the same result.  Also 
check TCP is enabled in SQL Config Mgr and Dynamic ports are blank on all IPs, 
etc.
 
Sent from Mail for Windows 10


**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be 
used for urgent or sensitive issues 






Reply via email to