When I've had SEP installation failures like this, the first place I look at is the install log. SEP's install log is "SEP_INST.LOG" and is in one of the temp directories on the system. 9 times out of 10, typing "%temp%\SEP_INST.LOG" will bring it up in notepad. (otherwise, you'll have to go looking for it)

 

 

Now, this log is really hard to read. However, if you've got another, successfull, SEP install log, you can compare the two and that sometimes gives you a clue as to what the problem is. If you can narrow down the portion of the failing install log that seems to indicate the problem, post that here.

 

Otherwise, Symantec tech support will ask for this log when you call them.

 

(and please post the solution/answer if you get one from them!)

do you see anything in your windows event log?

 

normally there would be a windows installer error message given - this may help us narrow it down

 

p.

My Log file from SEP:

 

 

Screenshot of EVENT VIEWER, Specifically the MSIInstaller error:

 

Just another info on another error bellow the MSIInstaller (dont know it this matters at all)

 

 

 

As far as I can recall, last time I got this same error (rolling back at the end of installation) was when I installed SAV CORPORATE 10.

It was solved by turning on a service..I believe it was the EVENT VIEWER..which at that time we eventually had it turned off. After turning it on, installtion of SAV CORPORATE 10 running well.

 

Anybody can help me

Is this an upgrade you are attempting?

 

From your screenshots I can see that the LiveUpdate installer is having problems removing the Automatic LiveUpdate Scheduler service and I see the following in SEP_INST.LOG

 

-- DECABI_LOGGING --   LiveUpdate registration failed. (HRESULT=-2144731115)

 

Can you check in your Add/Remove programs and see if you have LiveUpdate already installed?  If so, uninstall it from there and reboot.

 

Then try the install again.  If it still fails, can you run LUSETUP.exe from the SEP source on its own FIRST, then try the installation.

 

thanks

p.

Hello Paul,

Thank you for replying. I dont have Live Update installed in my computer. I dont know why it says that I do have one.

 

1. I have done MANUAL UNINSTALLATION described in http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2006022212084148?Open&docid=2002031914291648&nsf=ent-security.nsf&view=ppfdocs

2. I have followed your suggestiona and install LUSETUP.exe. The installation runs well. It finishes up just fine. I then try to run setup of SEP again...Yet, the same error message comes out again..it started rolling back and the "wizard was interrupted..." showed up again.

 

 

Paul, I'm seeing the same exact condition on one of my servers running Windows 2003 Server w/SP2.  I was running SAV 10.1.4 before introducing SEP 11 to my network.  Like the other user, I also had to use the manual method to remove SAV 10.1.4 because the uninstall failed partway through the uninstall.  Since then, I cannot complete SEP 11.  It goes through the rollback just as the other user described and I also have the same Windows event logs.  I've tried your suggestion and it does not work for me either.

 

Thanks.

 

Ken

I wonder if there is some sort of version conflict.

i.e. SEP 11 has a later LU version, SAV 10.x may have an earlier version.

 

I'd try uninstalling the 3.s LU version and reinstall the 3.2.x versipn from:

 

 

Then try the SEP install.

 

 

Thank you for replying. Tried that...no working.

Anybody else who can help me?

If you have savroam running, try stopping the service before installing or upgrading. I have some issues with savroam not stopping.

 

 

SK

Thank you for replying.

 

I have no Symantec nor any other services related to symantec in the current PC. I have done every single effort to make sure there is no trace that symantec name ever appears in the PC...after that I do installation. Yet, the installation still fails.

 

I still believe that the problem lays on a much simpler solution.

 

As I mentioned above, in my previous problem with SAV 10, the problem lays on EVENT LOG service that I happened to turned off. After turning it on, the installation run smoothly. So, how about in SEP? any Local Security Policy that I need to ensure running in order to get the installation up and running?

hmm..I believe this is a dead end?

I have finally found a clue...

 

it's the ERROR 1920 that makes it rolls back. How do I know this? I tried installing SAV and it shows me the error message

 

I have searched all the documents to troubleshoot ERROR 1920

I have looked here:

 

and here:

 

 

I have done everything asked in those documents. Yet, I still have the same error message everytime installing SAV. So, I can conclude that Endpoint protection has also encountered ERROR 1920 when installing. However, it doesnt show any error message (BAD PROGRAM?)

 

Anybody can tell me how to solve the ERROR 1920? Dont tell me to go to Symantec Support Center..I have done everything in those docs I mentioned above

Looks like there are multiple reason for this error and multiple possible fixes.  I did a google search for "symantec install error 1920" (no quotes) and there seems to be a ton of stuff you might be able to try. 

 

I remember that I had a similar issue on one machine trying to install the first release version of SAV 10, where the install would say that it had been interrupted and roll back.  After a lot of Googling I found many different suggestions, but the one that worked for me was on some forum or email list.  A file called Msxmls.inf was set to read-only, once I changed that, the install worked.  The problem with install errors are the error codes tend to be very generic and there can be multiple different reasons (and fixes) for them.  This won't fix your issue since SEP doesn't have/use this file, only given as an example.

 

One diagnostic that I have found handy is the freeware Process Monitor from the Sysinternals section of Microsoft.  With this (and some filtering applied to the output), you can see every file and/or registry access happening on your system in real time and the results.  So, if your issue is caused by the installer not being able to access or modify something, you could find out what that was and change permissions/settings for a possible fix.