- #SYMANTEC ENDPOINT PROTECTION 14 MSI HOW TO#
- #SYMANTEC ENDPOINT PROTECTION 14 MSI INSTALL#
- #SYMANTEC ENDPOINT PROTECTION 14 MSI FULL#
- #SYMANTEC ENDPOINT PROTECTION 14 MSI CODE#
(You could wonder why those machines had a SEP client once, but were removed later.
#SYMANTEC ENDPOINT PROTECTION 14 MSI INSTALL#
But in the past an install of the SEP client was never a problem on those machines and I couldn’t even find a single note in an article or forum thread SEP wasn’t supported for ISA Server: at the contrary! The weird thing was I had this issue on only 2 machines and both of them were almost identical, each running Windows Server 2003 SP2 R2 and ISA Server 2006.
333 this tool is included in the client itself, but I couldn’t use it this way as, well, the client wasn’t installed, remember? 🙂 Nope, no problem, everything should be fine for a perfect SEP client install… Sight… BTW, starting from SEP client version. Perhaps there was something wrong with the requirements? Was my system compliant with the requirements of the SEP client? To check this I downloaded the Symantec tool “Symantec Endpoint Protection Support Tool” and checked to see if there were issues with the server. But even after deleting those the issue remained… Perhaps CleanWipe hadn’t cleaned literally everything? I looked for the last traces and found several references left in registry and file system (mmm, this is not what I would expect from a tool named “CleanWipe”). Then I tried again to install the SEP client, but… still the same issue… Fulfilled with new hope, I downloaded CleanWipe, cleaned as much as I could and restarted the server (which was recommended by CleanWipe). Perhaps I should run CleanWipe first? CleanWipe is a tool of Symantec that cleans your system as to Symantec products it probably doesn’t surprise you that many uninstalls don’t uninstall everything (sometimes with a reason, wometimes not) and this statement is also valid for the SEP client. Wait a minute… once an “old” version of the SEP client was installed on this machine.
#SYMANTEC ENDPOINT PROTECTION 14 MSI HOW TO#
Yup, we know more now, but we still don’t know the exact cause, let alone how to solve the problem. It’s not clear why the virus definitions couldn’t be added and thus why this function has failed.
#SYMANTEC ENDPOINT PROTECTION 14 MSI CODE#
This has caused an exception and the function returns error code 3. It seems the function RegWithLiveUpdate has failed, while trying to add virus definitions. LUCA: Call to HandleLiveUpdateAction FAILED.Īction ended 9:52:26: InstallFinalize. LUCA: HandleLiveUpdateAction: COM Exception: LUCA(1020): Exception calling IluProductReg RegisterProduct LUCA(1157): CustomActionData=Add SESC Virus Definitions Win32 v11 MicroDefsB.CurDefs SymAllLanguages Antivirus and antispyware definitions ” DLL: C:\WINDOWS\Installer\MSI60.tmp, Entrypoint: RegWithLiveUpdate MSI (s) (5C:04) : Invoking remote custom action. In my case this file’s size was 7 to 8 megabyte! Exploring this file takes a while, but in my case I was lucky to find the very first failure:
#SYMANTEC ENDPOINT PROTECTION 14 MSI FULL#
Of course it’s a good thing this is logged, but when trying to find out why this failure has happened, this kind of logging is worthless! It doesn’t even give us an indication! Anyway, it’s time to take a look at the full blown install log, which is SEP_INST.LOG in %temp%. Mmm… It just logs the fact the installation has failed. We’re lucky as the following event is logged in the Application event log of Windows:ĭescription: Product: Symantec Endpoint Protection - Installation operation failed.įor more information, see Help and Support Center at. Here’s my story 🙂įirst thing to do is checking for events in the Windows event logs. Aaargh… Of course the installer doesn’t tell us what exactly went wrong, so we have to find out ourselves. First everything seems to go smooth till you see the “Rolling back action” appear in the installer’s GUI. When you try to install the Sympantec Endpoint Protection (SEP) client, it’s possible it rolls back after being confronted with an error.
0 kommentar(er)
