The issue is addressed in MP2. Upgrade your current version of SCSP to SCSP  5.2.6 MP2.

SCSP installation caused Windows server restart, Hanging and BSOD.

http://www.symantec.com/business/support/index?pag...

What Windows Event errors are you seeing?

None Error. Oly Information Events.

I recommmend you open a case with support for your issue. We can then get the engineers involved to find root cause of your SCSP issue.

Online Portal - https://mysupport.symantec.com/

Phone - http://www.symantec.com/business/support/contact_t...

fernando

As Cycletech recommend pls start a case with Symc. Additionally some troubleshooting steps to go through for everyone to see. Some initial questions to get better background:

1. Is this a new installation? How many agents do you have reporting into the machine?

2. Are you running with HIPS enabled, if so with the null policy or with a full policy (strict/core etc..)?

3. On larger implementation you should not be running the built in SQL instance with the free SQL express. Additionally it is not recommended nor (i believe) supported to have your backend database running in a virtual environment on larger deployments. It has to do with virtual IO limits of VMware virtual disk drivers and/or LUN connections (I can get more into that if you would like). This can drastically slow down the entire application.

4. dump the server into debug mode with the following (reminder to disable prevention on the server if you have it turned on as HIPS enabled since it will self protect the CSP files):

- navigate (on the CSP management server) to <CSP install root>\Server\tomcat\conf

- right click sis-server.properties, remove the read-only attrib

- edit sis-server.properties: uncomment the follow lines (remove the #):

Change INFO to TRACE

#sislogger.loglevel=INFO
#sislogger.logsize=10M
#sislogger.logcount=10

then the following "logger" lines changing WARN to TRACE:

#sisalertlogger.loglevel=WARN
#sisalertlogger.logsize=10M
#sisalertlogger.logcount=10

#sisagentlogger.loglevel=WARN
#sisagentlogger.logsize=10M
#sisagentlogger.logcount=10

#sisconsolelogger.loglevel=WARN
#sisconsolelogger.logsize=10M
#sisconsolelogger.logcount=10

<save the file>

- restart the sisserver management service (Symantec Critical System Protection Manager)

- Let the server run, log into the console, perform a few tasks

- If your company policy allows it (make sure to scrub any private data), after about 15 minutes or so, navigate to <csp install root>Server\tomcat\logs and send/post last10megs.log

- Return to the steps above and the sis-server.properties. Place back comments on the uncommented lines you just removed. save file. Restart management server.

The trace level debug will provide exact queries and stored procedures being initiated by the console. From there the timing can be compared on each operation to see if there is a specific action that is taking to long to return a success/failure code to the console.

Support will need this information as well to move things along quicker.

Hi Fernanado

If you havn't uninstalled that Agent, Please collect the installation logs and attach it here. Also Uninstall 5.2.6 Agent and install 5.2.4 Agent , That way you can check if it is product version related issue or Environmental issue.

Hope this helps.

Regards

Vick