Endpoint Protection

 View Only
  • 1.  After Upgrade to SEP 12.1.7004.6500 , the Monitors Tab shows Log on Screen

    Posted Jul 26, 2016 04:59 AM
      |   view attached

    Dear Support,

    We have large environment of 5000+ machines.

    Recently, 2 weeks ago we had upgraded from 12.1.6MP4 to 12.1.6 MP 5 ( 12.1.7004.6500).

     

    Now I get only in Monitors Tab the log on screen. Even if the page is refreshed, it keeps appearing, until, I log off and log in.

    Below is extract from the apache\logs\ reporting log


    2016-07-26 08:11:47 Login:start
    2016-07-26 09:13:43 INFO:available token: d20386ca5d3996b80555e935ce4bb71b6cb2647febb5464ee9a1edefc34a2b38
    2016-07-26 09:13:43 INFO:allowed token: secondary_token 226b696379a4963255845ec58d367ef8ac05b773f323e1e8b431c2c29de0b52e
    2016-07-26 09:13:43 ERROR:form verification failed in commandstatus.php:  form: auto referer:https://10.26.5.132:8445/Reporting/command/commandstatus.php?token=536d60e770860eb9f2af79d8f33579985d4a84674b63391abbfdf5d2fcc3340b
    2016-07-26 09:13:47 INFO:available token: 536d60e770860eb9f2af79d8f33579985d4a84674b63391abbfdf5d2fcc3340b
    2016-07-26 09:13:47 INFO:allowed token: secondary_token 23df3c0a4e08f402d106fa9dda39771526b83924a85420f2bde346acbf11e2a8
    2016-07-26 09:13:47 ERROR:form verification failed in commandstatus.php:  form: FilterForm referer:https://10.26.5.132:8445/Reporting/command/commandstatus.php?token=536d60e770860eb9f2af79d8f33579985d4a84674b63391abbfdf5d2fcc3340b
    2016-07-26 11:17:08 INFO:session.verifyFormToken oldtime is 1469506628.5152 tokentime is [26-Jul-2016 11:17:08 Europe/Moscow] PHP Warning:  extract() expects parameter 1 to be array, string given in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Inetpub\Reporting\Reports\reports.php on line 331

    2016-07-26 09:18:08 Login:start
    2016-07-26 09:18:29 Login:start
    2016-07-26 11:19:42 INFO:DashboardActionSummary>> cache #3 hit at 2016-07-26 11:19:42
    2016-07-26 11:19:43 INFO:DashboardActionSummary>> cache #4 miss at 2016-07-26 11:19:43
    2016-07-26 11:19:44 INFO:DashboardActionSummary>> cache #6 miss at 2016-07-26 11:19:44
    2016-07-26 11:19:49 INFO:EndpointStatus>> cache miss at 2016-07-26 11:19:49
    2016-07-26 11:19:56 INFO:DashboardActionSummary>> cache #3 hit at 2016-07-26 11:19:56
    2016-07-26 11:19:56 INFO:DashboardActionSummary>> cache #4 hit at 2016-07-26 11:19:56
    2016-07-26 11:19:56 INFO:DashboardActionSummary>> cache #6 hit at 2016-07-26 11:19:56[26-Jul-2016 08:21:46 UTC] PHP Warning:  date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Php\Include\Util\UtilClass.php on line 1198

    2016-07-26 08:21:46 Login:start[26-Jul-2016 09:31:22 Europe/London] PHP Warning:  session_destroy(): Session object destruction failed in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Php\Include\Resources\session.php on line 262
    [26-Jul-2016 08:31:46 UTC] PHP Warning:  date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Php\Include\Util\UtilClass.php on line 1198

    2016-07-26 08:31:46 Login:start
    2016-07-26 11:31:51 INFO:DashboardActionSummary>> cache #3 hit at 2016-07-26 11:31:51
    2016-07-26 11:31:55 INFO:DashboardActionSummary>> cache #4 miss at 2016-07-26 11:31:55
    2016-07-26 11:32:05 INFO:session.verifyFormToken oldtime is 1469507525.6629 tokentime is
    2016-07-26 11:32:05 INFO:EndpointStatus>> cache miss at 2016-07-26 11:32:05
    2016-07-26 11:32:15 INFO:DashboardActionSummary>> cache #6 miss at 2016-07-26 11:32:15[26-Jul-2016 11:32:16 Europe/Moscow] PHP Warning:  extract() expects parameter 1 to be array, string given in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Inetpub\Reporting\Inventory\inventorylist.php on line 141

    2016-07-26 11:32:22 INFO:DashboardActionSummary>> cache #3 hit at 2016-07-26 11:32:22
    2016-07-26 11:32:22 INFO:DashboardActionSummary>> cache #4 hit at 2016-07-26 11:32:22
    2016-07-26 11:32:22 INFO:DashboardActionSummary>> cache #6 hit at 2016-07-26 11:32:22
    2016-07-26 11:32:24 INFO:EndpointStatus>> cache hit at 2016-07-26 11:32:24
    2016-07-26 11:32:57 INFO:session.verifyFormToken oldtime is 1469507577.6292 tokentime is 1469521936.7896[26-Jul-2016 11:32:58 Europe/Moscow] PHP Warning:  extract() expects parameter 1 to be array, string given in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Inetpub\Reporting\Inventory\inventorylist.php on line 141

    2016-07-26 11:33:04 INFO:session.verifyFormToken oldtime is 1469507584.4454 tokentime is 1469521936.7896[26-Jul-2016 11:33:04 Europe/Moscow] PHP Warning:  extract() expects parameter 1 to be array, string given in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Inetpub\Reporting\Inventory\inventorylist.php on line 141

    2016-07-26 11:33:06 INFO:session.verifyFormToken oldtime is 1469507586.865 tokentime is 1469521936.7896
    2016-07-26 11:33:07 ERROR:I18nInventory could not translate key: [26-Jul-2016 11:34:09 Europe/Moscow] PHP Warning:  extract() expects parameter 1 to be array, string given in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Inetpub\Reporting\Inventory\ajax.php on line 66
    [26-Jul-2016 11:34:10 Europe/Moscow] PHP Warning:  extract() expects parameter 1 to be array, string given in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Inetpub\Reporting\Inventory\ajax.php on line 66

    2016-07-26 11:34:11 INFO:session.verifyFormToken oldtime is 1469507651.2755 tokentime is 1469521936.7896

     

     



  • 2.  RE: After Upgrade to SEP 12.1.7004.6500 , the Monitors Tab shows Log on Screen

    Broadcom Employee
    Posted Jul 26, 2016 07:53 AM

    Hi,

    Thank you for posting your query on Symantec community.

    1) I will suggest to repair the SEPM first

    2) In the logs it showing timezone related errors 

    Modify PHP configuration file :c:\program files(x86)\symantec\symantec endpoint protection manager\php\php.ini
    Add one line about  local time zone: date.timezone="Continent/City", for example  : date.timezone==" Asia/Shanghai"

    these setting will make SEPM to display in Beijing time 

    Restart the SEPM service

     

     



  • 3.  RE: After Upgrade to SEP 12.1.7004.6500 , the Monitors Tab shows Log on Screen

    Posted Jul 27, 2016 03:18 AM

    Thank you Chetan for the reply. But will that resolve the error????

    This error has been there since months and years . We had a similar issue , which was fixed by the Symantec team. At that time also, the apache \logs showed the time logs . The issue was Log on screen appearing on the HOME/Monitors/Reports page. The issue was then fixed by assigning more Space to SQL and upgrading Lumension on the SEPM server.

     

     



  • 4.  RE: After Upgrade to SEP 12.1.7004.6500 , the Monitors Tab shows Log on Screen

    Posted Jul 27, 2016 06:17 PM

    Unfortunately the only want to know is test. But this issue has more then one cause and it could even be a 3rd party app interfering with php causing the issue. The only way to know for sure is test, please create a case with support to resolve this issue.



  • 5.  RE: After Upgrade to SEP 12.1.7004.6500 , the Monitors Tab shows Log on Screen

    Broadcom Employee
    Posted Jul 28, 2016 06:43 AM

    If there is any special character in the hostname, If yes at the SEPM login page enter the server IP instead of the server name. 

    Did you perform SEPM repair?

    Post  the scm-server-0.log file present under tomcat\logs folders.