IIS-W3SVC-WP EventID 2308 loghttpRSS

2 replies

Last post Feb 11, 2020 07:44 AM by Jalpa Panchal

  • IIS-W3SVC-WP EventID 2308 loghttp

    Feb 10, 2020 10:11 AM|u-jinn|LINK

    Модулю loghttp в рабочем процессе с ИД "6684" не удалось получить данные настраиваемого журнала для запросов: "6". Поле данных содержит код ошибки.

    особенность в том, что процесса PID 6684 нет.

  • Re: IIS-W3SVC-WP EventID 2308 loghttp

    Feb 10, 2020 02:19 PM|Lewis-H|LINK

    This event is logged when FailedRequestTracing module failed to write buffered events to log file for the request that matched failure definition.
    Resolution :
    Enable tracing access to the log file directory
    In order for a worker process to write a failed request trace to a log file, the log file directory must exist, the IIS_IUSRS group must have the Write permission on the directory, and the disk must not be full. If the IIS_IUSRS group does not have write access to this directory, the logs will not be generated. If you specify a directory other than the default, make sure that the IIS_IUSRS group has the permission to write to it.
    To enable tracing access to the log file directory, perform the following procedures:
    1.Find the current Failed Request Tracing log file path setting.
    2.Make sure the configured Failed Request Tracing log file directory exists.
    3.Make sure the IIS_IUSRS group or appropriate identity has permission to write to the directory.
    4.Make sure there is sufficient disk space.
    To perform these procedures, you must have membership in Administrators , or you must have been delegated the appropriate authority.
    Find the current Failed Request Tracing log file path setting
    1.Click Start , click Control Panel , and then click Administrative Tools .
    2.Right-click Internet Information Services (IIS) Manager and select Run as administrator .
    3.In the IIS Manager Connections pane, expand the Web server name, then Sites .
    4.Select the Web site whose log file path you want to check.
    5.In the Actions pane , click Configure Failed Request Tracing . The Edit Web Site Failed Request Tracing Settings dialog box appears.
    6.If the Enable check box is cleared, select it. This will enable the Directory window in the dialog box.
    7.In the Directory window, note the log file directory path.
    Make sure the configured Failed Request Tracing log file directory exists
    1.Open an elevated Command Prompt window. Click Star t, point to All Programs , click Accessories , right-click Command Prompt , and then click Run as administrator .
    2.Type start explorer .
    3.Using Windows Explorer, navigate to the log directory location you noted earlier. If the directory does not exist, create it.
    Make sure the IIS_IUSRS group has permission to write to the log file directory
    1.Right-click the log file directory folder and select Properties .
    2.Click the Security tab.
    3.In the Group or user names window, look for the IIS_IUSRS group. If it appears, select it. In the Permissions for IIS_IUSRS window, Allow should be selected for the Write permission.
    If the Write permission is not selected:
    1.Click the Edit… button.
    2.Select the IIS_IUSRS group again.
    3.Select the Write check box under Allow , then click OK .
    4.In the initial Permissions for IIS_IUSRS window, a check mark for the Write permission should now appear under the Allow column.
    If the IIS_IUSRS group does not appear in the in the Group or user names window:
    1.Click Edit… , then Add . The Select Users, Computers, or Groups dialog box appears.
    2.In the Enter the object names to select window, type servername \IIS_IUSRS , where servername is the name of the Web server, then click OK .
    3.In the Permissions for IIS_IUSRS window, clear all check boxes and select the Allow check box for the Write permission, then click OK .
    4.In the initial Permissions for IIS_IUSRS window, a check mark for the Write permission now appears under the Allow column.

  • Re: IIS-W3SVC-WP EventID 2308 loghttp

    Feb 11, 2020 07:44 AM|Jalpa Panchal|LINK

    Hi,

    Please post your question in English. also, describe what is the exact problem and what you are trying to achieve. so that community members can provide your more accurate solution.

    Thank you for understanding.

    Regards,

    Jalpa

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.