First of all, hello!

Yeah, simple question for you:

Where do the Manager copy the Endpoint Protection installation files during Push install?

Hello,

We use SEP 12.1.x SBE (Small Business Edition) version, along with SEPM - all currently at 12.1.5 version. 

I read from Security Advisory (http://www.symantec.com/security_response/securityupdates/detail.jsp?fid=security_advisory&pvid=security_advisory&year=&suid=20150730_00) that I need to upgrade to 12.1.6.1a toi protect from vulnerabilities (in fact, I assisted in doing that for company with Enterprise Edition)

But in FileConnect I can see only 12.1.5 version downloadable! And I read from http://www.symantec.com/page.jsp?id=sbe-migration that I need to move to SEP SBE (was SEP SBE 2013) which I understand is different product, since there will not be any 12.1.x past 12.1.5 (which is vulnerable).

So what do I exactly do to patch both SEPM and clients? Our license renewal cycle is in December. I'm not convinced to upgrade to SBE 2013 yet (different features, much more expensive).

Hi,

I just wanted to know SEP 12.1.1 is avalible or discontinue, if avaible can i get system requirement for the same.

I appreciate your answer.

Hello,

I need some help. We have to exclude many extensions, from .data1 - .data500, however we have some troubles doing it with the wildcard.

As per Symantec article, it says:

Note: Wildcard variables such as * and ? are not supported for Known Risks, File, or Folder exceptions. The ? wildcard is supported for Extension exceptions. The Folder exceptions screen will accept * and ? but they will be treated as literal characters and not wildcard variables.

Did someone use wildcard for Extension exclusion, was it working and how exactly you configured it? We tested it but not working

Thanks

Hello DLP community

I recently set up a new DLP environment (1x Enforce, 1x Endpoint, various test clients - everything on the same local network).
Up to now, when I way authoring and editing policies, they have been distributed out to the clients in the network in seconds.
In the new environment it takes much longer. When I activate / modify / create a policy, it takes up to 5 minutes for the policy to arrive at the client and be effective. The same behaviour it shows when transmitting the incident data to the Enforce server.

What is causing this? Is it an agent setting? I know I can set the heartbeat to a different value, but this does not make sense.

By the way: It is 12.5.2 all over

It might be an absolute no-brainer, but I don't seem to find an answer to this.

Greetings

I left a company where I was using my own computer.  I removed all the software they required me to remove.  I am now stuck with some latent program that was trying to update and I am locked out of my own computer.  The computer itself is locked and I need an "Administrator Login" to unlock the computer.  Please advise.

Is there a way to change the SEP report from mht file type to one that can be open with a Mac?

Basically, is there any merit still to this HOWTO article?

https://support.symantec.com/en_US/article.HOWTO83492.html

Should I uncheck "Include unused disk space..." for encrypting SSDs, and leave it checked for encrypting mechanical HDDs? 

I'm using SEE 11.0.1. 

We've been experiencing an increase in messages getting through our Messaging Gateway as well as our customer's gateways.  This stuff goes in cycles, obviously, and the filters usually catch up but this time they haven't been.  Following all of the official and community best practices.  We've reduced a lot of the junk by lowering the directory harvesting thresholds down to 3 invalid recipients but this still results in a lot of messages getting through.

While reviewing the headers of these messages I found that the Return-Path is *almost always* formatted like this:
RandomName-RecipientsAddress@SenderDomain

The important detail is that the @ in the RecipientAddress portion is replaced with =, for example:
JohnDoe-myemail=address.com@sender.domain.com

Simple solution seems to be create a content filter rule to look for '=' in the Return-Path header.  I've tried this two ways and it does not work consistently, if at all.  Anybody have any ideas on what I'm doing wrong?  Is this a bug?  Here are the conditions I've tried:

If text in Message header "Return-Path" contains 1 or more occurrences of "="

If text in Message header "Return-Path" matches regular expression "^.*\=.*?"

Seems like this should be a no brainer but something isn't right.

Thanks!

Hi folks,

I'm prepareing to migrate DLP 12.5 system into virual server.

So I'm going to follow the steps of manual "Symantec_DLP_12.5_System_Maintenance_Guide.pdf"

I think migration the server and database would be ok but I'm worry about that all the agents also connect to new server as well.

I know that DLP 12.5 have new SSL key connectivity with agent so it might not cause any problem?

In the manual, it says only backup and restore tomcat keystore file but not mention about "\SymantecDLP\Protect\keystore\" files.

Just in case, please verify me the right steps.

Thank you.

I have Win 7 x64 installed on desktop (Dell T-7600)

We having SEE Ver 11.0.1 (build 7342) being pushed via GPO.

A machine in particular won't boot...it has a WSOD (White screen of death).

The recovery CD provided doesn't boot to a usable GUI. The eeAdminCli command won't launch.

Here is what I have done

1.  Removed the internal hard drive and pulled data off via a hardware caddy/usb connection to a diff computer.

2. I have updated tot he latest BIOS

3.  I used a Windows Repair DVD and ran repair to get to the recovery tools. I ran bootrec /fixmbr,  and bootrec /fixboot,  and bootrec /rebuild BCD. The computer then rebooted and I was able to login to Windows. This victory was short lived. Becasue when I rebooted again, I was back to square one...the same initial error of " Some required files are missing or corrupted. You may be able to continue through the advanced menu or recovery tool. Press any key to return."

So, I run through the drill or repairing computer and re-running the fixmbr etc. It then boots up properly. I login and the symantec agent says that the drive is not encrypted. However, when I run eeAdminCli --status --disk0 ...I get answer of "Disk 0 is instrumented by drive encryption".

And when I reboot, I get the same error as previously stated.

4. I have tried using Symantec Agent to 'Encrypt' via the Admin console with the thought that I could then 'decrypt'. But the encryption does not kick off.

Lastly, I am unable to unistall SEE Client nor Drive encryption. Error is: "Disk is still encrypted. Uninstallation aborted"

So, what can I do to save from reimaging?

Hi All, 

Looking for a little information here. I have a customer that is using SEPM 12.1.4013.4013, They requested an upgrade to 12.1.6 due to the release of Windows 10, easy enough I thought. However this has been giving me headaches for the past few days. We encountered issues with the current version when trying to do the upgrade. First thing we did was backup the current database which ran fine, and created a backup with no issues. I stopped all the Symantec services and began the process of upgrading. This is where the issues presented themselfs, first the server would not let the install run as it required a reboot to finish system changes. Once the server rebooted the services seemed to be running with no issues. I stopped the services again and started the install of 12.1.6 and got the same message about requiring a reboot of the server. I did not want to reboot the server due to this being their AD/DC server and during business hours. I did a little digging and found a tool that was suppose to help resolve the reboot request issue. However, I attempted to restart the services before downloading the tool so there would be no issues on the clients protection. This is where things went haywire, the SEPM service would start and then stop with no rhyme or reason, and the embedded database service would not start at all. After exausting all the steps I could find in the forums to resolve this, i spoke with the customer about the issues we were experiencing. He stated that this had been an issue in the past but if it was possible he would like the SEPM moved to their new server. So here is where I need some advice. We installed 12.1.6 on the new server and all services are running, however we need procedures to migrate the policies over to the new server, and connect the client machines to the new server. However at this point on the old server we can not get the management console to run to backup and migrate the policies. Does anyone know of a way that we can get these policies from the old server even though we can not access any SEPM tools or consle? Any help on this would be greatly apreciated as I do not want to have to rebuild the policies. I also have opened a case with Symantec but have not had any responce from them since the case was opened. I have chatted with them a couple of times and they stated they would re-dispatch the ticket and then i never hear from them afterwards. Im gettting frustrated with their support so I figured I would reach out on the forums and see what could be found. Any help or procedures to do this would be most appreciated. Thanks.   

Good Day,

May I know if there is available or existing SEP 12.1.6 installer for MAC OSX?

Thanks and regards.

hello community,

SMG setup:

A is a SMG gateway to the internet for all in / out of my company  (this is a VM) 10.5.4-4

B is another SMG right after A for other mail routing but all mail passes thru B as well in /out (this is a VM) as well 10.5.4-4

A and B both have the same SPAM filtering settings (delete mail with spam).

Problem: B is catching spam that A should have caught. <-- this is not right

Settings:  Both A and B are allowed (thru the firewall) to go where ever neeed to get virus and spam defs; basically they are allowed to make any                              connection to symantec or brightmail servers to get updates < this is NOT the issue, this works perfectly.

               Sender Authentication is off on A and B and DKIM is off

PLease help

I remember reading somewhere that having too many locations in one group in SEPM is a bad thing.  Is this still true? what is the limit?  We have more than 500 locations and managing them group is not fun.  Please advise.

hi,

I just got back from Vacation and my SEPM console is having all sorts of errors.

Firstly, Replication is failing - (Second site is OK) and Definitions are out of date since 08/02/15

All managment Server lists are gone - Unable to add any new ones or import - Receive Console Error

Under Admin> Servers i am getting unexpected Server errors.

Tried the following and none have worked

• Rebooting Server
• Disable Replication
• Reran Server Configuration Wizard
• Changed Embedded Server Service logon to local System rather than NT SERVICE\SQLANYs_sem5

Here is the SCMServer Log information

2015-08-12 07:59:47.728 THREAD 12 SEVERE: ================== Server Environment ===================
2015-08-12 07:59:47.728 THREAD 12 SEVERE: os.name = Windows Server 2008 R2
2015-08-12 07:59:47.728 THREAD 12 SEVERE: os.version = 6.1
2015-08-12 07:59:47.728 THREAD 12 SEVERE: os.arch = x64
2015-08-12 07:59:47.728 THREAD 12 SEVERE: java.version = 1.7.0_55
2015-08-12 07:59:47.728 THREAD 12 SEVERE: java.vendor = Oracle Corporation
2015-08-12 07:59:47.728 THREAD 12 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
2015-08-12 07:59:47.728 THREAD 12 SEVERE: java.vm.version = 24.55-b03
2015-08-12 07:59:47.728 THREAD 12 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jre
2015-08-12 07:59:47.728 THREAD 12 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
2015-08-12 07:59:47.728 THREAD 12 SEVERE: java.user = null
2015-08-12 07:59:47.728 THREAD 12 SEVERE: user.language = en
2015-08-12 07:59:47.744 THREAD 12 SEVERE: user.country = US
2015-08-12 07:59:47.744 THREAD 12 SEVERE: scm.server.version = 12.1.5337.5000
2015-08-12 07:59:47.759 THREAD 12 SEVERE: StartupServlet> startServer>> SEPM Service starting...
2015-08-12 07:59:49.366 THREAD 12 SEVERE: StartupServlet> verifySchemaVersion>> Database Schema Version = 12.1.5.4, Server Schema Version = 12.1.5.4
2015-08-12 07:59:49.382 THREAD 12 SEVERE:  in: com.sygate.scm.server.servlet.StartupServlet
com.sygate.scm.server.util.ScmServerError: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1438)
 at com.sygate.scm.server.configmanager.ConfigManager.getSemServerStateObject(ConfigManager.java:3560)
 at com.sygate.scm.server.servlet.StartupServlet.registerServer(StartupServlet.java:272)
 at com.sygate.scm.server.servlet.StartupServlet.startServer(StartupServlet.java:528)
 at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:124)
 at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1279)
 at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1192)
 at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
 at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5210)
 at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5493)
 at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
 at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
 at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:670)
 at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1839)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:502)
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:476)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:151)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:162)
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1432)
 ... 20 more
