Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.
Symantec EndPoint Protection 12.1 caused BSOD on my HP Proliant DL160 G6
Hi All,
I have a management server which I use for things like Backup Exec, Syslog and my Symantec EndPoint Protection Management server which is a HP Proliant DL160 G6 runnig Windows 2003 R2 Enterprise. It has been running EndPoint 11.1 for about 18 months fine, but the other day I decided it was time to go to 12.1 as we qualified for a free update.
I tested it out on my VM test lab and all seemed OK, so I did the upgrade on my management server and again the EndPoint Manager worked great on 12.1. I upgraded a few clients without issues so thought it was going OK, so then I upgraded the SEP client on my Management server to 12.1. As soon as the install finished my server blue screens with HARDWARE MALFUNCTION ??
I try a reboot, no joy, so I boot to safe mode and uninstall the SEP client and it then boots fine! Some googling later and I found some similar problems with Kaspersky so I updated all my management servers drivers, firmware and BIOS and tried again......same problem!
All my clients/VMs I have upgraded work fine, but this server doesn't want to work. All my other physical servers (DCs/Exchange etc) are also HP Proliant G6 servers (a mix of DL360 & DL380) while my management server is a DL160 G6. I have got no help from Symantec on this, they just tell me to update drivers etc which I have so I'm a little stuck.
I did find this - http://www.tricksguide.com/blue-screen-error-hardware-malfunction-pci-express-error-hp-proliant-server.html - which talks about disabling No Execute Memory Protection but my model server doesn't have this option.
Any suggestions?
Thx!
Andy
I have a management server which I use for things like Backup Exec, Syslog and my Symantec EndPoint Protection Management server which is a HP Proliant DL160 G6 runnig Windows 2003 R2 Enterprise. It has been running EndPoint 11.1 for about 18 months fine, but the other day I decided it was time to go to 12.1 as we qualified for a free update.
I tested it out on my VM test lab and all seemed OK, so I did the upgrade on my management server and again the EndPoint Manager worked great on 12.1. I upgraded a few clients without issues so thought it was going OK, so then I upgraded the SEP client on my Management server to 12.1. As soon as the install finished my server blue screens with HARDWARE MALFUNCTION ??
I try a reboot, no joy, so I boot to safe mode and uninstall the SEP client and it then boots fine! Some googling later and I found some similar problems with Kaspersky so I updated all my management servers drivers, firmware and BIOS and tried again......same problem!
All my clients/VMs I have upgraded work fine, but this server doesn't want to work. All my other physical servers (DCs/Exchange etc) are also HP Proliant G6 servers (a mix of DL360 & DL380) while my management server is a DL160 G6. I have got no help from Symantec on this, they just tell me to update drivers etc which I have so I'm a little stuck.
I did find this - http://www.tricksguide.com/blue-screen-error-hardware-malfunction-pci-express-error-hp-proliant-server.html - which talks about disabling No Execute Memory Protection but my model server doesn't have this option.
Any suggestions?
Thx!
Andy
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
LVL 9
I understand the 1st attempt was upgrade on existing 11.1 to 12.1, after uninstalling all Symantec endpoint related apps., did you try installing straightway version 12.1 ? plz try if "no".
@manic_andy ,
Do you have any of the dumps files? Could you post or 3 of them?
You can find the dumps file in C:\Windows\Minidump folder. More info below:
http://support.microsoft.com/kb/315263
Sudeep
Do you have any of the dumps files? Could you post or 3 of them?
You can find the dumps file in C:\Windows\Minidump folder. More info below:
http://support.microsoft.com/kb/315263
Sudeep
Yep after I did the uninstall from the upgraded 11.1 to 12.1 I tried a clean 12.1 client install and had the same problem.
Will generate a dump file later today when the backups have finished.
Will generate a dump file later today when the backups have finished.
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trial
This is a known problem, plz check the link.
http://www.symantec.com/business/support/index?page=content&id=TECH181336
http://www.symantec.com/business/support/index?page=content&id=TECH181336
Under solution it says..
Security Update MS11-077 which contains a fix for this problem
Any application like folder lock or Adope apps install ?
Security Update MS11-077 which contains a fix for this problem
Any application like folder lock or Adope apps install ?
No folder lock or adobe.
Only have - Backup Exec 2010 SP1 (no CPS as aware of the conflict with that)
Symantec EndPoint Protection Manager 12.1
WSUS
WatchGuard Firewall WSM 11.3
Kiwi Syslog
Only have - Backup Exec 2010 SP1 (no CPS as aware of the conflict with that)
Symantec EndPoint Protection Manager 12.1
WSUS
WatchGuard Firewall WSM 11.3
Kiwi Syslog
If you didn't try.
Disable in windows the "restart on error" function, afterwards you can read the BSOD error message.
I feel its a conflict with one the application.
Disable in windows the "restart on error" function, afterwards you can read the BSOD error message.
I feel its a conflict with one the application.
Already have it set like that, so when it crashes after the SEP 12.1 client install it sits at the blue screen saying hardware malfunction. When I reboot and it does the post steps it shows that the P212 controller locked up, which is consistent with the problems I found that Kaspersky caused, but HP fixed in version 5.14 of the controller firmware I have installed.
I have reinstalled 11.1 client for now which works fine.
I have reinstalled 11.1 client for now which works fine.
Following are the known issues for Symantec Endpoint Protection 12.1
http://www.symantec.com/business/support/index?page=content&id=TECH163700
If you wish to try, I would suggest uninstall Backup Exec 2010 SP1, Install first sysmantec endpoint 12.1 and than install Backup exec.
http://www.symantec.com/business/support/index?page=content&id=TECH163700
If you wish to try, I would suggest uninstall Backup Exec 2010 SP1, Install first sysmantec endpoint 12.1 and than install Backup exec.
Thanks. I have logged an issue with Symantec support anyway now so am letting them troubleshoot it for me. I've been installing/uninstalling and trying different things for about 3 days now and no joy. I put 11.1 back on and it works fine, then tried uninstalling that manually (seemed OK) then installed 12.1 again and it just fails to install which didn't happen before so I have sent Symantec the logs and will see what they suggest.
One thing for certain though, my confidence in the product is gone. There is no way I can confidently say to my manager that we should deploy 12.1 now onto our DCs and or Exchange servers following this even if Symantec come back to me with a solution whatever that is. It just seems way to flakey to be causing a physical controller lockup when 11.1 worked fine. Last thing I want is to have this replicated on my DCs/Exchange where the controllor lockup could be way more serious than on my management server where I can afford to lose everything if needed.
I will post back when I heard back from Symantec on it.
One thing for certain though, my confidence in the product is gone. There is no way I can confidently say to my manager that we should deploy 12.1 now onto our DCs and or Exchange servers following this even if Symantec come back to me with a solution whatever that is. It just seems way to flakey to be causing a physical controller lockup when 11.1 worked fine. Last thing I want is to have this replicated on my DCs/Exchange where the controllor lockup could be way more serious than on my management server where I can afford to lose everything if needed.
I will post back when I heard back from Symantec on it.
Just realized its not generating dump files as its not causing a STOP, its just doing a hardware malfunction bsod, so no minidump or kernal dumps. Don't really want to start messing around with NMI switches/jumpers to cause a stop so have logged a call with Symantec to get it looked at.
Thanks.
Thanks.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Anti-Virus Apps
From novice to tech pro — start learning today.
-
Microsoft ApplicationsCertification: MCSA MCSE Microsoft Certified Solutions Associate & … 398 lessons
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.