Exchange 2013 Broken PowerShell
Hi all:
I've installed Exchange 2013 with CU1 for a hybrid deployment. I'm currently running Exchange 2007 on premise. Yesterday I was configuring the Internal/External URLs for OWA and ECP. After that ECP stopped working and even the PowerShell console is giving
errors. No matter what command I type I get the following error:
An attempt was made to access a socket in a way forbidden by its access permissions.
Any ideas will be greatly appreciated.
Oh, the server is Windows 2008 R2.
April 10th, 2013 8:34pm
Any chance that another applications is trying to listen on tcp 80,443Dean Sesko
Free Windows Admin Tool Kit Click here and download it now
April 11th, 2013 6:15am
Hi
the symptom could occur if the replication service tries to use the ports that occupied by others, or by a malfunction NIC
Please restart the windows firewall service
Please reboot the problematic machine
Please run the ExBPA against the exchange server for health checkTerence Yu
TechNet Community Support
April 11th, 2013 10:23am
HI guys:
I stopped IIS and did a netstat -onab I found something listening on port 443:
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 4
Can not obtain ownership information
I can't figure out what service is using 443. Any ideas on how to proceed ? The PID 4 shows up as NT Kernel & System.
Free Windows Admin Tool Kit Click here and download it now
April 11th, 2013 4:44pm
Anything else installed on the server besides Exchange and the prerequisites?Dean Sesko
April 11th, 2013 4:53pm
Yes only Exchange.
Free Windows Admin Tool Kit Click here and download it now
April 11th, 2013 5:06pm
Will ExBPA work for Exchange 2013 ?
April 12th, 2013 12:29am
I've opened a case with MS.. I'll keep everybody posted to the results.
Free Windows Admin Tool Kit Click here and download it now
April 12th, 2013 7:09pm
Did you check to make sure that your default website and your backend website are not using the same ports?
Default should be on 80 and 443
Backend should be on 81 and 444Dean Sesko
April 13th, 2013 9:48pm