After Upgrading to SEP 14.3 RU7, Server Reporting Unexpected Error.

[Jermane Akoto]

After upgrading to SEP Manager 14.3 RU7 on hosting, server reporting unexpected error. Already checked on here as Broadcom is saying their engineers are working to fix that error. Could it be that since our Symantec runs on java on our client laptop and the java is not installed our server that is why we are getting these unexpected errors. Thank you.

[DAVID MATTHEWSON]

Interesting. We've recently u/gd two sites to ru7. One is fine and the other gives this 'unexpected error'

Time	Site	Server	Severity	Event Type	Description
25/04/2023 09:07:47	Site LON	LON	Error	An unexpected exception has occurred	Unexpected server error.
25/04/2023 08:54:23	Site LON	LON	Error	An unexpected exception has occurred	Unexpected server error.

I can't find anything in any logs and the error reoccurs every 45 mins or so. The system seems to be working fine but I'd like to either turn this 'warning' off or, better, fix it!

[Imtiaz Hussain]

Hi David,
there are notification , you will not get if you disable it from logs
notifications

Regards,
Imtiaz Hussain


On Tue, Apr 25, 2023 at 12:53 PM DAVID MATTHEWSON via Broadcom <
[e-mail]> wrote:

> Interesting. We've recently u/gd two sites to ru7. One is fine and the
> other gives this 'unexpected error' Time Site Server ...
> [image: Broadcom] <https: community.broadcom.com="">
> Endpoint Protection
> <https: community.broadcom.com/symantecenterprise/communities/community-home/digestviewer?communitykey="1ecf5f55-9545-44d6-b0f4-4e4a7f5f5e68">
> Post New Message <[e-mail]>
> Re: After Upgrading to SEP 14.3 RU7, Server Reporting Unexpected Error.
> <https: community.broadcom.com/symantecenterprise/discussion/after-upgrading-to-sep-143-ru7-server-reporting-unexpected-error#bmc64d9283-96ca-4bb1-b4de-0187b79a11ae="">
> Reply to Group
> <[e-mail]?subject=re:+after+upgrading+to+sep+14.3+ru7,+server+reporting+unexpected+error.> Reply
> to Sender
> <https: community.broadcom.com/symantecenterprise/communities/all-discussions/postreply?messagekey="c64d9283-96ca-4bb1-b4de-0187b79a11ae&ListKey=09a5d7f3-db14-428a-b8b8-bcc0ea7cb156&SenderKey=3fe717c7-f588-46e3-b3b6-3992e554b86b">
> [image: DAVID MATTHEWSON]
> <https: community.broadcom.com/network/members/profile?userkey="3fe717c7-f588-46e3-b3b6-3992e554b86b">
> Apr 25, 2023 4:53 AM
> DAVID MATTHEWSON
> <https: community.broadcom.com/network/members/profile?userkey="3fe717c7-f588-46e3-b3b6-3992e554b86b">
>
> Interesting. We've recently u/gd two sites to ru7. One is fine and the
> other gives this 'unexpected error'
>
> *Time*
>
> *Site*
>
> *Server*
>
> *Severity*
>
> *Event Type*
>
> *Description*
>
> 25/04/2023 09:07:47
>
> Site LON
>
> LON
>
> Error
>
> An unexpected exception has occurred
>
> Unexpected server error.
>
> 25/04/2023 08:54:23
>
> Site LON
>
> LON
>
> Error
>
> An unexpected exception has occurred
>
> Unexpected server error.
>
>
> I can't find anything in any logs and the error reoccurs every 45 mins or
> so. The system seems to be working fine but I'd like to either turn this
> 'warning' off or, better, fix it!
> *Reply to Group Online
> <https: community.broadcom.com/symantecenterprise/communities/all-discussions/postreply?messagekey="c64d9283-96ca-4bb1-b4de-0187b79a11ae&ListKey=09a5d7f3-db14-428a-b8b8-bcc0ea7cb156">*
> *Reply to Group via Email
> <[e-mail]?subject=re:+after+upgrading+to+sep+14.3+ru7,+server+reporting+unexpected+error.>*
> *View Thread
> <https: community.broadcom.com/symantecenterprise/discussion/after-upgrading-to-sep-143-ru7-server-reporting-unexpected-error#bmc64d9283-96ca-4bb1-b4de-0187b79a11ae="">*
> *Recommend
> <https: community.broadcom.com:443/symantecenterprise/discussion/after-upgrading-to-sep-143-ru7-server-reporting-unexpected-error?messagekey="c64d9283-96ca-4bb1-b4de-0187b79a11ae&cmd=rate&cmdarg=add#bmc64d9283-96ca-4bb1-b4de-0187b79a11ae">*
> *Forward
> <https: community.broadcom.com/symantecenterprise/communities/all-discussions/forwardmessages?messagekey="c64d9283-96ca-4bb1-b4de-0187b79a11ae&ListKey=09a5d7f3-db14-428a-b8b8-bcc0ea7cb156">*
> *Flag as Inappropriate
> <https: community.broadcom.com/symantecenterprise/discussion/after-upgrading-to-sep-143-ru7-server-reporting-unexpected-error?markappropriate="c64d9283-96ca-4bb1-b4de-0187b79a11ae#bmc64d9283-96ca-4bb1-b4de-0187b79a11ae">*
>
> -------------------------------------------
> Original Message:
> Sent: Apr 24, 2023 10:55 AM
> From: Jermane Akoto
> Subject: After Upgrading to SEP 14.3 RU7, Server Reporting Unexpected
> Error.
>
> After upgrading to SEP Manager 14.3 RU7 on hosting, server reporting
> unexpected error. Already checked on here as Broadcom is saying their
> engineers are working to fix that error. Could it be that since our
> Symantec runs on java on our client laptop and the java is not installed
> our server that is why we are getting these unexpected errors. Thank you.
>
>
>
>
> You are subscribed to "Endpoint Protection" as [e-mail]. To
> change your subscriptions, go to My Subscriptions
> <http: community.broadcom.com/preferences?section="Subscriptions">. To
> unsubscribe from this community discussion, go to Unsubscribe
> <http: community.broadcom.com/higherlogic/egroups/unsubscribe.aspx?userkey="d42a3a31-33f0-41ec-8a7e-1420d5798008&sKey=KeyRemoved&GroupKey=09a5d7f3-db14-428a-b8b8-bcc0ea7cb156">.
>
>
> Copyright © 2005-2023 Broadcom. All Rights Reserved. The term "Broadcom"
> refers to Broadcom Inc. and/or its subsidiaries.
>
> Hosted by Higher Logic, LLC on the behalf of Broadcom - Privacy Policy
> <https: www.broadcom.com/company/legal/privacy-policy=""> | Cookie Policy
> <https: www.higherlogic.com/legal/privacy=""> | Supply Chain Transparency
> <https: www.broadcom.com/company/citizenship/governance-and-ethics#supply="">
> | Terms of Use <http: termsandconditions="">
>

