Endpoint Protection

Unable to deploy package using CDW.  This error keeps popping up "Unexpected console error. [0x80010000]". 

SEPM version is at 12.1.1000 per article http://www.symantec.com/business/support/index?page=content&id=TECH168768.  Any ideas on how I can resolve this?

I'm experiencing the same thing here.

Actually, it just started AFTER I replaced a server, a SEPM server. I'll explain.

A while back I did an upgrade from 11.0.7 to 12.1 The first server, SEPM1 worked - it was an upgrade of SEPM over the 11.07 version. The SQL server lost network in the middle of upgrading SEPM2 to 12.1 so it crashed and burned - it acted so weird that I made a brand new server from scratch and did a native install of SEPM 12.1 to SEPM2 server.

So I was then running SEPM1 with an upgraded install to 12.1, and SEPM2 with a clean fresh install of SEPM 12.1 against our original SQL database that has been in use for years.

HOWEVER, strange things were going on with the communications, with the consoles, and with the alerting. Basically alerting was so screwed up, I had to turn off all email alerts and uncheck a bunch of logging. SEP itself was fine and seemed to be working.

SO, early this week, I took SEPM1 management services down, removed it from the SEPM structure in the console, renamed it in AD, and built a brand new server with a CLEAN fresh install of SEPM and SEP. So now both servers are fresh clean installs of SEPM, not upgrades, however the database is still the same one, and all the policies stayed in place - I did not change them or delete anything.

I needed to check for computers that didn't have SEP running on them so decided to use the clumsy push method - pretend I was going to push SEP out, and let it show me a list of computers..... but when I got to the final screen to search for computers, I get this error - ALL the time now. I'd never seen it prior to building a new server for SEPM1!   Now since building a replacement server, I cannot push SEP out at all. Our push installs are broken totally.

Any clues??

This problem is caused by issues with the way SEPM processes Unmanaged Detector information. The error occurs when the range/subnet of IP addresses provided to the Client Deployment Wizard contains one or more addresses discovered by an Unmanaged Detector.

http://www.symantec.com/business/support/index?page=content&id=TECH168768&actp=search&viewlocale=en_US&searchid=1333777832442

This issue will be fixed most probably in the next SEP built.

Hi,

Try to repair the SEPM.

Rightly said by Sandeep... the issue is expected to be fixed in the next built i.e. 12.1 RU1 MP1

I understand the explanation - however, we had no unmanaged detectors at the time!

They were all shut down, or rather the detector part turned off/disabled a year ago, before the upgrade, when I realized they were pretty worthless in actually giving me any facts.

So, in our case, why did it do that? There was no unmanaged detector enabled at the time of the error.

I just now this week enabled an unmanaged detector on a computer that had never been one before, I've not tried it since.

I also note that my own computers are in the list twise as being unmanaged - one is and one isn't, so the report is wrong, and they were listed twice. I excluded them from detection, and that removed one instance of each, but both STILL show up in the list/report, and one of them IS managed! In fact, it's part of the same group several other computers are in - so how can be be unmanaged?

Why did they show up twice in the report, and why did the exclusion remove only one instance of them?

And how is the unmanaged detector giving me a list of addresses and devices on a different subnet?

It's on xxx.xxx.180.xxx while it's giving me both the 180 addresses AND it's giving me xxx.xxx.170.xxx addresses. It used to be they had to be on the same subnet?

Is this another undocumented change? 

BTW - thanks for the replies in ANY case.....