We are having the same problem with our server. Any Ideas? I uninstalled the symantec console but the same.

 

Thanks,

I tried to install End Point Security in our test lab last Thursday and received the same error message. The server I am using is a WK2 with SP4 running the 10.1.0.396 version of Symantec. I also opened a trouble ticket with support and they haven’t gotten back with me on anything yet. I will post something if support ever calls me back with anything because right now I'm not impressed with the new version.

I use to have this problem when i first install the SEP 11; what i do is quit the wizard and stop the background process of the previous setup program. or simply reboot the machine and run the wizard again.

Ya i have tested this final release on 7 of my clients, it fails EVERYTIME!  i have even uninstalled all symantec products, same result. there is no endpoint service to stop.  And this dumb install should stop any service it needs and restart.. who wrote this program anyways???

In the off chance that the Service Control Manager is out of sync with what's installed (which does happen occasionally), you can try:

 

net stop semsrv

 

and/or

 

net stop IIS Admin

 

 

semsrv not an installed service

The solution for me on this was that port 8443 was already in use.  My server was running an old version of HP jetadmin that had this port open.  Once I uninstalled jetadmin it worked fine.  I would also imagine if you choose another port than 8443 it would also fix this issue.

I gave up on this, uninstalled it from the clients i was working with.  it is too buggy, plus i dont know what Symantec was thinking about forcing firewall and intrusion policies in by default.  what a nightmare.  This program shuts down servers completely, not a bright idea...

After having a disturbing conversation with support, they're convinced they're right 100% of the time.  First, they stated they're using Tomcat on a Windows box even if IIS is installed.  So why the popup saying to stop IIS?

 

Since WebJet Admin has been around for many years, why is it that HP has to change and not Symantec?

Note to Symantec: Your product is the new kid on the block, please make sure you don't step on existing services from MAJOR players when you release it.

 

In the end, I think we'll stay on 10.1.7.  Someone let me know when they work out the bugs in 11 and we'll revisit it.

I haven't tried the JetAdmin port change (or changing Symantec) but the machine in question does have JetAdmin on it.  I have been testing the waters on other products in the meantime.

 

[quote]In the end, I think we'll stay on 10.1.7.[/quote]

 

Probably deserves a seperate thread, but this would be my preference too.  But, how do I get a license file?

 

I am probably missing something simple...

 

DaveW

I can tell you this, the program is junk right out of the box.  1st off, who would write a program that installs on a server that will by default block all communications to the server?  If you install the protection suite, it will block all communications, ping, shares, everything.  So not only is this program junk from the install side, it is a lame suite completely by defaulting to block everything.  lets keep the protection suite with the home using symantec norton internet security (which i never use).  Try writing a program that admins can make the decisions, not the programmers...My clients will never use this version, we will all stay happy at 10.2.

While I'm not a fan of 11, if you install and configure it right you have access to anything you like.  Install the managment console and configure your preferences first then deploy the client and you're fine.

 

Now if they would only return RAM usage to <100MB, 500MB out of the box with no management clients is absolutely unacceptable.  How many SMBs will have access to a dedicated server to run v11?  Exactly ZERO.

I have been having the same problem with installing 11.0.  Has anyone come up with a solution?

 

Somehow, I think that SEP 11.0 is not-quite-ready-for-primetime.

 

I installed it previously on a test machine, and the CPU went to 100% and stayed there.

 

No way am I going to put this on my working servers!