[Szabi Kiss]

Hi,

We had same issue yesterday two thins what we did and the unexpected errors are disappered 
 - we set the syslog settings again
 - dcheck the admin user rights and the previously created reports (one user has no rights to view a reports)

[Jermane Akoto]

hey Szabi Kiss , how do we set the syslog settings ,  is it on the server side or the client side ?

[DAVID MATTHEWSON]

OK, we turned off 'notifications on server errors' and of course the emails topped. Which is a step forward, but I really want to know what the underlying problem is, as stopping 'notifications' also stops/hides any 'real' problem messages.

[Ed Agoff]

"Unexpected server error" is pretty generic. To troubleshoot, enable FINEST SEPM Tomcat debug logging, recreate the error, and review scm-server logging and others in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\logs. Google SEPM unexpected server error site:knowledge.broadcom.comand see if any the related KB articles align with what you see in logging. Please otherwise open a case with support to troubleshoot further.

Ref: Enabling Tomcat server debugging for the Endpoint Protection Manager

[DAVID MATTHEWSON]

Thanks for that.

[Kerry Brown]

Hi,
I'm having the same error after upgrading SEPM to 14.3.9816.7000 from RU5
i have an alert approx every hour. "An unexpected exception has occurred"

My scm-server-0.log has these repeating entries around when it alerts.

