Endpoint Protection Small Business Edition

12.1.5 installation fails - that's pretty much all the window says.

The associated log has indications that it cannot get to the database?!?

Saw the TECH225587  when searching Google.  However, when I run the query command, the SID is NONE for an embedded database.

The other item missing from the tech article is what to do AFTER running that command - do I start the installation over again?

I am on hold waiting to get to tech support now for 10 minutes, but could really use a faster solution.

Thanks!

You need to post some logs, particularly SEP_INST.log and SIS_INST.log

What logs do I need to gather in order to troubleshoot a failed SEP 12.1 client installation?

It is an upgrade from 12.1.4 to 12.1.5

After 30 minutes I've got a tech.  Will post logs as soon as practical.

Basically, I ran into the embedded database not starting.  But I'm not all clear as to what process to follow AFTER it is fixed.

So this is SEPM and not client just to clarify?

You can turn on advanced logging for SEPM

How to debug the Symantec Endpoint Protection Manager

Support is probably best case here since they will have remote access.

Yes, SEPM and had to reboot, ran repair and that failed.

Needed to run Upgrade.bat - without executing the commands in the KB article.

Process to optimize LiveUpdate content is running now.

We'll see how long this takes, and what happens when it completes.

As long as you have enough space on C: for the optimmization it should go smoothly. It will take longer than usual due to the optimization process. One time only.

Finally completed.

C:\ drive was 27.9 free before, is now 34.3 after.  A very nice savings.

Now, for the rant:  Technician says problem experienced is a "known issue".  Not exactly what this Symantec partner wants to hear early on a Sunday morning.  Notwithstanding the hour-long support session, it seems that despite "knowing" this is a problem, getting it fixed requires some extraordinary measures.  I am sorry, but searching through Google to find a solution is not acceptable.  Having inadequate documentation and incompletely documented KB articles is NOT acceptable.  NOT posting a warning about this in the upgrade materials IS NOT ACCEPTABLE!

End of rant.