SEPM 11 unable to update the 32bit definition file using .jdb file

Created: 22 Feb 2012 | Updated: 23 Feb 2012 | 11 comments

Hi All,

I'm having a problem on my SEPM 11 which install in Windows Server 2003. Usually I download the jdb file from symantec and put it into C:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\inbox\content\incoming to update the definition file in SEPM and distribute to the client. But currently whenever I put the jdb file at the directory show above, my SEPM only able to update the 64bit definition file. The 32bit definition file remain on 2011 Dec 11 rev 006. (Please refer to the print screen below).

By the way I also copy the scm-server-0.log for you guy reference for the message I have when loading in a jdb file.

2012-02-22 16:38:12.205 FINE: lockProcessState start for owner:ConfigServerHandler.processLUContent toWaitForUnlock:false
2012-02-22 16:38:12.205 FINE: markProcessState return state:1
2012-02-22 16:38:12.205 FINE: lockProcessState return state:1 for process owner:ConfigServerHandler.processLUContent toWaitForUnlock:false
2012-02-22 16:39:01.189 SEVERE: Unknown Exception in: com.sygate.scm.server.consolemanager.requesthandler.ConfigServerHandler
java.io.FileNotFoundException: C:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\inbox\content\tmp77ce.tmp\virscan8.dat (The system cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at com.sygate.scm.util.ZipUtil.zipFiles(ZipUtil.java:445)
at com.sygate.scm.util.ZipUtil.zipFiles(ZipUtil.java:419)
at com.sygate.scm.util.ZipUtil.zipData(ZipUtil.java:336)
at com.sygate.scm.util.ZipUtil.zipData(ZipUtil.java:306)
at com.sygate.scm.server.consolemanager.requesthandler.ConfigServerHandler.writeContentToOutdir(ConfigServerHandler.java:1836)
at com.sygate.scm.server.consolemanager.requesthandler.ConfigServerHandler.saveLUContent(ConfigServerHandler.java:1535)
at com.sygate.scm.server.consolemanager.requesthandler.ConfigServerHandler.processLUContent(ConfigServerHandler.java:568)
at com.sygate.scm.server.consolemanager.requesthandler.ConfigServerHandler.handleRequest(ConfigServerHandler.java:231)
at com.sygate.scm.server.consolemanager.RequestHandler.handleRequest(RequestHandler.java:116)
at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:79)
at com.sygate.scm.server.servlet.ConsoleServlet.doPost(ConsoleServlet.java:82)
at com.sygate.scm.server.servlet.ConsoleServlet.doGet(ConsoleServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:199)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:139)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:198)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2460)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:133)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:119)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:127)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:157)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:595)
2012-02-22 16:39:01.205 FINE: unlockProcessState Done for A923C3780A0800450093068A6D625287 (ConfigServerHandler.processLUContent)
2012-02-22 16:39:01.377 FINE: lockProcessState start for owner:ConfigServerHandler.processLUContent toWaitForUnlock:false
2012-02-22 16:39:01.392 FINE: markProcessState return state:1
2012-02-22 16:39:01.392 FINE: lockProcessState return state:1 for process owner:ConfigServerHandler.processLUContent toWaitForUnlock:false
2012-02-22 16:39:01.392 INFO: ConfigServerHandler>> Content 'SESM Virus Definitions Win64 (x64) v11 MicroDefsB.CurDefs SymAllLanguages' revision '120221002' already exists.
2012-02-22 16:39:01.408 FINE: unlockProcessState Done for A923C3780A0800450093068A6D625287 (ConfigServerHandler.processLUContent)
2012-02-22 16:39:01.767 INFO: RapidResponseContentTask.installContent(): Info >> return code = [0]
Rapid response content get installed successfully.

I have try a lot of method / workaround from the internet which are;

Uninstall and reinstall the SEPM
Clear the corrupted def file by remove all the files in "C:\Program Files\Common Files\Symantec Shared\VirusDefs", "C:\Program Files\Common Files\Symantec Shared\SymcData\sesmvirdef32 " and clear the registery file.

Discussion Filed Under:

Security, Endpoint Protection (AntiVirus) - 11.x, Endpoint Protection (AntiVirus), Error messages

Comments RSS Feed

Comments 11 Comments • Jump to latest comment

AJ_01

SEPM 11 unable to update the 32bit definition file using .jdb file - Comment:24 Feb 2012 : Link

Have you tried to update manually?

Regard

SMLatCST Partner Accredited

SEPM 11 unable to update the 32bit definition file using .jdb file - Comment:24 Feb 2012 : Link

...this article?

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

http://www.cstl.com/

Anthony@Lonza

SEPM 11 unable to update the 32bit definition file using .jdb file - Comment:27 Feb 2012 : Link

Hi AJ_01,

We cannot perform the manual Live Update because the machine did not have internet connection. Usually what we do is download the JDB file and paste it on C:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\inbox\content\incoming as I mention in my first post.

Hi SMLatCST,

I have try the solution from the link before which is clear up / delete the folder / files and manually put in the JDB file into the incoming folder to update the definition file. But unfortunetly it does not work for it.

I even follow a solution I found in Symantec forum which is removing all the related folder / files and delete the registery in the machine and it does not work as well.

DCOMP

SEPM 11 unable to update the 32bit definition file using .jdb file - Comment:27 Feb 2012 : Link

Hi,

After you downloading the jdb, its in zip format.

You can rename the extention vdxxxxx.zip to vdxxxxx.jdb.

Then check.

Anthony@Lonza

SEPM 11 unable to update the 32bit definition file using .jdb file - Comment:27 Feb 2012 : Link

Hi DCOMP,

Yes we know that. Previously (before Mid Dec 2011) all the JDB file we download and paste on the incoming folder are working fine for the 32bit definition file.

But after Mid Dec 2011, whatever JDB file we downloaded and paste on the incoming folder, it only update the 64bit definition file and not the 32bit. I notice that there is an error message whenever we paste the JDB file on the incoming folder which show in my first posted. (Please refer to the message below)