Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more. anyone ? Tweet Have just deployed a new installation of SEP 12.1.3 onto a new Windows Server 2012. Seemingly after this SEPM will no longer login ?
I'll get hold of that log file and post if you think it will help. Only change was installing Remote Access role onto Windows Server 2012....has this broken SEPM somehow ? When that is completed then go in and try to log into the console. 0 Tabasco OP Mithun Sanghavi (Symantec) Jul 22, 2013 at 11:06 UTC Brand Representative If the database is unavailable or cannot be accessed, you cannot log in.
Could you please let us know how are you trying to login to the SEPM? Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. You may get a better answer to your question by starting a new discussion. TECH134782 March 8th, 2016 http://www.symantec.com/docs/TECH134782 Support / Error when logging to Symantec Endpoint Protection Manager: "Failed to connect to server".
Is that via Java console or you are on the local server machine and then trying to login to the server? Secondly, in case of Symantec Endpoint Protection 12.1, check if the "Symantec Endpoint Protection Manager" and "Symantec Embedded Database" services are started and running under services.msc If they are already running, Sepm Failed To Connect To The Server Did this article resolve your issue? The Java Virtual Machine Exited With A Code Of 1 http://www.symantec.com/docs/TECH134782Errror Failed to Connect to the Server when using the Symantec Endpoint Protection Manager Remote Console 12.1 http://www.symantec.com/docs/TECH160378 Error: "Failed to connect to the server" after migrating to Endpoint Protection
Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more. http://chatflow.net/failed-to/ultravnc-failed-to-connect-to-server.html Something that this wizard does breaks SEP 12.1.3 Manager And simply uninstalling the Remote Access role doesn't fix the problem as I have already tried that. Thank you for your feedback! Hope that helps!!
Submit a False Positive Report a suspected erroneous detection (false positive).
Migrate 5 Windows XP machines to new Windows 7 machines, install a new router, upgrade wireless network from G to N. Provide feedback on this article Request Assistance Print Article Products Subscribe to this Article Manage your Subscriptions Search Again Situation The Symantec Endpoint Protection Manager (SEPM) login process bar hang for This will change directories to the folder containingdbsrv11.exe.
Apparently Remote Access has changed completely in Windows Server 2012.. ..probably why it has screwed up my SEPM I guess.. Operating Systems: Windows Server (2003/2008) Discussion Filed Under: Security, Endpoint Protection Small Business Edition, Configuring, Error messages, Installing, Windows Server (2003/2008) Comments RSS Feed Comments 10 Comments • Jump to latest Secondly try running the Symhelp on the machine to check for issues. Solution Solutions provided as per cause: Verify the correct server name/port entered into the console and try again.
Have tried a repair, that didn't work. Anyway, following a restart SEPM still doesn't logon, still 'Failed to connect to server' Did a repair and re-run configuration.. OR If theSymantec Endpoint Protection Managerservice fails to start then runManagement Server Configuration Wizardin order to log in to theSymantec Endpoint Protection Manager. http://chatflow.net/failed-to/failed-to-connect-to-the-www-server-fw-1.html If it staysstartedthen go ahead and log into theSymantec Endpoint Protection Managerand everything should now be working properly.
Mithun Sanghavi Symantec Employee Technical Support Accredited SEPM 12.1.3 - on Windows Server 2012 - Failed to connect to server - Comment:11 Oct 2013 : Link Hello, Symantec Endpoint Protection 12.1.3001 Everything was working OK up until adding the Remote Access role, SEP 12.1.3 having been previously installed and functioning perfectly Following the required restart all was still OK, but after running ClickStart, click onRunand Type “Services.MSC” then clickOKand start theSymantecEmbedded DatabaseService Start theSymantec Endpoint Protection Managerservice. Rafeeq SEPM 12.1.3 - on Windows Server 2012 - Failed to connect to server - Comment:10 Oct 2013 : Link can you please post the smc-server0.log found under sepm logs folder.
Join the community Back I agree Powerful tools you need, all for free. Force the recreation of sem5.log. This would assist me to answer your query. Dental Practice - Montana Dental, PLLC Design, construct, and implement network to support a completely digital Dental practice.
This will change directories to the folder containingdbsrv12.exe. Seems Backup Exec 2012isn't.. Stylax SEPM 12.1.3 - on Windows Server 2012 - Failed to connect to server - Comment:14 Oct 2013 : Link Guys, I've just tried the exact same thing on another brand by Edward9929 on Oct 4, 2013 at 10:59 UTC 1st Post | Symantec 0Spice Down Next: Symantec Mail Security: which email should I release?
No Yes Products Products Home Threat Protection Advanced Threat Protection Endpoint Protection Endpoint Protection Cloud IT Management Suite Email Security.cloud Data Center Security Blue Coat Products Information Protection Data Loss Prevention Join the community Back I agree Powerful tools you need, all for free. No Yes Home symantec endpoint protection manager-failed to connect server by karthick s on Dec 22, 2011 at 1:09 UTC 1st Post | Symantec 0Spice Down Next: Symantec SafeWeb is marking However, for compatibility with 1.6, the SEPM must be RU6 or later.