Explanation: The database may be corrupted.
Solutions:
A. Verify if the database is corrupted.
The following are signs of a corrupted database. Contact your Support provider if you believe the database is corrupted but does not exhibit any of these symptoms.
The OfficeScan clients cannot run the Update Now task.
The OfficeScan clients can ping the OfficeScan server and telnet to the listening port.
The OfficeScan Master Service is running.
The OfficeScan client reports failure to connect to the OfficeScan server when running Update Now.
The \PCCSRV\HTTPDB folder has a lot of *.TMP files.
The following message displays when changing the scan settings of OfficeScan clients from the Web console: "Some of selected item(s) not exist! Please refresh the client tree, and try again."
The OfficeScan clients disappear from the OfficeScan console.
OfficeScan clients do not receive the Scan Now command initiated from the web console.
B. Fix a corrupted OfficeScan database.
Export and then import client settings.
Delete the *.TMP files in the \PCCSRV\HTTPDB folder because these are not necessary.
Apply the latest OfficeScan patch to prevent future database corruption.
C. Restore a backed up OfficeScan database to replace a corrupted database.
Note: Make sure you configure database backup settings to ensure that you have backup files available when you need to replace the corrupted database.
Stop the OfficeScan Master Service.
Copy the database backup files in the \DBBackup folder to the \PCCSRV\HTTPDB folder.
Restart the OfficeScan Master Service.
Explanation: The OfficeScan database files may be corrupted, locked, or too large to back up.
Solution:
Go to the \PCCSRV\HTTPDB folder and delete any TMP files inside.
Upgrade OfficeScan.
OR
Stop all OfficeScan services. Change the Startup type of the services to "Disabled" by right-clicking the services and clicking Properties.
Restart the server computer.
Install OfficeScan.