Video Screencast Help

SEP Unable to install..1708 & 1603

Created: 23 May 2013 | 14 comments

Hello,

Been trying to install SEP 11.0.6 on two servers and keep on falling flat! Please can someone assist...I have uploaded the SEP_INST log file - too much to go over. Servers are Win 2K8 R2 and had SEP installed but I uninstalled it (as the service would not start) and did cleanwipe as well. Still, not able to install. 

The errors seem to be 1708 and 1603.

Thanks!

Operating Systems:

Comments 14 CommentsJump to latest comment

.Brian's picture

is this 32 or 64 bit OS?

Rewview the manual uninstall KBAs to see if anything was left behind

How to manually uninstall Symantec Endpoint Protection client from Windows Vista, Windows 7, and Windows 2008 32-bit

Article:TECH102286  |  Created: 2007-01-02  |  Updated: 2011-07-25  |  Article URL http://www.symantec.com/docs/TECH102286

 

How to manually uninstall the Symantec Endpoint Protection client from Windows Vista, Windows 7, and Windows 2008 R2 64-bit

Article:TECH91038  |  Created: 2008-01-21  |  Updated: 2012-02-24  |  Article URL http://www.symantec.com/docs/TECH91038

 

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

SMLatCST's picture

I don't suppose you've Service Packed the machine have you?  If so, you'll want to install RU7 or later instead:

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

lara400notout's picture

Hello Brian - this is Win2k8 R2 - it is only 64-bit. I will check out the link.

Mithun Sanghavi's picture

Hello,

I would suggest you to install the Latest version of SEP 11.0.7300 on your Windows 2008 R2 SP1 Server as  the version below SEP 11.0.RU7 is not supported.

"Symantec Endpoint Protection 11.0 Release Update 7 (RU7) and Symantec Endpoint Protection 12.1 or higher is supported on Windows 7 SP1 and Windows Server 2008 R2 SP1."

Reference:

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

Hope that helps!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

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

lara400notout's picture

The server is SP1 (sorry, forgot to mention that bit). So, Windows 2008 R2 SP1.

Unfortunatly I wish I could install RU7 - however, it has not been signed off in our company so we only use 11.0.6.

We have it installed fine in about 500 other servers (same Os type) fine but these two are just not playing ball!

SMLatCST's picture

Perhaps they were installed with SEP prior to the SP being installed?  Nonetheless, as per my linked article, only RU7 and later is supported for Win2k8R2SP1 I'm afraid frown

lara400notout's picture

Hi - are you saying that 11.0.6 is not supported on Win2K8 R2 SP1? If so, can you provide an official link from symantec showing this so I can kick someones backside in my organisation......

Also - the build that is done is with SP1 by default - it is not an upgrade. It is straight forward fresh build using Win2k8 R2 SP1. 

I cannot see it being a compatitibility problem - as it works on 500+ other servers...?

Mithun Sanghavi's picture

Hello,

I would suggest you to install the Latest version of SEP 11.0.7300 on your Windows 2008 R2 SP1 Server as  the version below SEP 11.0.RU7 is not supported.

"Symantec Endpoint Protection 11.0 Release Update 7 (RU7) and Symantec Endpoint Protection 12.1 or higher is supported on Windows 7 SP1 and Windows Server 2008 R2 SP1."

Reference:

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

Hope that helps!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

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

.Brian's picture

Yes it is not officially supported. Check the link in his first post.

Which versions of Symantec Endpoint Protection are supported on Windows 7 SP1 and Windows Server 2008 R2 SP1?
Symantec Endpoint Protection 11.0 Release Update 7 (RU7) and Symantec Endpoint Protection 12.1 or higher is supported on Windows 7 SP1 and Windows Server 2008 R2 SP1. For information on getting the latest release, read the document Obtaining the latest version of Symantec Endpoint Protection or Symantec Network Access Control.

To be officially supported, you need to go to RU7

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

SMLatCST's picture

I linked the article in my first post, but here's a repeat:

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

As Brian says, it may work.  But it is hit and miss, and won't be supported by Symantec frown

.Brian's picture

It still may install, just not officially supported should a problem arise, like in this case.

The first piece of advice you will get is to install a supported version. If you're still having the issue than troubleshooting can be done.

If you cannot get to a supported version just yet than I would go thru the manual uninstall link to see if there is something left behind, then try the install again.

If you already have it installed on other machines that are similar, I suspect it may be something else.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

lara400notout's picture

ok - thanks all for the help.....although it still does not help in my situation in that it is not installing - I will inform the relevant team in my company.

I have removed all the things as listed in the first article and will test out a new install..

 

lara400notout's picture

darn it........its not worked....I did all the things in the article but it's still failing....http://www.symantec.com/docs/TECH91038

dmaltby's picture

For what it's worth, a similar issue was posted here:

https://www-secure.symantec.com/connect/forums/iss...

It wasn't SP1 for W2K8 64-bit, but the same "CustomAction WriteCcServiceRegistry.D9F570F7_4F5A_41B0_9D99_89851EE85080 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)" error was found in your SEP_INST output, although you don't have any 1607 errors.  In the previous case, it seemed the deployment package was corrupted, so running a repair on the SEP Manager seemed to work.  I can't explain why the package would suddenly become corrupted if you had this installed on several systems previously, and no changes made to the install packages.

Of course, updating to SEP 11 RU7 would likely give the same result (and that version supported by Symantec for that OS, as already proven by other replies), since it would update all of the packages.