![symantec endpoint manager failed to connect to server symantec endpoint manager failed to connect to server](http://lh3.ggpht.com/_A3o0EjLYCNg/TW3dXpbTqiI/AAAAAAAAE4c/e3Aocmba60w/image_thumb[1].png)
This Web site uses the same credentials as the SEPM Console. If the SEPM Web server service is running, and not blocked by a firewall, you will be prompted to log in to the Reporting Web site. Change the Reporting port to an unused port on the SEPM computerīrowse to the SEPM Reporting Web site ( by default).In the Management Server Configuration Wizard, select Reconfigure the management server, ensure Use a recovery file to restore communication with previously deployed clients is checked, and click Next.Symantec Endpoint Protection 14.0. To correct the port conflict, follow the steps below on the SEPM server: If the Symantec Endpoint Protection Manager service fails to start then run Management Server Configuration Wizard in order to log in to the Symantec Endpoint Protection Manager. Go to the Start menu, and open inetcpl.cpl. When you reset these internet settings, it may delete your browser temporary files, cookies, browsing history, and online passwords.
![symantec endpoint manager failed to connect to server symantec endpoint manager failed to connect to server](https://content.spiceworksstatic.com/service.community/p/post_images/0000064316/54bc6126/attached_image/client2.png)
If this command shows any process listening on the SEPM Web server port, re-run the Management Server Configuration Wizard, and reconfigure the SEPM Reporting server port. Exit all open programs, including the web browser.If the Symantec Endpoint Protection Webserver service is stopped and fails to start, confirm that no other process is listening on the SEPM Reporter Web site port (default: 8445). BTW, this problem is common if you have more than Native Client installed (certainly different versions, eg one copy is v10, another one, v11).
#Symantec endpoint manager failed to connect to server upgrade
Hello, We had the same issue when we upgrade to CB1706.It was first brought up by our security team who saw a bunch of failed logins to our SQL server where the username was the machine account of our site servers. If the STATE returned by this command equals "4 RUNNING", log off and log back on to the SEPM Console. I think SteveNguyen is giving a very good way to troubleshoot the issue. Attempting to manually start the Endpoint Protection Manager services results in the following message: 'Windows could not start the Symantec Endpoint Protection Manager service on Local Computer. Since updating from ConfigMgr 1702 to 1706 we are seeing the below errors on some of our site systems.This command should return a STATE value of "2 START_PENDING".
![symantec endpoint manager failed to connect to server symantec endpoint manager failed to connect to server](https://techdocs.broadcom.com/content/dam/broadcom/techdocs/symantec-security-software/endpoint-security-and-management/endpoint-protection/content/images/sqlserver_enabled.png)