Endpoint Protection

 View Only
  • 1.  Hi all

    Posted Dec 02, 2009 12:09 AM
    I'm encountering problem with sep reports tab, it keeps on giving me an update an error  bad gateway during generating any kind of reports.

    Please advise!


  • 2.  RE: Hi all

    Posted Dec 02, 2009 12:11 AM
    You must be using proxy, try disabling the proxy in internet explorer and create  a report
    if you are having enhanced settings in internet explorer disable that too and try again should work.

    if the above two fails you should try thes steps

    Unable to communicate with reporting component" and BAD GATEWAY error on SERVER/reporting

    http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/5f71e9e114cc657a802575d100495d8e?OpenDocument

    https://www-secure.symantec.com/connect/forums/bad-gateway-error


  • 3.  RE: Hi all

    Posted Dec 02, 2009 12:17 AM
    Did you install the server on the correct system requirements?There some tools available on support tool folder.


  • 4.  RE: Hi all

    Posted Dec 02, 2009 12:19 AM
    Yes, it is 4 gb of ram.I'm also using sql database installed on a remote pc.Version of sep is ru5.


  • 5.  RE: Hi all

    Posted Dec 02, 2009 12:24 AM
    Please let me know how it goes


  • 6.  RE: Hi all
    Best Answer

    Posted Dec 02, 2009 12:24 AM
    Good, thanks for the info I suggest to follow the procedure first below found the this link  : 


    In most cases, large reports can successfully be updated after implementing FastCGI, and then configuring increased timeout and memory limit values in the Php.ini and fcgiext.ini files.
    Install FastCGI, and ensure that it is configured correctly.
    FastCGI is a third-party tool from Microsoft which can improve the performance of the IIS component that the SEPM uses for Home, Monitors and Reporting. Refer the document "FastCGI_Setup_Readme.pdf" at "Tools\NoSupport\FastCGI\".

    If FastCGI is not configured correctly, IIS will use CGI and set the default time out 300 seconds (5 minutes). This will often lead to time-outs when exporting very large reports.

    Please note: the fcgiext.ini file is often not created automatically upon install. This may need to be manually created. A sample file:
    fcgiext.ini (at directory "C:\WINDOWS\system32\inetsrv\fcgiext.ini"):

    [Types]
    php=PHP

    [PHP]
    ExePath=C:\Program Files\Symantec\Symantec Endpoint Protection Manager\PHP\php-cgi.exe
    EnvironmentVars=PHP_FCGI_MAX_REQUESTS:10000
    InstanceMaxRequests=10000
    RequestTimeout=30000
    ActivityTimeout=30000

    Note: The sample fcgiext.ini file illustrated above uses the default 32-bit path for the SEPM install. This string will need to reflect the correct path, if the SEPM is installed on a 64-bit server or to a non-default location.


    Configure ...\Symantec Endpoint Protection Manager\Php\Php.ini to Add "memory_limit = 512M" and change the max_execution_time timeout value
    Modify the default php.ini file so that it can interact with FastCGI and have ample resources at its disposal.
    1.        Start Windows Explorer.
    2.       Go to the following folder:

    Default location on SAV Reporter: C:\Program Files\Symantec\Reporting Server\PHP
    Default location on the SEPM: C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Php
    3.       Right-click the Php.ini file, and then click Properties.
    4.       On the General tab, uncheck Read-only, and then click OK.
    5.        Open the Php.ini file in a plain-text editor, such as Notepad.
    6.       Find the memory_limit entry and increase the value to 512M.
    7.        Find the max_execution_time entry and increase the value (in seconds).
    For example, to increase the timeout to ten minutes, change the line to the following:
    max_execution_time=600 (or higher, the sample php.ini below is set to 3000)
    8.       Save and close the Php.ini file.
    9.       Right-click the Php.ini file, and then click Properties.
    10.     On the General tab, check Read-only, and then click OK.

    An example:
    [PHP]
    cgi.force_redirect=0
    error_reporting=E_ALL & ~E_NOTICE
    extension=php_gd2.dll
    extension=php_mbstring.dll
    extension=php_mcrypt.dll
    extension_dir=.\ext
    max_execution_time=3000
    upload_max_filesize = 200M
    display_errors = Off
    display_startup_errors = Off
    log_errors = On
    report_memleaks = On
    track_errors = Off
    error_log = syslog
    expose_php=0
    allow_url_fopen=0
    session.gc_maxlifetime=2592000

    fastcgi.impersonate=1
    fastcgi.log=0
    memory_limit = 512M

    ;MBSTRING stuff
    mbstring.language = Neutral; Set default language to Neutral(UTF-8) (default)
    mbstring.internal_encoding = UTF-8 ; Set internal encoding to UTF-8
    mbstring.encoding_translation = On
    mbstring.http_input = UTF-8 ;
    mbstring.http_output = UTF-8 ; Set HTTP output encoding to UTF-8
    mbstring.detect_order = auto ; Set detect order to auto
    mbstring.substitute_character = none ; Do not print character
    output_buffering = On
    zlib.output_compression=On
    zlib.output_compression_level=6
    zlib.output_handler=mb_output_handler
    mbstring.func_overload = 7

    extension=php_openssl.dll
    extension=php_curl.dll
    session.save_path=C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection Manager\Php\temp\

    Note: Be sure to reset IIS (iisreset) or restart the World Wide Web Publishing service after making the above changes!
     
     


  • 7.  RE: Hi all

    Posted Dec 02, 2009 01:32 AM

    I was able to see the reports now by following the first step procedure only without following the advanced level procedure. Hope this will continue working. Thanks