Endpoint Protection

I upgraded our SEMP from 11.0.6-MP3 to 11.0.7-MP1.  I went through and deleted a number of old client install packages.  There were a few times where the database appeared to time out during this process and had to rebuild itself after a reboot.  The last install package I was trying to delete was 11.0.7.  It took a couple tries with the database locking up, but it eventually disappeared from the list.  Now, everytime I click on Install packages the following error is logged:

The binary file [hex formatted numbers] referred at the physical file [hex formatted numbers], which is referred at the software package [hex formatted numbers and directory path], does not exist.

I am guessing there is an inconsistency in the database.  Is there any easy fix to this?

Thanks,

Hi,

have you tried by running upgrade.bat ?

You will find it under C:or Installed drive\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\upgrade.bat

Also try to repair SEPM from add/remove programs.

If after running upgrade.bat as suggested by Chetan, it is still not working, you can try to repair your installation.  It seems something has gotten corrupted.

Do you have a replication server in place?

If not, I would suggest you be pro-active and implement Disaster recovery immediately.

http://www.symantec.com/business/support/index?page=content&id=TECH102333

What you are indicating could be bad sectors on the disk or a failing disk itself.

Are you seeing ATAPI errors in the event logs when you were trying to delete packages, possibly a loss of communication with the dive?

After preparing disaster recovery, try and run some diagnostics on the drive(s) to see if any are having issues/troubles.

The upgrade to 11.0.7-MP1 completed successfully.  However, it was after the upgrade that I wanted to clean out older install packages from the management console.

The SEMP server is a vmware virtual machine and is not reporting hardware trouble.

Okay, well that rules out the HD going bad.

Have you tried to run a repair on the SEPM?  It should put the files back where they need to be. 

I contacted Symantec Support regarding the stated problem.  The problem was resolved by reimporting the client package that produced the error after deleting it.  The client package file was found under SEPM\Packages of the version that was deleted.  I named the client package with the same name as noted in the error.  Once the import was successful, I then deleted the package and no errors persisted.