Hi all, I can't get past this installation step trying to install SP 2013 on a WIN 2012r2 server running SQL 2014 server. The install step creates the SP config file on the SQL server, but then fails with a port error:

Relevant error text from the log file: 

A SocketException was thrown with SocketError ConnectionRefused Connect has been refused for port 24181, so we will consider this a free port Adding port to the exclusion list so it is not chosen again during this run...

I've tried almost everything I can google... setting time out to 3600 etc. but nothing seems to help. Wondering what to do: uninstall SharePoint Server and try again? Sounds like a bad idea. What say you? thx!

Can you try rerunning the configuration wizard

Have done so many times, with various google remedies applied. Each time I have to delete the SQL config file it creates. This thing is a beast. I guess I will try another version, and / or a complete reinstall. I also have SP 10 available, but I don't know if that work for the end game at play: MS Project Server 2013. Thx! 

Have you installed SP May 2014 Cumulative Update?

thx Sharepointalltheway, no, have not done but good news, I uninstalled completely and reinstalled, and now I am at the point where the configuration site was created in IIS. The files don't run yet, but at least I got past the initial problem. Other websites in IIS run fine, so it's probably some kinda permission error (all SP pages throw a 503). Also, these tremors here in Nepal are wrecking my concentration, and I forgot to load SP1 on top of the install before I tried it. I figure I will do that, then the SP May 2014 Cumulative Update and perhaps that will sort things out. Thx! 

UPDATE: I am getting these: 

PHOENIXSERVER

5139

Warning

Microsoft-Windows-WAS

System

5/23/15 8:50:18 PM

A listener channel for protocol 'http' in worker process '6752' serving application pool 'SharePoint Central Administration v4' reported a listener channel failure.  The data field contains the error number.

Have you installed SP May 2014 Cumulative Update?

• Marked as answer by Jigs Gaton 4 hours 28 minutes ago

Have you tried running it in the SharePoint PowerShell? Open SharePoint management shell as an administrator and then use the following:

Note change info to your environments info

psconfig -cmd configdb -create -server "SQL\Instance" -database "SharePoint_Config" -passphrase -admincontentdatabase "WSS_AdminContentDB" -user Contoso\Spadmin -password password

Can you check the log file generate for exact set of errors . It will be helpful ..  Else paste the error portion over here . It would be helpful

thx Jcollinsks  - now the Sharepoint Products Configuration Wizard runs fine (brings up a non-web dialog box), but [servername]:[port number] still not working. However, there are dozens of KBs downloading thru Windows Update still, even more after SP update was applied. I'll report back after all that settles down. PS. Your Powershell command is just for the Sharepoint Products Configuration Wizard, no? 

Well, if you mean this: ubersrv2013-kb3039780-fullfile-x64-glb.exe, then no, I tried, and I get this: 

But SP1 update installed ok. Now, with all the updates applied (dozens of farm-related ones), the configuration wizard gets to the point where it wants to launch a website [servername:portname] but fails with 

Service Unavailable

Okay, I think we can close this out now. The fix for 503 errors after configuration install is documented on the web as: 

Goto IIS manager ->Application  Pool, click 'SharePoint Central Administration v4' Right click Advanced settings, and set "Enable 32-bit applications" to "False"

I also had to do the same with the default pool as well! 

Anytime man.. take care

Jimmy,

Have you tried this:

https://www.simego.com/Help/DataSync/How-To-Fix-Could-not-load-file-or-assembly-Microsoft-IdentityModel-Version-3-5-0-0

Probably, this is a potential fix to your problem.

Thanks,

Rahul

thx for your reply, the fix was to completely uninstall sharepoint, reinstall it, apply SP1, then wait until all the other dozens of security KBs were applied, then re-run the wizard. Now the IIS-based configuration page comes up, but not yet fully functional. I'll just create a new ticket based on trying to debug that...