2015-08-12 08:00:42.887 THREAD 41 SEVERE:  in: com.sygate.scm.server.consolemanager.RequestHandler
com.sygate.scm.server.util.ScmServerError: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1438)
 at com.sygate.scm.server.consolemanager.requesthandler.GetObjectHandler.getObject(GetObjectHandler.java:284)
 at com.sygate.scm.server.consolemanager.requesthandler.GetObjectHandler.handleRequest(GetObjectHandler.java:148)
 at com.sygate.scm.server.consolemanager.RequestHandler.handleRequest(RequestHandler.java:532)
 at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:150)
 at com.sygate.scm.server.servlet.ConsoleServlet.doPost(ConsoleServlet.java:116)
 at com.sygate.scm.server.servlet.ConsoleServlet.doGet(ConsoleServlet.java:59)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at com.sygate.scm.server.servlet.ConsoleFilter.doFilter(ConsoleFilter.java:69)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
 at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
 at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
 at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
 at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:315)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:502)
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:476)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:151)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:162)
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1432)
 ... 26 more
2015-08-12 08:00:42.904 THREAD 41 SEVERE:  in: com.sygate.scm.server.servlet.ConsoleServlet
java.lang.RuntimeException: com.sygate.scm.server.util.ScmServerError: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:165)
 at com.sygate.scm.server.servlet.ConsoleServlet.doPost(ConsoleServlet.java:116)
 at com.sygate.scm.server.servlet.ConsoleServlet.doGet(ConsoleServlet.java:59)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at com.sygate.scm.server.servlet.ConsoleFilter.doFilter(ConsoleFilter.java:69)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
 at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
 at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
 at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
 at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:315)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: com.sygate.scm.server.util.ScmServerError: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1438)
 at com.sygate.scm.server.consolemanager.requesthandler.GetObjectHandler.getObject(GetObjectHandler.java:284)
 at com.sygate.scm.server.consolemanager.requesthandler.GetObjectHandler.handleRequest(GetObjectHandler.java:148)
 at com.sygate.scm.server.consolemanager.RequestHandler.handleRequest(RequestHandler.java:532)
 at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:150)
 ... 22 more
