Home > Symantec Endpoint > Symantec Endpoint Protection Error Code 6

Symantec Endpoint Protection Error Code 6

Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. SEPM web console stalls at "Initializing... Custom log location folder lacks correct ACL settings Fix ID: 3689028 Symptom: After Symantec Endpoint Protection 12.1 RU5 strengthened ACL settings on program folders, the required ACL settings only apply to Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more. http://allconverter.net/symantec-endpoint/symantec-endpoint-protection-error-code-15.html

Here are Module / result code combinations that have appeared in support cases to date, along with the string version of the error: Module Result String Additional Information Generic 6 RESULT_FILE_NOT_FOUND SMC commands do not set proper return code in %errorlevel% Fix ID: 3387362 Symptom: SMC commands do not return any error codes if the operation fails. SEPM sends notification for low disk space when there is adequate disk space Fix ID: 3551334 Symptom: Symantec Endpoint Protection Manager sends a low disk space notification when there is plenty Solution: Added code to update the CIDS opstate cache when the CIDS opstate cache is not initialized.

Solution: Changed code to unlock the section of the registry before the Sysplant driver tries to modify it, and restores the lock immediately after Sysplant is done. Solution: Corrected the FileCache dialog logic. These clients then show up in the Computers Not Scanned report until they complete a scan.

Solution: SMC commands now return error codes for the operation to indicate success and what the failure was, if any, per documentation. You may continue working but cannot scan or repair. Solution: Append the TCP port into the BCP command line. Solution: Modified the code to handle the errors properly when BCP fails.

No Yes Symantec Connect Entire Site Search Tips Home Community:All Communities Overview Login or Register to participate English English 简体中文 Français Deutsch 日本語 Español Help Video Screencast Help Error messages Content Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more. Solution: Modified the Symantec Endpoint Protection Manager to no longer incorrectly trigger a security breach on this legitimate interaction. Article by Joshua Johnson | 01 Dec 2016 | 0 comments After installation of SMP 8.0 HF4 the data classes not shown in console I need a solution Colleagues!

Solution Download the Latest Version Contents Symantec Endpoint Protection 12.1.6 fixes Symantec Endpoint Protection 12.1.6 component versions Symantec Endpoint Protection 12.1.6 fixes Apache process crashes, clients reporting offline after SEPM upgrade SEP Mac IPS detects "brute force remote logon" despite host exclusions Fix ID: 3669436 Symptom: Even if an IP address range-based exclusion is added in the IPS exclusion policy, Symantec Endpoint Firewall rules incorrectly block an established connection when the screensaver activates Fix ID: 3686164 Symptom: Firewall rules incorrectly block an established connection when the screensaver activates. After the Application and Device Control rule triggers on the clients, the Symantec Endpoint Protection Manager logs contain the target MD5, but not the caller MD5.

Please reinstall Symantec Endpoint Protection. Solution: Compared the registry string lengths to make sure the string search does not overrun the boundary. It now reads Last Scan Started. Solution: Added a command to delete the contents for a cached directory that can cause this delay or hang.

References 3367659 Terms of use for this information are found in Legal Notices. weblink Solution: Added alternate method of obtaining the profile data with the required encryption key if the ProfileMangement.dat file cannot be migrated. Solution: Set the standard US decimal separators in PHP. 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.

Cause This is fixed in Symantec Endpoint Security 11.0 RU6 MP2. Solution: Added a command-line password prompt for this specific case. Faced with an error on full inventory page (screenshot). navigate here Solution: Mitigate the memory load by optimizing the verification code for existing unremediated items.

Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. Solution: Corrected the queries in the reports so that the counts are consistent. 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.

SEPM current deployment settings do not work consistently Fix ID: 3567574 Symptom: The option Apply current deployment settings to other groups does not work consistently.

Some firewall domain name block rules are also invalid in some situations. This status message is confusing. Solution: Updated the IRON driver to make it thread-safe. Solution This issue is fixed in Symantec Endpoint Protection 12.1.6.4 (RU6 MP4).

Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. Solution: Added a check to notify installer to not prompt for a password during an AutoUpgrade feature set change. Error 2502 while upgrading the client computers from SEP 11.0.6 / SEP 12.1 RU3 to 12.1 RU5 Fix ID: 3680155 Symptom: Error 2502 appears while upgrading the client computers from an his comment is here For more information, please refer to the Related Articles section below.

Solution: Modified tamper detection functionality to handle all host names correctly. Both of these issues stem from an incorrect DNS query for remote IPs. Unexpected scheduled scan on the client after a return to Standard Time Fix ID: 3655795 Symptom: An unexpected scheduled scan appears after a return to Standard Time from Daylight Savings Time SEPM processing slows down due to incorrect replication state does not return to 0 after replication finishes Fix ID: 3613994 Symptom: Symantec Endpoint Protection Manager slows down processing items such as

Solution: Append the custom port to the JDBC URL string if the default port 2638 is occupied by other application. Solution: Fixed the logic error and ensured that while copying the private cloud settings to other groups, the settings are not duplicated to the current group. ClientRemote.exe failing to push to more than 15 clients at a time Fix ID: 3691610 Symptom: Client deployment with ClientRemote.exe fails after the approximately 15 clients. SEP client installer rolls back and fails Fix ID: 3709190 Symptom: The Symantec Endpoint Protection client installer rolls back and fails, due to a failure to migrate the ProfileManagement.dat file.

No Yes Solution: Fixed the dbvalidator tool logic to correctly set the flag for both retrievals. Solution: Fixed the conversion of date/time columns when exporting the Computer Status logs. Solution: Text "may temporarely" changed to "might temporarily".

AutoUpgrade does not respect reduced-size install setting Fix ID: 3721853 Symptom: AutoUpgrade performs upgrade of reduced-size client to full-size client, regardless of the option set in Client Install Settings. Solutions: Adjusted settings so that the correct profile is identified as active. Solution: Changed the API in use to prevent memory leaks when no user is logged in.