Jan 26 2020 02:31 AM
Existing Environment-
We have Lync server 2013 with pool enterprises with 3 Front-end.
I just upgraded from Lync 2013 to Skype for Business 2019. (the new Existing Environment on windows server 2019 and we doing migration side by side ).
Everything seems to be working fine except I cannot log into the Control Panel from anywhere the web interface (PoolName/CSCP) or from the app : ”skype for business control panel”.
When I connect I get - Error 503 service unavailable.
Also the new MACP (the new control panel with Html 5 not working).
Thanks for the help!
Jan 26 2020 08:56 AM
Hi @Elazaro,
503 seems to be backend related.
Jan 30 2020 04:13 AM
Hi Erik,
Jan 30 2020 12:09 PM - edited Jan 30 2020 12:11 PM
Hi @Elazaro ,
to me this seems like the IIS configuration was messed up anyhow.
Please note, the above are just some ideas and thoughts and might be incomplete. You might want to open a support case at Microsoft Support for more in-depth support.
Feb 09 2020 02:44 AM
Hi Erik,
I want to update you on the changes we made yesterday.
We Removed the Pool from The Topology builder and cleaned the SQL Database.
We installed new servers (Server 2019) and create new pool in Topology builder.
We didn’t install CU, we want clean environment. (So now we don’t have the MACP).
After we finished we try to open the CSCP and the issue 503 service unavailable still happening.
I checked the logs in CLSloger.
But I don't see the Web Infra logs.
They are empty.
I want to clarify that the issue his with all the application pools in IIS. (503 service unavailable).
Feb 10 2020 11:16 PM
Hi @Elazaro,
that's a very odd behaviour especially that you set up a new pool including fresh servers.
Just some basic things I'd re-check although you probably have done that already.
Add-WindowsFeature RSAT-ADDS, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, Web-Dyn-Compression, NET-WCF-HTTP-Activation45, Web-Asp-Net45, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Windows-Identity-Foundation, Server-Media-Foundation, Telnet-Client, BITS, ManagementOData, Web-Mgmt-Console, Web-Metabase, Web-Lgcy-Mgmt-Console, Web-Lgcy-Scripting, Web-WMI, Web-Scripting-Tools, Web-Mgmt-Service
Feb 17 2020 12:13 AM
Thanks for the response, Erik.
I checked the applications and virtual services all configured correctly.
no, the Cscp of skype 2019, not available.
only the old cscp Lync 2013 ( different environment in the pool).
no, all get error 503.
Already checked.
Add-WindowsFeature RSAT-ADDS, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, Web-Dyn-Compression, NET-WCF-HTTP-Activation45, Web-Asp-Net45, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Windows-Identity-Foundation, Server-Media-Foundation, Telnet-Client, BITS, ManagementOData, Web-Mgmt-Console, Web-Metabase, Web-Lgcy-Mgmt-Console, Web-Lgcy-Scripting, Web-WMI, Web-Scripting-Tools, Web-Mgmt-Service
Feb 24 2020 02:05 PM
Hi Erik,
thanks a lot for your help.
the issue solved by install 3 new Servers 2016.
and install in the existing pool 3 new FE and Remove the (Old 2019 from the pool).
it seems like the server 2019 with the last update was the issue.
Feb 25 2020 05:56 AM
Jan 26 2021 06:47 AM
just update -
this issue happened if you are installing Windows Admin Center 2019 on your Windows Server 2019 machine.
admin center was installed on my Server.
I removed the Admin Center before the installation of skype.
but this not fixes the issue.
because some who port 443 still used.
I previously had Windows Admin Center installed, and now nothing else can use the same TCP/IP port
Manually run these two commands in an elevated command prompt:
Microsoft adds this note lately -
more details -
If you are installing Windows Admin Center 2019 on your Windows Server 2019 machine, it will prompt you for a port to listen on. There's a likelihood you might choose port 443, but if that machine has Skype for Business Server 2019 installed on it, or is going to have Skype for Business Server 2019 installed on it, then you must choose a different port number.
Why is this the case? If Windows Admin Center 2019 is running on port 443, you will not be able to connect to the server using the Skype for Business Control Panel, nor will you be able to connect to any internal web service running on the server (Address Book Web Service, Autodiscover Service, WebTicket Service, etc). In fact, you will not be able to connect to any Internal Web Service URL. Please choose a different port, in the event you need or want to put Windows Admin Center 2019 on a server with Skype for Business Server 2019.