Caused by: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:502)
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:476)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:151)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:162)
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1432)
 ... 26 more
2015-08-12 08:00:42.982 THREAD 44 SEVERE:  in: com.sygate.scm.server.consolemanager.RequestHandler
com.sygate.scm.server.util.ScmServerError: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1438)
 at com.sygate.scm.server.consolemanager.requesthandler.GetObjectHandler.getObject(GetObjectHandler.java:284)
 at com.sygate.scm.server.consolemanager.requesthandler.GetObjectHandler.handleRequest(GetObjectHandler.java:148)
 at com.sygate.scm.server.consolemanager.RequestHandler.handleRequest(RequestHandler.java:532)
 at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:150)
 at com.sygate.scm.server.servlet.ConsoleServlet.doPost(ConsoleServlet.java:116)
 at com.sygate.scm.server.servlet.ConsoleServlet.doGet(ConsoleServlet.java:59)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at com.sygate.scm.server.servlet.ConsoleFilter.doFilter(ConsoleFilter.java:69)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
 at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
 at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
 at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
 at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:315)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:502)
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:476)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:151)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:162)
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1432)
 ... 26 more
2015-08-12 08:00:42.997 THREAD 44 SEVERE:  in: com.sygate.scm.server.servlet.ConsoleServlet
java.lang.RuntimeException: com.sygate.scm.server.util.ScmServerError: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:165)
 at com.sygate.scm.server.servlet.ConsoleServlet.doPost(ConsoleServlet.java:116)
 at com.sygate.scm.server.servlet.ConsoleServlet.doGet(ConsoleServlet.java:59)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at com.sygate.scm.server.servlet.ConsoleFilter.doFilter(ConsoleFilter.java:69)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
 at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
 at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
 at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
 at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:315)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: com.sygate.scm.server.util.ScmServerError: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1438)
 at com.sygate.scm.server.consolemanager.requesthandler.GetObjectHandler.getObject(GetObjectHandler.java:284)
 at com.sygate.scm.server.consolemanager.requesthandler.GetObjectHandler.handleRequest(GetObjectHandler.java:148)
 at com.sygate.scm.server.consolemanager.RequestHandler.handleRequest(RequestHandler.java:532)
 at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:150)
 ... 22 more
