locked
windows 2003. Проблема с WMI RRS feed

  • Вопрос

  • Windows 2003 SP2, Контроллер домена

    WMIDiag говорит следующее:

    .1425 23:35:03 (0) ** WMIDiag v2.0 started on 4 августа 2010 г. at 22:34.
    .1426 23:35:03 (0) ** 
    .1427 23:35:03 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
    .1428 23:35:03 (0) ** 
    .1429 23:35:03 (0) ** This script is not supported under any Microsoft standard support program or service.
    .1430 23:35:03 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
    .1431 23:35:03 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
    .1432 23:35:03 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
    .1433 23:35:03 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
    .1434 23:35:03 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
    .1435 23:35:03 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
    .1436 23:35:03 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
    .1437 23:35:03 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
    .1438 23:35:03 (0) ** of the possibility of such damages.
    .1439 23:35:03 (0) ** 
    .1440 23:35:03 (0) ** 
    .1441 23:35:03 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1442 23:35:03 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
    .1443 23:35:03 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1444 23:35:03 (0) ** 
    .1445 23:35:03 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1446 23:35:03 (0) ** Windows Server 2003 - No service pack - 32-bit (3790) - User 'EKTB-2GIS\ADMEKTB' on computer 'AD-EKTB'.
    .1447 23:35:03 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1448 23:35:03 (0) ** Environment: ........................................................................................................ OK..
    .1449 23:35:03 (0) ** There are no missing WMI system files: .............................................................................. OK.
    .1450 23:35:03 (0) ** There are no missing WMI repository files: .......................................................................... OK.
    .1451 23:35:03 (0) ** WMI repository state: ............................................................................................... N/A.
    .1452 23:35:03 (0) ** BEFORE running WMIDiag:
    .1453 23:35:03 (0) ** The WMI repository has a size of: ................................................................................... 0 MB.
    .1454 23:35:03 (0) ** - Disk free space on 'C:': .......................................................................................... 1705 MB.
    .1455 23:35:03 (0) **  - INDEX.BTR,           57344 bytes,    04.08.2010 21:17:22
    .1456 23:35:03 (0) **  - MAPPING.VER,          4 bytes,      04.08.2010 22:25:48
    .1457 23:35:03 (0) **  - MAPPING1.MAP,         120 bytes,     04.08.2010 22:25:48
    .1458 23:35:03 (0) **  - MAPPING2.MAP,         120 bytes,     04.08.2010 22:08:34
    .1459 23:35:03 (0) **  - OBJECTS.DATA,         90112 bytes,    04.08.2010 21:17:22
    .1460 23:35:03 (0) ** AFTER running WMIDiag:
    .1461 23:35:03 (0) ** The WMI repository has a size of: ................................................................................... 0 MB.
    .1462 23:35:03 (0) ** - Disk free space on 'C:': .......................................................................................... 1703 MB.
    .1463 23:35:03 (0) **  - INDEX.BTR,           57344 bytes,    04.08.2010 21:17:22
    .1464 23:35:03 (0) **  - MAPPING.VER,          4 bytes,      04.08.2010 23:22:36
    .1465 23:35:03 (0) **  - MAPPING1.MAP,         120 bytes,     04.08.2010 23:22:36
    .1466 23:35:03 (0) **  - MAPPING2.MAP,         120 bytes,     04.08.2010 22:54:27
    .1467 23:35:03 (0) **  - OBJECTS.DATA,         90112 bytes,    04.08.2010 21:17:22
    .1468 23:35:03 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1469 23:35:03 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
    .1470 23:35:03 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1471 23:35:03 (0) ** DCOM Status: ........................................................................................................ OK.
    .1472 23:35:03 (0) ** WMI registry setup: ................................................................................................. OK.
    .1473 23:35:03 (0) ** WMI Service has no dependents: ...................................................................................... OK.
    .1474 23:35:03 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
    .1475 23:35:03 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
    .1476 23:35:03 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1477 23:35:03 (0) ** WMI service DCOM setup: ............................................................................................. OK.
    .1478 23:35:03 (0) ** WMI components DCOM registrations: .................................................................................. OK.
    .1479 23:35:03 (0) ** WMI ProgID registrations: ........................................................................................... OK.
    .1480 23:35:03 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
    .1481 23:35:03 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
    .1482 23:35:03 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
    .1483 23:35:03 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
    .1484 23:35:03 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1485 23:35:03 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
    .1486 23:35:03 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
    .1487 23:35:03 (0) **    - REMOVED ACE:
    .1488 23:35:03 (0) **     ACEType: &h0
    .1489 23:35:03 (0) **          ACCESS_ALLOWED_ACE_TYPE
    .1490 23:35:03 (0) **     ACEFlags: &h0
    .1491 23:35:03 (0) **     ACEMask: &h1
    .1492 23:35:03 (0) **          DCOM_RIGHT_EXECUTE
    .1493 23:35:03 (0) ** 
    .1494 23:35:03 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    .1495 23:35:03 (0) **  Removing default security will cause some operations to fail!
    .1496 23:35:03 (0) **  It is possible to fix this issue by editing the security descriptor and adding the ACE.
    .1497 23:35:03 (0) **  For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    .1498 23:35:03 (0) ** 
    .1499 23:35:03 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
    .1500 23:35:03 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
    .1501 23:35:03 (0) **    - REMOVED ACE:
    .1502 23:35:03 (0) **     ACEType: &h0
    .1503 23:35:03 (0) **          ACCESS_ALLOWED_ACE_TYPE
    .1504 23:35:03 (0) **     ACEFlags: &h0
    .1505 23:35:03 (0) **     ACEMask: &h1
    .1506 23:35:03 (0) **          DCOM_RIGHT_EXECUTE
    .1507 23:35:03 (0) ** 
    .1508 23:35:03 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    .1509 23:35:03 (0) **  Removing default security will cause some operations to fail!
    .1510 23:35:03 (0) **  It is possible to fix this issue by editing the security descriptor and adding the ACE.
    .1511 23:35:03 (0) **  For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    .1512 23:35:03 (0) ** 
    .1513 23:35:03 (0) ** DCOM security for 'Windows Management Instrumentation' (Launch & Activation Permissions): ........................... MODIFIED.
    .1514 23:35:03 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
    .1515 23:35:03 (0) **    - REMOVED ACE:
    .1516 23:35:03 (0) **     ACEType: &h0
    .1517 23:35:03 (0) **          ACCESS_ALLOWED_ACE_TYPE
    .1518 23:35:03 (0) **     ACEFlags: &h0
    .1519 23:35:03 (0) **     ACEMask: &h1
    .1520 23:35:03 (0) **          DCOM_RIGHT_EXECUTE
    .1521 23:35:03 (0) ** 
    .1522 23:35:03 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    .1523 23:35:03 (0) **  Removing default security will cause some operations to fail!
    .1524 23:35:03 (0) **  It is possible to fix this issue by editing the security descriptor and adding the ACE.
    .1525 23:35:03 (0) **  For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    .1526 23:35:03 (0) ** 
    .1527 23:35:03 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
    .1528 23:35:03 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
    .1529 23:35:03 (0) **    - REMOVED ACE:
    .1530 23:35:03 (0) **     ACEType: &h0
    .1531 23:35:03 (0) **          ACCESS_ALLOWED_ACE_TYPE
    .1532 23:35:03 (0) **     ACEFlags: &h0
    .1533 23:35:03 (0) **     ACEMask: &h1
    .1534 23:35:03 (0) **          DCOM_RIGHT_EXECUTE
    .1535 23:35:03 (0) ** 
    .1536 23:35:03 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    .1537 23:35:03 (0) **  Removing default security will cause some operations to fail!
    .1538 23:35:03 (0) **  It is possible to fix this issue by editing the security descriptor and adding the ACE.
    .1539 23:35:03 (0) **  For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    .1540 23:35:03 (0) ** 
    .1541 23:35:03 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
    .1542 23:35:03 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
    .1543 23:35:03 (0) **    - REMOVED ACE:
    .1544 23:35:03 (0) **     ACEType: &h0
    .1545 23:35:03 (0) **          ACCESS_ALLOWED_ACE_TYPE
    .1546 23:35:03 (0) **     ACEFlags: &h0
    .1547 23:35:03 (0) **     ACEMask: &h1
    .1548 23:35:03 (0) **          DCOM_RIGHT_EXECUTE
    .1549 23:35:03 (0) ** 
    .1550 23:35:03 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    .1551 23:35:03 (0) **  Removing default security will cause some operations to fail!
    .1552 23:35:03 (0) **  It is possible to fix this issue by editing the security descriptor and adding the ACE.
    .1553 23:35:03 (0) **  For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    .1554 23:35:03 (0) ** 
    .1555 23:35:03 (0) ** 
    .1556 23:35:03 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
    .1557 23:35:03 (0) ** DCOM security error(s) detected: .................................................................................... 5.
    .1558 23:35:03 (0) ** WMI security warning(s) detected: ................................................................................... 0.
    .1559 23:35:03 (0) ** WMI security error(s) detected: ..................................................................................... 0.
    .1560 23:35:03 (0) ** 
    .1561 23:35:03 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
    .1562 23:35:03 (0) ** Overall WMI security status: ........................................................................................ OK.
    .1563 23:35:03 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
    .1564 23:35:03 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
    .1565 23:35:03 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
    .1566 23:35:03 (1) !! ERROR: WMI ADAP status: ............................................................................................. NOT AVAILABLE.
    .1567 23:35:03 (0) **  You can start the WMI AutoDiscovery/AutoPurge (ADAP) process to resynchronize
    .1568 23:35:03 (0) **  the performance counters with the WMI performance classes with the following commands:
    .1569 23:35:03 (0) **  i.e. 'WINMGMT.EXE /CLEARADAP'
    .1570 23:35:03 (0) **  i.e. 'WINMGMT.EXE /RESYNCPERF'
    .1571 23:35:03 (0) **  The ADAP process logs informative events in the Windows NT event log.
    .1572 23:35:03 (0) **  More information can be found on MSDN at:
    .1573 23:35:03 (0) **  http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/wmi_adap_event_log_events.asp
    .1574 23:35:03 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
    .1575 23:35:03 (0) ** - Root, 0x1AD - Невозможно создание объекта контейнером ActiveX.
    .1576 23:35:03 (0) ** 
    .1577 23:35:03 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 5 ERROR(S)!
    .1578 23:35:03 (0) ** - Root, 0x80080005 - Ошибка при выполнении приложения-сервера.
    .1579 23:35:03 (0) ** - Root, 0x80080005 - Ошибка при выполнении приложения-сервера.
    .1580 23:35:03 (0) ** - Root/Default, 0x80080005 - Ошибка при выполнении приложения-сервера.
    .1581 23:35:03 (0) ** - Root/CIMv2, 0x80080005 - Ошибка при выполнении приложения-сервера.
    .1582 23:35:03 (0) ** - Root/WMI, 0x80080005 - Ошибка при выполнении приложения-сервера.
    .1583 23:35:03 (0) ** 
    .1584 23:35:03 (0) ** WMI GET operations: ................................................................................................. OK.
    .1585 23:35:03 (0) ** WMI MOF representations: ............................................................................................ OK.
    .1586 23:35:03 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
    .1587 23:35:03 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
    .1588 23:35:03 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
    .1589 23:35:03 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
    .1590 23:35:03 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    .1591 23:35:03 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    .1592 23:35:03 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    .1593 23:35:03 (0) ** WMI static instances retrieved: ..................................................................................... 0.
    .1594 23:35:03 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    .1595 23:35:03 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
    .1596 23:35:03 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1597 23:35:03 (0) ** 
    .1598 23:35:03 (0) ** 1 error(s) 0x1AD - (WBEM_UNKNOWN) This error code is external to WMI.
    .1599 23:35:03 (0) ** 
    .1600 23:35:03 (0) ** 5 error(s) 0x80080005 - (WBEM_UNKNOWN) This error code is external to WMI.
    .1601 23:35:03 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1602 23:35:03 (0) ** WMI Registry key setup: ............................................................................................. OK.
    .1603 23:35:03 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1604 23:35:03 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1605 23:35:03 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1606 23:35:03 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1607 23:35:03 (0) ** 
    .1608 23:35:03 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1609 23:35:03 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
    .1610 23:35:03 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1611 23:35:03 (0) ** 
    .1612 23:35:03 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\ADMEKTB.EKTB-2GIS\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_2003_.SRV.RTM.32_AD-EKTB_2010.08.04_22.34.00.LOG' for details.
    .1613 23:35:03 (0) ** 
    .1614 23:35:03 (0) ** WMIDiag v2.0 ended on 4 августа 2010 г. at 23:35 (W:101 E:19 S:1).
    
    В журнале событий:

    Тип события: Ошибка
    Источник события: Userenv
    Категория события: Отсутствует
    Код события: 1090
    Дата: 10.08.2010
    Время: 14:44:19
    Пользователь: NT AUTHORITY\SYSTEM
    Компьютер: W2003
    Описание:
    Windows не удалось записать в журнал состояние сеанса RSoP. Попытка подключения к WMI не удалась. Дальнейшее протоколирование RSoP не будет выполняться для этого применения политики.

    10 августа 2010 г. 9:00

