Hi,

Below is the link which you can use to troubleshoot the unexpected server error.

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008062510082748

Regarding the update on the client which can be due to multiple reasons.
Things to check

1. Under Admin --> Servers --> Select local site (My site)
2. Under tasks select show liveupdate content.
3. You will be able to find the definitions which are published by SEPM.
4. If the definitions are upto date on that location in that case you need to troubleshoot why the definitions are not distributed to the clients.

You can collect the sylink logs from the one of the machine which is not upto date and paste the same on forum and we will proceed further from the same.

Regards,
Nirav Mistry.

Hi guys

Thanks for feedback, but non of your links worked .
After making the database respond successfully and a reboot, the same error still apperar.

Nirav: how do I collect the sylink logs ?
 

The definition files on the manager server is up to date

Have u install SEPM by taking RDP or Dameware or VNC ?

Repair the SEPM by using ILO or from console .

We had the same issue when we have installed MR3 but resolved by reparing the sepm using Direct console.

Kindly find the below URL
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008030509272248

I have now repaired my installation, despite it was already installed with the "mstsc /admin"  switch.

But still the same error message.

Any other suggestions I should try that could resolve my problem ?

Appreciate all help I can get. 

HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SEP\smc\sylink

Creat new deword ther name DumpSylink and edit it and give path for sylink log "c:\sylink.log"

C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs

scm-server-0.log 

did u see anything error

did u delete any packages , assigend to the clients ?

Here is the svm-server-0.log

I do find it a bit odd, that the JAVA version is 1.5.0_15, since i have installed java 6 update 15 ?

2009-08-19 03:43:52.565 SEVERE: ================== Server Environment ===================
2009-08-19 03:43:52.565 SEVERE: os.name = Windows 2003
2009-08-19 03:43:52.565 SEVERE: os.version = 5.2
2009-08-19 03:43:52.565 SEVERE: os.arch = x86
2009-08-19 03:43:52.565 SEVERE: java.version = 1.5.0_15
2009-08-19 03:43:52.565 SEVERE: java.vendor = Sun Microsystems Inc.
2009-08-19 03:43:52.565 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
2009-08-19 03:43:52.565 SEVERE: java.vm.version = 1.5.0_15-b04
2009-08-19 03:43:52.565 SEVERE: java.home = F:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
2009-08-19 03:43:52.565 SEVERE: catalina.home = F:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
2009-08-19 03:43:52.565 SEVERE: java.user = null
2009-08-19 03:43:52.565 SEVERE: user.language = en
2009-08-19 03:43:52.565 SEVERE: user.country = GB
2009-08-19 03:43:52.565 SEVERE: scm.server.version = 11.0.4202.75
2009-08-19 03:43:54.721 SEVERE: ================== StartClientTransport ===================
2009-08-19 03:43:55.565 SEVERE: Schedule is started!
2009-08-19 03:44:09.722 SEVERE: Unknown Exception in: com.sygate.scm.server.task.PackageTask
java.lang.NullPointerException
 at com.sygate.scm.common.configobject.Util.getLastestT(Util.java:47)
 at com.sygate.scm.common.configobject.Util.getLastestT(Util.java:43)
 at com.sygate.scm.server.publisher.compiler.logicaobject.FwFirewallRuleGroupObject.createNicGroup(FwFirewallRuleGroupObject.java:254)
 at com.sygate.scm.server.publisher.compiler.logicaobject.FwFirewallRuleGroupObject.getNicGroupLinkName(FwFirewallRuleGroupObject.java:207)
 at com.sygate.scm.server.publisher.compiler.logicaobject.FwFirewallRuleGroupObject.compile(FwFirewallRuleGroupObject.java:121)
 at com.sygate.scm.server.publisher.compiler.logicaobject.FwFirewallPolicyObject.buildFirewallPolicy(FwFirewallPolicyObject.java:525)
 at com.sygate.scm.server.publisher.compiler.logicaobject.FwFirewallPolicyObject.buildFirewallPolicy(FwFirewallPolicyObject.java:242)
 at com.sygate.scm.server.publisher.compiler.logicaobject.FwFirewallPolicyObject.compile(FwFirewallPolicyObject.java:214)
 at com.sygate.scm.server.publisher.compiler.Spa50ProfileCompiler.buildFirewallPolicy(Spa50ProfileCompiler.java:1851)
 at com.sygate.scm.server.publisher.compiler.Spa50ProfileCompiler.compile(Spa50ProfileCompiler.java:794)
 at com.sygate.scm.server.task.PackageTask.updateProfile(PackageTask.java:819)
 at com.sygate.scm.server.task.PackageTask.updateGroup(PackageTask.java:766)
 at com.sygate.scm.server.task.PackageTask.checkGroupDirectory(PackageTask.java:678)
 at com.sygate.scm.server.task.PackageTask.run(PackageTask.java:286)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
2009-08-19 03:44:26.441 SEVERE: Unknown Exception in: com.sygate.scm.server.task.PackageTask
java.lang.NullPointerException
2009-08-19 03:44:42.989 SEVERE: Unknown Exception in: com.sygate.scm.server.task.PackageTask
java.lang.NullPointerException

And it just repeats itself after this.

i see that it says about package task

com.sygate.scm.server.task.PackageTask

did u delete any packages , assigend to the clients ?

The package deployed to all clients are the 11.0.4202.75
All the old packages are removed.

The SEPM is also been reinstalled on another location (f: drive) and clients been redeployed.
They are reportin

If old packages are deleted that could be the problem.

long back had this issue.

if you delete the package, u will get these error message

the only way is to re-add the deleted packages in the
SEPM, the error should go away

Give it a shot , it should work.

After a total reinstall I do not see the relation. :o)

But I will offcourse try.

I will post when I have tried. :o)

I have now added the 11.0.4014.26 , 32 and 64 bit packages and restarted the SEPM service.

used the " Add client Install package"  under admin - install packages.
 
Still the same error message.

Thanks for all the help, but am afraid non of the suggestion helped me.

I have now installed the SEPManager on another server, redeployed packages to the clients and everything works as it should.

Still not sure why the installation failed on the primary server.