2023-05-16 13:17:01.978 THREAD 18 WARNING: MetadataManager>> getFile: Error-> no file is found! id=A2AC771692A29765861BD066B1242245
2023-05-16 13:17:01.994 THREAD 18 SEVERE:  in: com.sygate.scm.server.consolemanager.requesthandler.ConfigServerHandler
java.io.FileNotFoundException: Latest full not found: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Inetpub\content\{1A79EE79-891B-4CB6-9A00-8D07FC6BF1FF}\190206023\Full
    at com.sygate.scm.server.liveupdate.delta.ContentDeltaManager.getPreExistingLatestFullPath(ContentDeltaManager.java:855)
    at com.sygate.scm.server.liveupdate.delta.IncrementalDeltaRequest.createForLatestRevision(IncrementalDeltaRequest.java:356)
    at com.sygate.scm.server.liveupdate.delta.IncrementalDeltaRequest.createIncrementalDeltaRequest(IncrementalDeltaRequest.java:146)
    at com.sygate.scm.server.liveupdate.delta.ContentDeltaManager.addContent(ContentDeltaManager.java:466)
    at com.sygate.scm.server.consolemanager.requesthandler.ConfigServerHandler.addDelta(ConfigServerHandler.java:3705)
    at com.sygate.scm.server.consolemanager.requesthandler.ConfigServerHandler.saveLUContent(ConfigServerHandler.java:3265)
    at com.sygate.scm.server.consolemanager.requesthandler.ConfigServerHandler.saveLUContent(ConfigServerHandler.java:3092)
    at com.sygate.scm.server.consolemanager.requesthandler.ConfigServerHandler.processLUContent(ConfigServerHandler.java:714)
    at com.sygate.scm.server.consolemanager.requesthandler.ConfigServerHandler.handleRequest(ConfigServerHandler.java:470)
    at com.sygate.scm.server.consolemanager.RequestHandler.handleRequest(RequestHandler.java:382)
    at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:171)
    at com.sygate.scm.server.servlet.ConsoleServlet.doPost(ConsoleServlet.java:148)
    at com.sygate.scm.server.servlet.ConsoleServlet.doGet(ConsoleServlet.java:69)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:502)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:596)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:209)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
    at com.sygate.scm.pool.HttpResponseFilters.doFilter(HttpResponseFilters.java:129)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
    at com.sygate.scm.server.servlet.ConsoleFilter.doFilter(ConsoleFilter.java:86)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:167)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:492)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
    at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:389)
    at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
    at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:926)
    at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1713)
    at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
    at org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1265)
    at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:641)
    at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:619)
    at java.base/sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:127)
    at java.base/sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:282)
    at java.base/sun.nio.ch.WindowsAsynchronousSocketChannelImpl$ReadTask.completed(WindowsAsynchronousSocketChannelImpl.java:581)
    at java.base/sun.nio.ch.Iocp$EventHandlerTask.run(Iocp.java:387)
    at java.base/sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base/java.lang.Thread.run(Thread.java:829)