Caused by: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:502)
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:476)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:151)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:162)
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1432)
 ... 26 more
2015-08-12 08:00:50.535 THREAD 41 SEVERE:  in: com.sygate.scm.server.consolemanager.RequestHandler
com.sygate.scm.server.util.ScmServerError: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1438)
 at com.sygate.scm.server.consolemanager.requesthandler.GetObjectHandler.getObject(GetObjectHandler.java:284)
 at com.sygate.scm.server.consolemanager.requesthandler.GetObjectHandler.handleRequest(GetObjectHandler.java:148)
 at com.sygate.scm.server.consolemanager.RequestHandler.handleRequest(RequestHandler.java:532)
 at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:150)
 at com.sygate.scm.server.servlet.ConsoleServlet.doPost(ConsoleServlet.java:116)
 at com.sygate.scm.server.servlet.ConsoleServlet.doGet(ConsoleServlet.java:59)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at com.sygate.scm.server.servlet.ConsoleFilter.doFilter(ConsoleFilter.java:69)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
 at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
 at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
 at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
 at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:502)
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:476)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:151)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:162)
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1432)
 ... 26 more
2015-08-12 08:00:50.550 THREAD 41 SEVERE:  in: com.sygate.scm.server.servlet.ConsoleServlet
java.lang.RuntimeException: com.sygate.scm.server.util.ScmServerError: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:165)
 at com.sygate.scm.server.servlet.ConsoleServlet.doPost(ConsoleServlet.java:116)
 at com.sygate.scm.server.servlet.ConsoleServlet.doGet(ConsoleServlet.java:59)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at com.sygate.scm.server.servlet.ConsoleFilter.doFilter(ConsoleFilter.java:69)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
 at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
 at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
 at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
 at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: com.sygate.scm.server.util.ScmServerError: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1438)
 at com.sygate.scm.server.consolemanager.requesthandler.GetObjectHandler.getObject(GetObjectHandler.java:284)
 at com.sygate.scm.server.consolemanager.requesthandler.GetObjectHandler.handleRequest(GetObjectHandler.java:148)
 at com.sygate.scm.server.consolemanager.RequestHandler.handleRequest(RequestHandler.java:532)
 at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:150)
 ... 22 more
