Solved!
Go to Solution03 Service Unavailable
Good day! I deployed a farm based on Windows Server 2019 in the RDS test environment. All components were installed successfully, but when I try to open the address with the rdweb collections, I get a 503 Service Unavailable error, I find out that this is a problem of the pool responsible for this, but it has a constant status works, where to dig and what's the problem? I do everything on Dell Power Edge Server R740
DELL-Marco B
Moderator
•
3980 Posts
910
0
Posted July 3rd, 2020 07:00
Hello,
it seems that this is more a software problem, we only support PowerEdge hardware. Do you have some issue regarding the hardware PowerEdge R740? It is up and running?
Thanks
MarcoDELL- Marco B
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#IWork4Dell
Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!
Spanjokus
1 Rookie
•
9 Posts
874
0
Posted July 5th, 2020 05:00
Hi everybody. I spent the whole weekend over the solution to this problem, and yet I solved it.
Since my service was on virtual machines, I made snapshots and put out everything. Then I just reinstalled everything from scratch, the systems and roles, and as a result, the error did not reproduce, as it turned out Dell's physical servers had nothing to do with it. But I was wondering what was the cause of the previous problem, in the end it turned out that the service of a certain Dell utility, which remained after the P2V server virtualization, was spinning on port 443, I deleted it, deleted the port ACL. I found this hint on a site with methods to eliminate 503 errors. Maybe this will help someone not to spend two days looking for a problem.