Home > Symantec Endpoint > Symantec Endpoint Protection Error Code 6

Symantec Endpoint Protection Error Code 6

No further interpretation of these codes is offered or available within the scope of this document. SEPM cannot push client package to itself with the Client Deployment Wizard Fix ID: 3626587 Symptom: On Windows servers, a local push deployment with the Client Deployment Wizard (CDW) in Symantec Solution: Fixed the logic to the query. Solution: Changed the API in use to prevent memory leaks when no user is logged in. http://mmonoplayer.com/symantec-endpoint/symantec-endpoint-protection-error-code-10.html

Both of these issues stem from an incorrect DNS query for remote IPs. Otherwise, the admin can cancel the installation, which rolls back. The Last Scan Time or Last Scanned Time for scheduled report is incorrect Fix ID: 3553048 Symptom: You see different times in two places for the last scan time and the RSA authentication for SEPM administrators stops working after upgrade Fix ID: 3636768 Symptom: After an upgrade to Symantec Endpoint Protection 12.1.5 (12.1 RU5), RSA authentication stops working.

Solution: Removed the logic of checking default data folder first, and added logic to check the existence of the current data path only before sending client data to Symantec Endpoint Protection Under Exceptions policy, cannot create Application Exception Fix ID: 3723791 Symptom: The application exception dialog box doesn't come up in the Exceptions policy. SmartDNS blocks all incoming DNS traffic to the client Fix ID: 3522496 Symptom: SmartDNS blocks all incoming DNS traffic to the client. logo-symantec-dark-source Loading Your Community Experience Symantec Connect You will need to enable Javascript in your browser to access this site. © 2016 Products Products Home Threat Protection Advanced Threat Protection Endpoint

Solution: Added a command-line password prompt for this specific case. Obtaining the latest version of Endpoint Protection or Network Access Control 11 Work-around Restart the computer, run LiveUpdate again, then you should be able to re-enable AutoProtect using the client Thank you for your feedback! The SQL user domain account does not have local logon user rights in the GPO, so BCP expectedly fails.

High memory usage from SymEFA databases Fix ID: 3046332 Symptom: Under certain circumstances, the Symantec Endpoint Protection client makes a full Insight (SymEFA) query, such as during the client heartbeat and If you need a specific error diagnosed, please provide a sample of the file and the accompanying log entry to Symantec Technical Support. Solution: Allowed hyphen and underscore characters as valid characters in a proxy server name. This issue also occurs with a new installation.

Forum Discussion by Dekich | 25 Nov 2016 | 11 comments 1 2 3 4 5 6 7 8 9 … next › last » Current search Search found 7,236 itemsHow SEP ADC doesn't log caller MD5 on 64-bit Windows Fix ID: 3670468 Symptom: Application and Device Control does not log caller MD5 for 64-bit Windows computers. SEPM login hangs or takes a long time during replication Fix ID: 3595647 Symptom: Replication takes much longer than expected, or completely hangs. Don't have a SymAccount?

Legacy ID 2009041708170054 Terms of use for this information are found in Legal Notices. IIS Service error during SEPM repair after removing IIS Fix ID: 3661647 Symptom: You upgrade Symantec Endpoint Protection Manager from 11.0, then repair the installation. The firewall state table clears unexpectedly. SEP Daily Status report does not show correct number of computers Fix ID: 3640666 Symptom: The Daily/Weekly Scheduled Risk Reports display inconsistent computer counts.

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 http://mmonoplayer.com/symantec-endpoint/symantec-endpoint-protection-error-code-11-whitelist-failure.html They can then make changes to domain policies and then launch the installation again. Solution: Resolved an issue on LiveUpdate scheduling for site with multiple Symantec Endpoint Protection Manager servers. This message appears when the Symantec Endpoint Protection client attempts to upgrade to the same version that the client already has, or to an earlier version.

Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. Solution: Removed the license serial number from resource file. Cannot enable "Include only clients that have checked in with the management server today" in SEPM Fix ID: 3646594 Symptom: You cannot enable Include only clients that have checked in with his comment is here Busy server experiences worker thread deadlocks and runs out of worker threads Fix ID: 3660134 Symptom: Servers with multiple volumes might experience deadlock when Symantec Endpoint Protection queries for file data.

This issue occurs even when there are no running scans. Solution: Fixed logic to give limited administrators the correct rights for read-only groups. Provide feedback on this article Request Assistance Print Article Products Subscribe to this Article Manage your Subscriptions Search Again Situation This article describesthe differenterror codes that appear within the logs

Scheduled Reports run at a later time every day Fix ID: 2148375 Symptom: A scheduled report does not run on time in many common scenarios, such as the Symantec Endpoint Protection

All services are running, connect to the database server ... Event ID 7000 and 7041: SemWebSrv and SemSrv fail to start after an upgrade to 12.1 RU5 Fix ID: 3705158 Symptom: Symantec Endpoint Protection Manager services failed to start after an Typo in error message in in scm-server*.log Fix ID: 3684471 Symptom: The error message “Login is from a local address Stirng format true” contains a typo. Limited admin is not able to run commands Fix ID: 3659056 Symptom: Limited administrators cannot run commands after giving them the correct rights to do so.

Forum Discussion by Alexander Cherbunin | 04 Dec 2016 | 3 comments Symantec Endpoint Protection - TECH231286 Issue mentioned in case TECH231286 is still not solved in version 14.  If it is Forum Discussion by Alexander Cherbunin | 26 Nov 2016 | 2 comments Error login to SEPM 14 Console "Unexpected server error" I need a solution   Hi all,   Yesterday we've Therefore, the policy does not save FileCache configuration changes. weblink Create a SymAccount now!' Unable to install Endpoint Protection client on Windows 10 after applying MS KB3140743 TECH234344 September 16th, 2016 http://www.symantec.com/docs/TECH234344 Support / Unable to install Endpoint Protection client on

Unexpected server error on SEPM Fix ID: 3725146 Symptom: The processing of content events stops if an event has the wrong number of fields. Create a SymAccount now!' Auto-Protect is disabled after running LiveUpdate in Symantec Endpoint Protection for Macintosh TECH137653 April 25th, 2013 http://www.symantec.com/docs/TECH137653 Support / Auto-Protect is disabled after running LiveUpdate in Symantec Solution: Now prompts for user group selection to avoid breaking the uninstallation. Meanwhile, other sortable columns were not sorted.

I need a solution Does anyone know what the IP address is for the following Symantec URL: liveupdate.symantecliveupdate.com A customers firewall team needs the information to ... SEPM unable to expand settings in Reports Fix ID: 3640460 Symptom: In the Symantec Endpoint Protection daily or weekly reports, nothing happens when you click Greater than 7 days under the