Ответы

  • Вот еще скриптик:

    ::to fix "not found" wmi error
    ::to fix .net calls to wmi repository
    ::to fix "initialization failure" error

    net stop winmgmt
    c:
    cd c:\windows\system32\wbem
    rd /S /Q repository
    regsvr32 /s %systemroot%\system32\scecli.dll
    regsvr32 /s %systemroot%\system32\userenv.dll
    mofcomp cimwin32.mof
    mofcomp cimwin32.mfl
    mofcomp rsop.mof
    mofcomp rsop.mfl
    for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
    for /f %%s in ('dir /b *.mof') do mofcomp %%s
    for /f %%s in ('dir /b *.mfl') do mofcomp %%s
    mofcomp exwmi.mof
    mofcomp -n:root\cimv2\applications\exchange wbemcons.mof
    mofcomp -n:root\cimv2\applications\exchange smtpcons.mof
    mofcomp exmgmt.mof

     

    Если есть Citrix тогда еще это:

    C:
    CD "C:\Program Files\Citrix\System32\Citrix\WMI"
    for %i in (*.mof, *.mfl) do Mofcomp %i

    А все могло быть и лучше...
    • Предложено в качестве ответа Vinokurov Yuriy 23 августа 2010 г. 6:31
    • Помечено в качестве ответа Vinokurov Yuriy 25 августа 2010 г. 6:19
    12 августа 2010 г. 7:15

