Home > Symantec Endpoint > Symantec Endpoint Protection Unable To Connect To The Server Specified

Symantec Endpoint Protection Unable To Connect To The Server Specified

now I need to move my replication server to a new server. The Home, Monitors, and Reports pages display a continuously loading progress bar, without displaying any content. In the ODBC tab, click Test Connection. Provide feedback on this article Request Assistance Print Article Products Related Articles Subscribe to this Article Manage your Subscriptions Search Again Situation Symantec Endpoint Protection Manager (SEPM) 12.1 is logging errors

Click Next. Check that the Symantec Endpoint Protection firewall or third-party firewall does not cause any network problems. In the left column, select Connection Status. You can run the tool remotely or save it and then run it on the client computer.

Click OK. site already exists do you want to replace with a new site and when said yes i see replicating database and this time is said failed to connect to server. Submit a False Positive Report a suspected erroneous detection (false positive).

Information for: Enterprise Small Business Consumer (Norton) Partners Our Offerings: Products Products A-Z Services Solutions Connect with us: Support

Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. Next.. Test the ODBC connection. Note: Ensure that the Computer Browser Service is running on the server.

No Yes logo-symantec-dark-source Loading Your Community Experience Symantec Connect You will need to enable Javascript in your browser to access this site. © 2016 Forum Themes: Classic Mobile Original Welcome ! Submit a Threat Submit a suspected infected fileto Symantec. JVM Option 0 specifies the minimum size of the Java Heap JVM Option 1 specifies the maximum size of the Java Heap. If the ping command does not return the correct address, verify the DNS service for the client and check its routing path.

In the Replication Information panel, type values in the following boxes:Replication server name -The name or IP address of the remote Symantec Endpoint Protection ManagerReplication server port -The default value is In the SEPM, export the communication file (sylink.xml) from the client group to which you want the client computer to connect. There may be other errors. Look on the client to see if the client connects to the management server You can check several important connection data values in the client.

In the Password field, type the password for the database. Click OK. Check system requirements Ensure that both the client and the management server meet the minimum or recommended system requirements. If the management server runs the remote SQL database, perform the following actions: Verify that you have specified a named instance when you installed and configured Symantec Endpoint Protection Manager.

Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. this contact form This password is the one that you entered for the database when you installed the management server. Troubleshoot management server and console or database communications If you have a connection problem with the console or the database, you may see one of the following symptoms: The management server If you can detail what you are doing with the initial steps in the wizard I'm sure we can get you up and running :) Regards Alan #2 simon

You can use the server IP address in place of the computer name. You should also check network connectivity. In the Windows Registry, turn on debugging in the client under HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\smc_debuglog_on. have a peek here If you use the tool on the command line, read the SylinkDrop.txt file for a list of the tool's command parameters.

If you cannot log in to the management server's remote console, or if you see an out-of-memory message in the smc-server log, you may need to increase the heap size. View the connection status data values. Close Regedit.

In the Database tab, in the Server name field, type <\\servername\instancename>.

Create a SymAccount now!' "Unable to connect to the server specified" error during the replication of Symantec Endpoint Protection Manager TECH106224 November 29th, 2011 Support / "Unable to connect to i have also upgraded to SEPM version 12.1.4a currently working with no issues. Select the number of clients you expect the server to manage, and then clickNext. Click Next.

To check the inbox logs on the management server: On the management server, under HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SEPM, set DebugLevel=3. References KB 2008061813510348 Tuning the Performance of the Symantec Endpoint Protection Manager console KB 2009061219002148 Error: Keystore was tampered with, or password was incorrect error in Catolina.out log Technical Information The Type ping and the computer name of the management server, and then press Enter. Check This Out Check that the management server is not running multiple versions of PHP You can check whether the management server runs multiple software packages that use different versions of PHP.

Error in the Catalina.out log: NFO: Initializing Coyote HTTP/1.1 on http-9090 May 12, 2009 12:19:58 PM org.apache.coyote.http11.Http11BaseProtocol init SEVERE: Error initializing endpoint Keystore was tampered with, or password was incorrect Check for any network problems Verify that there are no network problems by checking the following items: Test the connectivity between the client and management server first. Check the client's routing path. In the left pane, click Debug Logs.

Submit a False Positive Report a suspected erroneous detection (false positive).

Information for: Enterprise Small Business Consumer (Norton) Partners Our Offerings: Products Products A-Z Services Solutions Connect with us: Support In the right pane, under Symantec Endpoint Protection, click Edit Debug Log Settings. The Home, Monitors, and Reports pages display an HTTP error. The scm-server log is typically located at C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\scm-server-0.log.

Error "Retrieval of local changed data for replication requested by remote server x.x.x.x failed during retrieving data! [reason: Failed to retrieve Metadata - Java heap space]" in Admin > Server > Disable the Apache HTTP server Access log when you are done. All Forums >> [Security and Patching] >> AntiVirus Products and Best Practices Forum MenuPhoto GalleriesLog inRegistration / Sign up RSS FeedThread Options View Printable PageThread Reading Mode Installing a SEPM replication Close Login Didn't find the article you were looking for?