Endpoint Protection Small Business Edition

 View Only

  • 1.  Symantec 12.1.5 Log Says No Disk Space, But There Is Plenty

    Posted Apr 27, 2015 02:11 PM
      |   view attached

    A customer has a very strange problem.  They have the latest version of Symantec Endpoint Protection Small Business Edition (12.1.5).  None of the client workstations or two servers including a dedicated server for the Symantec Endpoint Protection Manager will update.  This is a small network with less than 10 computers including servers.  I have removed SEP twice and reinstalled it with no change to the situation.  I have tried using the server configuration tool three time with no results.  None of the computers can be brought into their respective groups.  I looked at the scm-server-0.log and this is what is reported repeatedly:

    2015-04-27 13:41:59.978 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:41:59.978 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:42:09.844 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:42:09.985 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:42:09.985 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:42:19.851 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:42:20.006 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:42:20.006 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:42:29.857 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:42:29.981 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:42:29.981 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:42:39.863 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:42:39.988 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:42:39.988 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:42:49.869 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:42:50.072 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:42:50.072 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:42:59.875 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:42:59.953 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:42:59.953 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:43:09.882 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:43:09.975 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:43:09.975 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:43:19.888 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:43:19.997 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:43:19.997 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:43:29.894 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:43:30.003 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:43:30.003 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:43:39.900 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:43:40.040 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:43:40.040 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:43:49.922 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:43:50.016 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:43:50.016 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:43:59.928 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:44:00.006 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:44:00.006 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:44:09.934 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:44:10.059 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:44:10.059 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:44:19.941 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:44:20.065 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:44:20.065 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:44:29.947 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:44:30.056 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:44:30.056 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:44:39.969 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:44:40.125 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:44:40.125 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
    2015-04-27 13:44:49.959 THREAD 31 SEVERE: Disk space below critical, Updating server health
    2015-04-27 13:44:50.084 THREAD 31 SEVERE: Stop ClientTransport.
    2015-04-27 13:44:50.084 THREAD 31 SEVERE: There is not enough disk space, Stopping Client Transportion.
     

    As I said this is a small network.  The Symantec Endpoint Protection Manager is installed on the F drive, which it has been for years.  There is plenty of disk space based on system requirements.  The C drive has 11 GB free and the F drive has 17.7 GB free. I attached an image of a disk size screen shot.

    This all started when I upgraded the server to ver 12.1.5.  Can anyone tell me how to fix this?  It appears there is a component within the manager that is reading the disk space wrong and I don't know how to fix it.

    Tony

     

     

     



  • 2.  RE: Symantec 12.1.5 Log Says No Disk Space, But There Is Plenty

    Posted Apr 28, 2015 12:30 PM

    Out of curiosity have you run symhelp to see what it shows?



  • 3.  RE: Symantec 12.1.5 Log Says No Disk Space, But There Is Plenty

    Posted Apr 28, 2015 01:32 PM

    Have not run symhelp.  I'm not familiar with it.  Isn't it a diagnostic tool used by Symantec engineers?  I will gladly run it if you or someone can help me interpret the results.



  • 4.  RE: Symantec 12.1.5 Log Says No Disk Space, But There Is Plenty

    Posted Apr 28, 2015 01:42 PM

    Yes, it is a free download

    Download the Symantec Help (SymHelp) diagnostic tool to detect Symantec product issues



  • 5.  RE: Symantec 12.1.5 Log Says No Disk Space, But There Is Plenty
    Best Answer

    Posted Apr 28, 2015 01:49 PM

    could be a permission issue , check this discussion

    http://www.symantec.com/connect/forums/sepm-claiming-there-not-enough-disk-space



  • 6.  RE: Symantec 12.1.5 Log Says No Disk Space, But There Is Plenty

    Posted Apr 28, 2015 02:06 PM
      |   view attached

    Attached is the Symhelp report.  It does state that 16 GB is required on the C drive, but that doesn't make sense.  I had the previous version of SEPM installed on this server with less disk space and it worked fine.  Also, SEPM is not installed on C.  It is installed on F, which has more than 16 GB of space.

    Attachment(s)

    zip
    [JDFPA-AV]__2015-04-28__13-47-38_1.zip   1.28 MB 1 version


  • 7.  RE: Symantec 12.1.5 Log Says No Disk Space, But There Is Plenty

    Posted Apr 28, 2015 02:19 PM

    What version of SEPM that worked was installed? I know the 16GB disk requirement goes back to at least 12.1.2.

    Also, is all of SEPM installed to F? I know that it can be installed to another drive but some files will stay on C by default (hard-coded).



  • 8.  RE: Symantec 12.1.5 Log Says No Disk Space, But There Is Plenty

    Posted Apr 28, 2015 02:43 PM

    Thanks, Rafeeq.  That link led me to the solution.  I had already changed the web service to the Local System account and after reading the posts from the link you supplied, I changed the SEPM service to the Local System account.  All the clients reported in and everything is working.

    I applaud Symantec for trying to make SEP more secure, but it has not been executed well.  I have had problems at just about everywhere an upgrade to 12.1.5 has taken place.  Perhaps when they introduce the next update, they will have it working so it can be used.

    Tony