Все ответы

  • http://www.eventid.net/display.asp?eventid=1090&eventno=1881&source=Userenv&phase=1>

    http://forum.oszone.net/thread-107067.html

    Тут описано возможное решение этой проблемы.


    In pivo veritas... t.G. - испокон и вовеки. Want to believe... It's a magic...
    10 августа 2010 г. 12:08
  • Спасибо за ответ.

    Первым делом был на eventid и пробовал предложенные варианты по лечению\очистке wmi. "Всеобъемлющий метод восстановления": 

    rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf

    тоже не помогает. Кто-нибудь сталкивался с подобной ситуацией и получилось ли её победить?

    12 августа 2010 г. 3:04
  • В логах кроме 1090 что есть (красное)?


    А все могло быть и лучше...
    12 августа 2010 г. 7:11
  • Вот еще скриптик:

    ::to fix "not found" wmi error
    ::to fix .net calls to wmi repository
    ::to fix "initialization failure" error

    net stop winmgmt
    c:
    cd c:\windows\system32\wbem
    rd /S /Q repository
    regsvr32 /s %systemroot%\system32\scecli.dll
    regsvr32 /s %systemroot%\system32\userenv.dll
    mofcomp cimwin32.mof
    mofcomp cimwin32.mfl
    mofcomp rsop.mof
    mofcomp rsop.mfl
    for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
    for /f %%s in ('dir /b *.mof') do mofcomp %%s
    for /f %%s in ('dir /b *.mfl') do mofcomp %%s
    mofcomp exwmi.mof
    mofcomp -n:root\cimv2\applications\exchange wbemcons.mof
    mofcomp -n:root\cimv2\applications\exchange smtpcons.mof
    mofcomp exmgmt.mof

     

    Если есть Citrix тогда еще это:

    C:
    CD "C:\Program Files\Citrix\System32\Citrix\WMI"
    for %i in (*.mof, *.mfl) do Mofcomp %i

    А все могло быть и лучше...
    • Предложено в качестве ответа Vinokurov Yuriy 23 августа 2010 г. 6:31
    • Помечено в качестве ответа Vinokurov Yuriy 25 августа 2010 г. 6:19
    12 августа 2010 г. 7:15
  • Уважаемый пользователь!

    В вашей теме отсутствует активность в течение последних 5 дней. При отсутствии каких-либо действий в течение 2 последующих дней, тема будет переведена в разряд обсуждений. Вы можете возобновить дискуссию, просто оставив сообщение в данной теме.


    Мнения, высказанные здесь, являются отражением моих личных взглядов, а не позиции корпорации Microsoft. Вся информация предоставляется "как есть" без каких-либо гарантий
    Follow MSTechnetForum on Twitter

    Посетите Блог Инженеров Доклады на Techdays: http://www.techdays.ru/speaker/Vinokurov_YUrij.html
    23 августа 2010 г. 6:32