Endpoint Protection

Hi,

My Symantec SQL database service is getting stopped weekly once at monday or tuesday..why it is happening? but when i start the services it is working fine?

do you have the logs , when the services are stopped?

Same duplicate thread, You don't be provide scm-server-0.log last time

https://www-secure.symantec.com/connect/forums/sql-service-stops-sepm

Hi,

Where we can find the logs?

Check in the log file (scm-server-0.log) located in \Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\logs, look for any errors.

Hi,

I found the logs..please have it

Attachment(s)

scm-server-0_26.zip   76 KB 1 version

THREAD 7216 WARNING: Log table switched to: AGENT_TRAFFIC_LOG_1, old table estimated row count: 54781, to add row count in new table: 6340, last switch time: 2012-07-30 11:28:39

What is the size of the sem5 database and the sem5.log file?

As mentioned before, we would need to have access to scm-server-0.log. However, the most important data in my opinion would be SQL Server Error logs, as you said this is SQL Server service that is crashing.

Such issues might appear if you have limited memory available on SQL Server. You may try to increase RAM and see if it helps.

If your sem5 database and the sem5.log file size high folow this process.

Try these Steps as provided below:

1. Log in to the Sep Manager.
2. Click Admin and select Servers.
3. Select the localhost under Servers.
4. Under Tasks, Select Edit Database Properties.
5. In the General tab under Database Maintenance Tasks.
6. Select the checkboxes next to Truncate the database transaction logs and Rebuild Indexes.
7. Click OK to apply the changes.

It is required to truncate log immediately, change the frequency to daily and enter current System time In the start time box. You will be able to truncate log Immediately.

If the issue still not resolved, then 

• Rename sem5.log file to sem5.log.old.
• Try Forcing to create sem5.log file again by running dbsrv11.exe from C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\ location.
• Once, the sem5.log starts getting created again, Delete the old sem5.log file.

Check this forums

https://www-secure.symantec.com/connect/forums/database-size-and-site-properties

Following errors:

"2012-07-30 09:49:30.712 THREAD 6707 SEVERE: Unexpected server error. in: com.sygate.scm.server.task.SecurityAlertNotifyTask
java.sql.SQLException: There is insufficient system memory in resource pool 'internal' to run this query.
com.sygate.scm.server.util.ServerException: Unexpected server error."

If you are using SQL Server 2008, please refer to this article:
http://support.microsoft.com/kb/982854

As suggested previously, try to increase RAM available on SQL Server. It might be worth also to reduce the size of the database, by decreasing number of logs to keep (Admin > Server > Local Site Properties > Log settings). Moreover, as NotifyTask is related to notifications, I would recommend you to temporarely disable all your notifications/scheduled reports.

If you are using Small Business edition with Embedded database, please upgrade to 12.1 RU1 MP1 in order to fix a problem with Transaction log (see defect 2660649 in http://www.symantec.com/docs/TECH187656).

To upgrade: http://www.symantec.com/docs/TECH187753

PLease follow these steps:-

1) Stop the Symantec Endpoint Protection Manager and Symantec Embedded Database services. 
2) Rename or delete the current sem5.log
3) Click Start > Run and type CMD then click OK 
4) In the Command Prompt type:
    For 32-bit: CD C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\
    For 64-bit: CD C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\ASA\win32\
5) Press Enter. This will change directories to the folder containing dbsrv11.exe. 
6) To force the recreation of sem5.log, type:
    For 32-bit: dbsrv11 -f "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db"      (There is a space after -f and "C:\...)
    For 64-bit: dbsrv11 -f "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db"     (There is a space after -f and "C:\...)
7) Press Enter
8) Click Start > Run and type services.msc then click OK
9) Start the Symantec Endpoint Protection Manager and Symantec Embedded Database services.

Hi,

Iam not using Embedded database iam using SQL

Try running a repair on the SEPM

In truncate data logs i choose as weekly once on sunday...so only it is not working??

Hello Srikanth,

The truncation of the logs and the rebuilt of the indexes have to be continuous. It would not affect your server performance.

Ya..but the service is only stopping..

As mentioned by John Q:-

"2012-07-30 09:49:30.712 THREAD 6707 SEVERE: Unexpected server error. in: com.sygate.scm.server.task.SecurityAlertNotifyTask
java.sql.SQLException: There is insufficient system memory in resource pool 'internal' to run this query.
com.sygate.scm.server.util.ServerException: Unexpected server error."

If you are using SQL Server 2008, please refer to this article:
http://support.microsoft.com/kb/982854

As suggested previously, try to increase RAM available on SQL Server. It might be worth also to reduce the size of the database, by decreasing number of logs to keep (Admin > Server > Local Site Properties > Log settings). Moreover, as NotifyTask is related to notifications, I would recommend you to temporarely disable all your notifications/scheduled reports.

If you are using Small Business edition with Embedded database, please upgrade to 12.1 RU1 MP1 in order to fix a problem with Transaction log (see defect 2660649 inhttp://www.symantec.com/docs/TECH187656).

To upgrade: http://www.symantec.com/docs/TECH187753

I will install the cumulative update pack and check.

Please do the following and revert back

• Rename sem5.log file to sem5.log.old.
• Try Forcing to create sem5.log file again by running dbsrv11.exe from C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\ location.
• Once, the sem5.log starts getting created again, Delete the old sem5.log file

Regards