Previous Post Next Post

SEPM log file went nots, can't install upgrade to MP1

Created: 09 Nov 2012 | 2 comments

jrockman13

Over the last week, I started getting "low disk space" errors from my SEP server. Overnight, the disk filled up and the SEP Emmbeded database crashed. After some short investigation, I found an article on Symantec Connect which to check the sep5.log file. Sure enough, 253GB!

After following this: http://www.symantec.com/docs/TECH178718 I set about upgrading.

My current version: 12.1.1000.157

I downloaded 12.1.1101.401 and unzipped it.

I'm assuming I can install the new manager and roll out the updated client by upgrading the package (Autoupdate).

When I try to install the new SEPM, I get the following error:

"Symantec Endpoint Protection Manager has detected that there are pending system changes that require a reboot. Please reboot the system and rerun the installation."

This error occurs even though I have just rebooted the server.

Any ideas on how to resolve this?

Discussion Filed Under:

Security, Endpoint Protection Small Business Edition 12.x - 12.1, Endpoint Protection Small Business Edition 12.x, Error messages, Installing, Upgrade

Comments RSS Feed

Comments 2 Comments • Jump to latest comment

Brian81 Trusted Advisor

SEPM log file went nots, can't install upgrade to MP1 - Comment:09 Nov 2012 : Link

Check the registry key mentioned in the solution in this thread:

https://www-secure.symantec.com/connect/forums/symantec-endpoint-protection-has-detected-there-are-pending-system-changes-require-reboot-ple

Deleting should fix the reboot message and allow you to install.

SEP Knowledge Base

Endpoint SWAT

Chetan Savade Symantec Employee Technical Support Accredited

SEPM log file went nots, can't install upgrade to MP1 - Comment:12 Nov 2012 : Link

Hi,

Your comment - "I'm assuming I can install the new manager and roll out the updated client by upgrading the package (Autoupdate)"

You can use auto upgrade feature if clients are communicating with Manager.

If you uninstall SEPM then you will have to use Sylink replacer tool to restore client communication.

You have not performed given workaround as per this article

http://www.symantec.com/docs/TECH178718

Check this article as well:

SEPM Upgrade fails with the message "Pending system changes that require a reboot have been detected"

http://www.symantec.com/business/support/index?pag...

Chetan Savade
Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.&