Wondering if anyone has ideas here. I redid my entire lab from scratch (DC, etc.). Another fresh VM with Server 2012 R2 and only SQL installed with requires Windows roles/features. During CM pre-req, same issue! I installed SQL 2014 this time as well but same issue. Tried 2012 before too.
Only difference on these new VMs is using Hyper-V on Windows 10. My previous working labs were on 2012 or Win 7 hypervisor. Sent from Mail for Windows 10 From: Jay Parekh Sent: Monday, November 2, 2015 4:27 PM To: [email protected] Subject: Tcp is enabled and set to Static port. 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