2023-05-16 13:17:09.842 THREAD 61 WARNING: MetadataManager>> getFile: Error-> no file is found! id=A2AC771692A29765861BD066B1242245
2023-05-16 13:17:09.842 THREAD 61 SEVERE: Warning: PackageTask.publishContent>> Speculating Broken content link! Skipping content: {1A79EE79-891B-4CB6-9A00-8D07FC6BF1FF} Revision: 190206023 Reference Type: ObjReference ID: 8CB1E35FA471DBD19F7854BDE559E112 binFileID: A2AC771692A29765861BD066B1242245 FileName: full.zip FileType: 1 TypeName: Content: {1A79EE79-891B-4CB6-9A00-8D07FC6BF1FF} Seq#: 190206023 FULL: true{TargetId: 8CB1E35FA471DBD19F7854BDE559E112} IFD: false IRD: true{TargetId: 29E2162B355FF44922B8B9E5E39AC426, Target: 190206008}
2023-05-16 13:17:09.842 THREAD 61 WARNING: MetadataManager>> getFile: Error-> no file is found! id=27C3AD5D350F924A1B0209B1FF7CF143
2023-05-16 13:17:09.842 THREAD 61 SEVERE: Warning: PackageTask.publishContent>> Speculating Broken content link! Skipping content: {535CB6A4-441F-4e8a-A897-804CD859100E} Revision: 190206023 Reference Type: ObjReference ID: B7C8E6AC1AE49D31FF631574102A1D58 binFileID: 27C3AD5D350F924A1B0209B1FF7CF143 FileName: full.zip FileType: 1 TypeName: Content: {535CB6A4-441F-4e8a-A897-804CD859100E} Seq#: 190206023 FULL: true{TargetId: B7C8E6AC1AE49D31FF631574102A1D58} IFD: false IRD: true{TargetId: 4B5684685B8388DCCEDED0704BA67D4B, Target: 190206008}
2023-05-16 13:17:18.561 THREAD 61 WARNING: MetadataManager>> getFile: Error-> no file is found! id=A2AC771692A29765861BD066B1242245
2023-05-16 13:17:18.561 THREAD 61 SEVERE: Warning: PackageTask.publishContent>> Speculating Broken content link! Skipping content: {1A79EE79-891B-4CB6-9A00-8D07FC6BF1FF} Revision: 190206023 Reference Type: ObjReference ID: 8CB1E35FA471DBD19F7854BDE559E112 binFileID: A2AC771692A29765861BD066B1242245 FileName: full.zip FileType: 1 TypeName: Content: {1A79EE79-891B-4CB6-9A00-8D07FC6BF1FF} Seq#: 190206023 FULL: true{TargetId: 8CB1E35FA471DBD19F7854BDE559E112} IFD: false IRD: true{TargetId: 29E2162B355FF44922B8B9E5E39AC426, Target: 190206008}
2023-05-16 13:17:18.577 THREAD 61 WARNING: MetadataManager>> getFile: Error-> no file is found! id=27C3AD5D350F924A1B0209B1FF7CF143
2023-05-16 13:17:18.577 THREAD 61 SEVERE: Warning: PackageTask.publishContent>> Speculating Broken content link! Skipping content: {535CB6A4-441F-4e8a-A897-804CD859100E} Revision: 190206023 Reference Type: ObjReference ID: B7C8E6AC1AE49D31FF631574102A1D58 binFileID: 27C3AD5D350F924A1B0209B1FF7CF143 FileName: full.zip FileType: 1 TypeName: Content: {535CB6A4-441F-4e8a-A897-804CD859100E} Seq#: 190206023 FULL: true{TargetId: B7C8E6AC1AE49D31FF631574102A1D58} IFD: false IRD: true{TargetId: 4B5684685B8388DCCEDED0704BA67D4B, Target: 190206008}

Any Ideas?
 

------------------------------
K Brown
------------------------------

[John Owens]

Hi Kerry,

It appears to be broken content in the database. Support has tools they can provide to fix this. Please open a case.

------------------------------
John Owens
Strategic Support Engineer | Symantec Endpoint Security Division (SES)
Broadcom Software
------------------------------

[Krister Henningsson]

Hello all

We have one client with an old Symantec Endpoint Protection < RU6 that can't connect to SEPM
This causes an unexpected error.

The log say it has wrong domain identifier.

Since the SEP installed has a password protection I can't uninstall
I will reset Windows and then the error message will go away I assume.

Med vänlig hälsning/
Kind regards

Krister
IT-avdelningen / The IT Crowd ;-)

[Jermane Akoto]

Hey Krister Henningsson , Can you please elaborate more on the wrong domain identifier ,if possible a suggestion or advice on how to fix that .Thank you.

[Krister Henningsson]

AgentRegister-1.log(31025): 2023-05-03 10:55:30.852 THREAD 18 WARNING: com.sygate.scm.server.agentmanager.InvalidDomainIdRegistrationException: Client n is trying to register with invalid Domain ID nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn.