Caused by: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:502)
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:476)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:151)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:162)
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1432)
 ... 26 more
2015-08-12 08:00:50.601 THREAD 44 SEVERE:  in: com.sygate.scm.server.consolemanager.RequestHandler
com.sygate.scm.server.util.ScmServerError: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1438)
 at com.sygate.scm.server.consolemanager.requesthandler.GetObjectHandler.getObject(GetObjectHandler.java:284)
 at com.sygate.scm.server.consolemanager.requesthandler.GetObjectHandler.handleRequest(GetObjectHandler.java:148)
 at com.sygate.scm.server.consolemanager.RequestHandler.handleRequest(RequestHandler.java:532)
 at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:150)
 at com.sygate.scm.server.servlet.ConsoleServlet.doPost(ConsoleServlet.java:116)
 at com.sygate.scm.server.servlet.ConsoleServlet.doGet(ConsoleServlet.java:59)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at com.sygate.scm.server.servlet.ConsoleFilter.doFilter(ConsoleFilter.java:69)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
 at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
 at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
 at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
 at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:502)
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:476)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:151)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:162)
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1432)
 ... 26 more
2015-08-12 08:00:50.603 THREAD 44 SEVERE:  in: com.sygate.scm.server.servlet.ConsoleServlet
java.lang.RuntimeException: com.sygate.scm.server.util.ScmServerError: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:165)
 at com.sygate.scm.server.servlet.ConsoleServlet.doPost(ConsoleServlet.java:116)
 at com.sygate.scm.server.servlet.ConsoleServlet.doGet(ConsoleServlet.java:59)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at com.sygate.scm.server.servlet.ConsoleFilter.doFilter(ConsoleFilter.java:69)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
 at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
 at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
 at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
 at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: com.sygate.scm.server.util.ScmServerError: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1438)
 at com.sygate.scm.server.consolemanager.requesthandler.GetObjectHandler.getObject(GetObjectHandler.java:284)
 at com.sygate.scm.server.consolemanager.requesthandler.GetObjectHandler.handleRequest(GetObjectHandler.java:148)
 at com.sygate.scm.server.consolemanager.RequestHandler.handleRequest(RequestHandler.java:532)
 at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:150)
 ... 22 more
Caused by: com.sygate.scm.common.configobject.ValidationException: Content is not allowed in prolog.
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:502)
 at com.sygate.scm.common.configobject.XMLHelper.parseSAX(XMLHelper.java:476)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:151)
 at com.sygate.scm.common.configobject.AbstractSchema.readXML(AbstractSchema.java:162)
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1432)
 ... 26 more
 

Hi Team,

A member of partner team shared me a PGP Public Key to encrypt a file, then when I encrypted the file I will send it again and they will decrypt  with their private key.

When they decrypt the file, they have an error: PGP 164 Error.

So, I want to know If I have to SIgn and Verify the Public key?

I look forward your response,

Hello everyone,

we have the following scenario:

- User creates a new email (HTML format), the user will then attach another email message as a file that is encrypted and in a HTML format.
- The user then sends the message to a recipient that has PGP as well
- The recipient can open the attached encrypted message just fine, but the actual body does not get decrypted, even though the recipient has the sender's key

We're on 10.3.2 (MP7), Outlook 2013 32-bit in an Exchange environment.

Any help is appreciated!

A couple of weeks ago after connecting to a hotel network to do some work, my laptop started getting the Unsolicited incoming ARP reply detected messages. Now I get this showing up whenever I connect to a non-company network (like home or a hotel) and when I'm connected to my company's network via a VPN connection. I went through the IT department of my company to try and find out what to do...after a couple of weeks of trying different things and them doing research, they decided I need to have my hard drive replaced or reformatted.

Seems like that's a drastic fix to the problem...especially after looking at past threads on this website that said just turn off the notification. Our company is using Symantec Endpoint protection and my installed version is 12.1.4013.4013.

Is there a better fix for this...or should I just ignore it...or follow the IT department's direction and send my computer back in to get reformatted??

Thanks!

I recently upgraded my Security Virtual Appliance from 12.1.2 to 12.1.5.  My new 12.1.5 SVA’s show up in SEPM in the Monitors section as “online”, but my old 12.1.2 SVA’s are still listed as well as “offline”.  Does anyone know how to remove the old SVA’s from SEPM?