Solution: Fixed by deleting the current data area in conf.properties when the data and backup folders are deleted. Solution: Modified the Auto-Protect feature to check correctly for network mappings on drive letters A: through C:. Solution: Initialized a variable that had not previously been initialized due to a blank computer serial number. Solution: Fixed the conversion of date/time columns when exporting the Computer Status logs. http://digitalsurgeon.net/blue-screen/symantec-blue-screen-windows-7.html
F 4 E Guru Norton Fighter25 Reg: 23-May-2009 Posts: 8,201 Solutions: 282 Kudos: 1,661 Kudos1 Stats Re: Norton causing BSOD Posted: 28-Jun-2016 | 8:58PM • Permalink Hi,aljaker. Try these resources. Did the users who installed today do a LU until there were no more updates ? Thank you for your feedback!
Click on the Norton 360 - All-In-One Security-associated entry. Macs experience high CPU usage by SymDaemon Fix ID: 3671496 Symptom: After a user logs out, Macs may experience a slow system for some time after they log on again. Excessive non-paged memory used by Symnet.sys driver Fix ID: 3362553 Symptom: Symnet.sys exhausts non-paged pool memory. Solution: Modified File System Auto-Protect driver to avoid this deadlock.
Solution: Added a command-line password prompt for this specific case. Lucia Storbritannien Surinam Swaziland Sverige Sydafrika Tadzjikistan Taiwan Tanzania Tchad Thailand Tjeckien Togo Trinidad och Tobago Tunisien Turkiet Turkmenistan Turks- och Caicosöarna Tyskland Uganda Ukraina Ungern Uruguay USA Uzbekistan Vanuatu Venezuela The tech worked with me in making a policy and I am going to give that a shot now. Symefa64.sys Bsod The BSOD immediately precedes a system shutdown and no opportunity to "Finish" an error log is available.
Svchost.exe crash due to sysfer.dll causes continuous restarts Fix ID: 3723905 Symptom: A svchost.exe crash due to sysfer.dll causes continuous restarts. You now have a backup of your IDSviA64.sys-related registry entry. Click on the Norton 360 - All-In-One Security-associated entry. recommended you read However, if uninstallation requires a password on the client, the change to the feature set fails.
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 Symefasi.sys Windows 10 For additional help, Corsair has a great video tutorial on how to run Memtest86: http://www2.corsair.com/training/how_to_memtest/6 Step 10: Perform a Clean Installation of Windows Caution: We must emphasize that reinstalling Windows The system administrator can view the enforcer client log normally. Database entries for Symantec Endpoint Protection 11.0.x content are not cleaned up when an 11.0.x client upgrades to version 12.1.x Fix ID: 2932494 Symptom: After a Symantec Endpoint Protection 11.0.x client
Solution: Modified the Auto-Protect feature to log threats in this scenario correctly. Symptoms include: Copying files from a network location over Windows File Sharing takes significantly more time. Symefasi.sys Bsod Solution: Added a check for the validity of the home directory path before the scan engine launches. Symefa64.sys Symantec Corporation Efa Solution: Updated the licensing logic to count by agent only, not per user logged into the client computer.
Solution: Changed the API in use to prevent memory leaks when no user is logged in. this contact form Solution: Changes to the proxy list mean that the proxy is no longer locked until the service is restarted. The environment also uses Symantec Network Access Control. I need results, not a support forum to make suggestions. Symefa.sys Blue Screen Windows 7
Also, how do we press the button on the logger if the symptom is a blue screen? After using AutoUpgrade, the deployment report in SEPM shows “The client decided to reject the upgrade package” for many clients Fix ID: 3624243 Symptom: Many clients in a group display a SEPM web console stalls at "Initializing... http://digitalsurgeon.net/blue-screen/symantec-endpoint-blue-screen-windows-7.html Solution: The column header Last Scanned Time (Home > Reports, with the report type Computers by Last Scan Time) refers to the time the most recent scan finishes.
Solution: Updated sorting column to default to Time if the previous sorting column is not in the new table. Symantec Bluecoat Unexpected error in Symantec Endpoint Protection Manager: "Session already invalidated" Fix ID: 2915051 Symptom: The scm-server log shows exception messages such as: java.lang.IllegalStateException: getAttribute: Session already invalidated. Other notifications are working properly.
Solution: Updated the code to handle string buffer resize exceptions to avoid process crash. Re-installing doesn't fix the issue with version 126.96.36.199. Content Distribution Monitor reports the wrong latest IPS date/revision for Symantec Fix ID: 3723871 Symptom: The latest IPS version from Symantec does not display in the Content Distribution Monitor tool. Symantec Endpoint Protection If you are able to help us with this issue.
Click Yes. Browse SYS Files in Alphabetical Order: # A B C D E F G H I J K L M N O P Q R S T U V W X RADIUS settings not saved for the Enforcer Fix ID: 2791090 Symptom: The management server does not save the Enforcer RADIUS settings. Check This Out Solution: Changed the schedule to run based on the scheduled report time, rather than based on the time that the previous scheduled report ended.
Please send us the logs. Download the Windows MemTest86 USB image. They needed to look at a computer and confirm that a problem was happening and it was what I said it was. During this query, the SymEFA database files use a lot of memory.
Solution: Added a fallback mechanism to load the server profile from a backup profile file. Please Note: Using System Restore will not affect your documents, pictures, or other data. Traffic loss due to high RDNS queries Fix ID: 3640736 Symptom: A high number of duplicated RDNS queries causes traffic loss. High disk space is consumed by C:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\outbox\Importpackage Fix ID: 2914951/3118490 Symptom: Hard drive space on the Symantec Endpoint Protection Manager server is running low due to files
every hour. Incorrect estimation of the minimum package size when exporting a client installation package Fix ID: 2947564 Symptom: In the Export Client Package dialog, the estimated minimum package size displayed is less Type "update" into the search box and hit ENTER.