Från: Jermane Akoto via Broadcom <[e-mail]>
Skickat: den 5 maj 2023 17:27
Till: Krister Henningsson <[e-mail]>
Ämne: RE: Endpoint Protection : After Upgrading to SEP 14.3 RU7, Server Reporting Unexpected Error.

Hey Krister Henningsson , Can you please elaborate more on the wrong domain identifier ,if possible a suggestion or advice on how to fix that ... -posted to the "Endpoint Protection" community
[Bild som tagits bort av avsändaren. Broadcom]<https: community.broadcom.com/="">
Endpoint Protection<https: community.broadcom.com/symantecenterprise/communities/community-home/digestviewer?communitykey="1ecf5f55-9545-44d6-b0f4-4e4a7f5f5e68">
Post New Message<mailto:[e-mail]>

Re: After Upgrading to SEP 14.3 RU7, Server Reporting Unexpected Error.<https: community.broadcom.com/symantecenterprise/discussion/after-upgrading-to-sep-143-ru7-server-reporting-unexpected-error#bm458044d3-e8ba-4d73-9e29-0187ec82b403="">
Reply to Group<mailto:[e-mail]?subject=re:%20after%20upgrading%20to%20sep%2014.3%20ru7,%20server%20reporting%20unexpected%20error.>
Reply to Sender<https: community.broadcom.com/symantecenterprise/communities/all-discussions/postreply?messagekey="458044d3-e8ba-4d73-9e29-0187ec82b403&ListKey=09a5d7f3-db14-428a-b8b8-bcc0ea7cb156&SenderKey=8d8fb90b-9ec5-4e43-9c8a-01859c04d141">
[Bild som tagits bort av avsändaren. Jermane Akoto]<https: community.broadcom.com/network/members/profile?userkey="8d8fb90b-9ec5-4e43-9c8a-01859c04d141">
May 5, 2023 11:25 AM
Jermane Akoto<https: community.broadcom.com/network/members/profile?userkey="8d8fb90b-9ec5-4e43-9c8a-01859c04d141">

Hey Krister Henningsson , Can you please elaborate more on the wrong domain identifier ,if possible a suggestion or advice on how to fix that .Thank you.
Reply to Group Online<https: community.broadcom.com/symantecenterprise/communities/all-discussions/postreply?messagekey="458044d3-e8ba-4d73-9e29-0187ec82b403&ListKey=09a5d7f3-db14-428a-b8b8-bcc0ea7cb156"> Reply to Group via Email<mailto:[e-mail]?subject=re:%20after%20upgrading%20to%20sep%2014.3%20ru7,%20server%20reporting%20unexpected%20error.> View Thread<https: community.broadcom.com/symantecenterprise/discussion/after-upgrading-to-sep-143-ru7-server-reporting-unexpected-error#bm458044d3-e8ba-4d73-9e29-0187ec82b403=""> Recommend<https: community.broadcom.com:443/symantecenterprise/discussion/after-upgrading-to-sep-143-ru7-server-reporting-unexpected-error?messagekey="458044d3-e8ba-4d73-9e29-0187ec82b403&cmd=rate&cmdarg=add#bm458044d3-e8ba-4d73-9e29-0187ec82b403"> Forward<https: community.broadcom.com/symantecenterprise/communities/all-discussions/forwardmessages?messagekey="458044d3-e8ba-4d73-9e29-0187ec82b403&ListKey=09a5d7f3-db14-428a-b8b8-bcc0ea7cb156"> Flag as Inappropriate<https: community.broadcom.com/symantecenterprise/discussion/after-upgrading-to-sep-143-ru7-server-reporting-unexpected-error?markappropriate="458044d3-e8ba-4d73-9e29-0187ec82b403#bm458044d3-e8ba-4d73-9e29-0187ec82b403">

[siva guthula]

Hello Jermane,

Please check if SQL service is running > Open services.msc > SQL service > go to properties and change to Local > restart all services and check.

Regards,
Siva