Cluster smon_scn_to_time is corrupted

Hi,
our database is automatically shutdown.i saw in alert log file it say that
ora-00604:error occured at recursive sql level 1
ora-1578 : oracle data bock corrupted (file#1,block 3726)
ora-01110 : data file 1:'c:\pracle\oradata\bmms\system01.dbf'
we dont have rman backup so that i can recover the specific block.we have logical backup
i fire a select statement it show that
sql>select tablespace_name,segment_type,owner,segment_name from dba_extents
where file_id=1
and 3726 between block_id AND BLOCK_ID + blocks -1;
output is
tablespace_Name=system
segment _type=cluster
owner=sys
segment_name=smon_scn_to_time
i search on the google we can repair the block usin dbms_repair package but i dont get idea how to do it please any one suggest me how to recover the block or any solution .it cause the database down automatically thrice in day.quick response will be highyl appreciated.thanks a lot inadvance

You don't have a logical backup ... you have nothing. If it isn't RMAN it isn't a backup. The word that may well apply is toast: Hopefully not burnt toast.
Open an SR at metalink and if you are a religious person apply prayer liberally.
If you really want to try DBMS_REPAIR I have full demos of its functionality in Morgan's Library at:
www.morganslibrary.org/library.html
And, if you succeed, immediately take an RMAN backup and then do so religiously every 24 hours thereafter.
Warning to everyone that has bought into the total nonsense that EXP and DataPump Exports are backups: They are not.

Similar Messages

  • Mapping to VMware Clusters

    Is it possible to map volumes to more than one cluster without possibly corrupting data? We currently have 5 volumes that are mapped to our cluster of 5 ESXi hosts.  We are adding 2 more hosts, so added another cluster for those hosts.  I was wondering if I could map those 5 volumes to both clusters, or do I need to create all new volumes for the new cluster?
    Thanks for your help!

    Hello, jyoung709.
    So, basically mapping a volume to 2 different clusters would the same as mapping to 2 hosts not in a cluster. It would result in corruption. The beauty in clustering is that there is a 'moderator' (if you will) that manages when a read or write hits a disk. The hosts in the cluster are managed by the software that allows them to 'take turns' so to say, so there is not simultaneous writing. (this is a crude explanation, but serves the purpose)
    In your scenario, each cluster is unaware of the other, and is not managed by said moderator. If there were a 'cluster management system' for the clusters? ...sure. but, I have my doubts that it's out there.
    I hope this helps.
    Let me know if you have any questions.

  • ACFS on RAC:

    Hello ,
    in our RAC environment we are using ACFS to store the backups of the database. For monitoring and administrating our databases we are uisng Cloud Contorl 12c.
    This morning the CloudControl reported thew following error:
    ASM Cluster File System Corrupt (Volume Device /dev/asm/v03_backup-33)
    My understanding is that the ASM Cluster File System using volume device /dev/asm/v03_backup-33 has sections that are corrupt.
    Running the command chkdg DG03_BACKUP under ASMCMD did not report any error at all. Isn't it so that ASM runs automatically checks if the file system is corrupt? Anyway, the error message persists even if reevaluating the alert in CloudControl.
    The error occurred in a productional environment - therefore I have to be a bit careful when doing checks etc.
    My question now is: are we really having a problem with a corrupt ACFS - and how could this be checked?
    Any help will be appreciated
    Rgds
    JH

    Hi Sebastian,
    thanks for your fast reply...
    I've tried to excute the following commands:
    [root]# fsck.acfs -v /dev/asm/v03_backup-33
    version = 11.2.0.3.0
    fsck.acfs: temporary directory '/usr/tmp'
    fsck.acfs: current directory '/root'
    fsck.acfs: ACFS-00511: /dev/asm/v03_backup-33 is mounted on at least one node of the cluster.
    fsck.acfs: ACFS-07656: unable to continue
    Seems to me that fsck could only get executed when the volume is not mounted...
    Rgds
    JH

  • Orainventory corrupted in a cluster

    Hi,
    There is a 4 node cluster and I was assigned to apply a DST patch on one node (ex: server-C). And server-A and server-B have databases running on them but not on sever-C and server-D.
    When I checked server-C, I did not see any database on it. Then I tried to apply the DST patch on it and it failed (since the other nodes are having running databases)
    After the failure of the patch, I noticed that the Orainventory is corrupted.
    So somebody please help me how to fix this problem.
    Thank you very much

    Which server - BI Server or Presentation Services server?
    In an OBIEE Cluster it's only your BI Server and Scheduler that are Clustered.
    You can configured your Presentation Services to be load balanced, and the two answers given already will both help you for that.

  • SUN Cluster 3.2, Solaris 10, Corrupted IPMP group on one node.

    Hello folks,
    I recently made a network change on nodename2 to add some resilience to IPMP (adding a second interface but still using a single IP address).
    After a reboot, I cannot keep this host from rebooting. For the one minute that it stays up, I do get the following result from scstat that seems to suggest a problem with the IPMP configuration. I rolled back my IPMP change, but it still doesn't seem to register the IPMP group in scstat.
    nodename2|/#scstat
    -- Cluster Nodes --
    Node name Status
    Cluster node: nodename1 Online
    Cluster node: nodename2 Online
    -- Cluster Transport Paths --
    Endpoint Endpoint Status
    Transport path: nodename1:bge3 nodename2:bge3 Path online
    -- Quorum Summary from latest node reconfiguration --
    Quorum votes possible: 3
    Quorum votes needed: 2
    Quorum votes present: 3
    -- Quorum Votes by Node (current status) --
    Node Name Present Possible Status
    Node votes: nodename1 1 1 Online
    Node votes: nodename2 1 1 Online
    -- Quorum Votes by Device (current status) --
    Device Name Present Possible Status
    Device votes: /dev/did/rdsk/d3s2 0 1 Offline
    -- Device Group Servers --
    Device Group Primary Secondary
    Device group servers: jms-ds nodename1 nodename2
    -- Device Group Status --
    Device Group Status
    Device group status: jms-ds Online
    -- Multi-owner Device Groups --
    Device Group Online Status
    -- IPMP Groups --
    Node Name Group Status Adapter Status
    scstat:  unexpected error.
    I did manage to run scstat on nodename1 while nodename2 was still up between reboots, here is that result (it does not show any IPMP group(s) on nodename2)
    nodename1|/#scstat
    -- Cluster Nodes --
    Node name Status
    Cluster node: nodename1 Online
    Cluster node: nodename2 Online
    -- Cluster Transport Paths --
    Endpoint Endpoint Status
    Transport path: nodename1:bge3 nodename2:bge3 faulted
    -- Quorum Summary from latest node reconfiguration --
    Quorum votes possible: 3
    Quorum votes needed: 2
    Quorum votes present: 3
    -- Quorum Votes by Node (current status) --
    Node Name Present Possible Status
    Node votes: nodename1 1 1 Online
    Node votes: nodename2 1 1 Online
    -- Quorum Votes by Device (current status) --
    Device Name Present Possible Status
    Device votes: /dev/did/rdsk/d3s2 1 1 Online
    -- Device Group Servers --
    Device Group Primary Secondary
    Device group servers: jms-ds nodename1 -
    -- Device Group Status --
    Device Group Status
    Device group status: jms-ds Degraded
    -- Multi-owner Device Groups --
    Device Group Online Status
    -- IPMP Groups --
    Node Name Group Status Adapter Status
    IPMP Group: nodename1 sc_ipmp1 Online bge2 Online
    IPMP Group: nodename1 sc_ipmp0 Online bge0 Online
    -- IPMP Groups in Zones --
    Zone Name Group Status Adapter Status
    I believe that I should be able to delete the IPMP group for the second node from the cluster and re-add it, but I'm sure about how to go about doing this. I welcome your comments or thoughts on what I can try before rebuilding this node from scratch.
    -AG

    I was able to restart both sides of the cluster. Now both sides are online, but neither side can access the shared disk.
    Lots of warnings. I will keep poking....
    Rebooting with command: boot
    Boot device: /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/disk@0,0:a File and args:
    SunOS Release 5.10 Version Generic_141444-09 64-bit
    Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    Hardware watchdog enabled
    Hostname: nodename2
    Jul 21 10:00:16 in.mpathd[221]: No test address configured on interface ce3; disabling probe-based failure detection on it
    Jul 21 10:00:16 in.mpathd[221]: No test address configured on interface bge0; disabling probe-based failure detection on it
    /usr/cluster/bin/scdidadm: Could not stat "../../devices/iscsi/[email protected],0:c,raw" - No such file or directory.
    Warning: Path node loaded - "../../devices/iscsi/[email protected],0:c,raw".
    /usr/cluster/bin/scdidadm: Could not stat "../../devices/iscsi/[email protected],1:c,raw" - No such file or directory.
    Warning: Path node loaded - "../../devices/iscsi/[email protected],1:c,raw".
    Booting as part of a cluster
    NOTICE: CMM: Node nodename1 (nodeid = 1) with votecount = 1 added.
    NOTICE: CMM: Node nodename2 (nodeid = 2) with votecount = 1 added.
    WARNING: CMM: Open failed for quorum device /dev/did/rdsk/d3s2 with error 2.
    NOTICE: clcomm: Adapter bge3 constructed
    NOTICE: CMM: Node nodename2: attempting to join cluster.
    NOTICE: CMM: Node nodename1 (nodeid: 1, incarnation #: 1279727883) has become reachable.
    NOTICE: clcomm: Path nodename2:bge3 - nodename1:bge3 online
    WARNING: CMM: Open failed for quorum device /dev/did/rdsk/d3s2 with error 2.
    NOTICE: CMM: Cluster has reached quorum.
    NOTICE: CMM: Node nodename1 (nodeid = 1) is up; new incarnation number = 1279727883.
    NOTICE: CMM: Node nodename2 (nodeid = 2) is up; new incarnation number = 1279728026.
    NOTICE: CMM: Cluster members: nodename1 nodename2.
    NOTICE: CMM: node reconfiguration #3 completed.
    NOTICE: CMM: Node nodename2: joined cluster.
    NOTICE: CCR: Waiting for repository synchronization to finish.
    WARNING: CCR: Invalid CCR table : dcs_service_9 cluster global.
    WARNING: CMM: Open failed for quorum device /dev/did/rdsk/d3s2 with error 2.
    ip: joining multicasts failed (18) on clprivnet0 - will use link layer broadcasts for multicast
    ==> WARNING: DCS: Error looking up services table
    ==> WARNING: DCS: Error initializing service 9 from file
    /usr/cluster/bin/scdidadm: Could not stat "../../devices/iscsi/[email protected],0:c,raw" - No such file or directory.
    Warning: Path node loaded - "../../devices/iscsi/[email protected],0:c,raw".
    /usr/cluster/bin/scdidadm: Could not stat "../../devices/iscsi/[email protected],1:c,raw" - No such file or directory.
    Warning: Path node loaded - "../../devices/iscsi/[email protected],1:c,raw".
    /dev/md/rdsk/d22 is clean
    Reading ZFS config: done.
    NOTICE: iscsi session(6) iqn.1994-12.com.promise.iscsiarray2 online
    nodename2 console login: obtaining access to all attached disks
    starting NetWorker daemons:
    Rebooting with command: boot
    Boot device: /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/disk@0,0:a File and args:
    SunOS Release 5.10 Version Generic_141444-09 64-bit
    Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    Hardware watchdog enabled
    Hostname: nodename1
    /usr/cluster/bin/scdidadm: Could not stat "../../devices/iscsi/[email protected],0:c,raw" - No such file or directory.
    Warning: Path node loaded - "../../devices/iscsi/[email protected],0:c,raw".
    /usr/cluster/bin/scdidadm: Could not stat "../../devices/iscsi/[email protected],1:c,raw" - No such file or directory.
    Warning: Path node loaded - "../../devices/iscsi/[email protected],1:c,raw".
    Booting as part of a cluster
    NOTICE: CMM: Node nodename1 (nodeid = 1) with votecount = 1 added.
    NOTICE: CMM: Node nodename2 (nodeid = 2) with votecount = 1 added.
    WARNING: CMM: Open failed for quorum device /dev/did/rdsk/d3s2 with error 2.
    NOTICE: clcomm: Adapter bge3 constructed
    NOTICE: CMM: Node nodename1: attempting to join cluster.
    NOTICE: bge3: link up 1000Mbps Full-Duplex
    NOTICE: clcomm: Path nodename1:bge3 - nodename2:bge3 errors during initiation
    WARNING: Path nodename1:bge3 - nodename2:bge3 initiation encountered errors, errno = 62. Remote node may be down or unreachable through this path.
    WARNING: CMM: Open failed for quorum device /dev/did/rdsk/d3s2 with error 2.
    NOTICE: CMM: Cluster doesn't have operational quorum yet; waiting for quorum.
    NOTICE: bge3: link down
    NOTICE: bge3: link up 1000Mbps Full-Duplex
    NOTICE: CMM: Node nodename2 (nodeid: 2, incarnation #: 1279728026) has become reachable.
    NOTICE: clcomm: Path nodename1:bge3 - nodename2:bge3 online
    WARNING: CMM: Open failed for quorum device /dev/did/rdsk/d3s2 with error 2.
    NOTICE: CMM: Cluster has reached quorum.
    NOTICE: CMM: Node nodename1 (nodeid = 1) is up; new incarnation number = 1279727883.
    NOTICE: CMM: Node nodename2 (nodeid = 2) is up; new incarnation number = 1279728026.
    NOTICE: CMM: Cluster members: nodename1 nodename2.
    NOTICE: CMM: node reconfiguration #3 completed.
    NOTICE: CMM: Node nodename1: joined cluster.
    WARNING: CMM: Open failed for quorum device /dev/did/rdsk/d3s2 with error 2.
    ip: joining multicasts failed (18) on clprivnet0 - will use link layer broadcasts for multicast
    /usr/cluster/bin/scdidadm: Could not stat "../../devices/iscsi/[email protected],0:c,raw" - No such file or directory.
    Warning: Path node loaded - "../../devices/iscsi/[email protected],0:c,raw".
    /usr/cluster/bin/scdidadm: Could not stat "../../devices/iscsi/[email protected],1:c,raw" - No such file or directory.
    Warning: Path node loaded - "../../devices/iscsi/[email protected],1:c,raw".
    /dev/md/rdsk/d26 is clean
    Reading ZFS config: done.
    NOTICE: iscsi session(6) iqn.1994-12.com.promise.iscsiarray2 online
    nodename1 console login: obtaining access to all attached disks
    starting NetWorker daemons:
    nsrexecd
    mount: /dev/md/jms-ds/dsk/d100 is already mounted or /opt/esbshares is busy

  • Hyper-V Failover Cluster Node Corruption

    Dear All,
                Some of my nodes are showing abnormal behavior.  They are restarting every now and then.  I had updated the cluster nodes, but all updates were OS specific, there was nothing specific
    with respect to hardware update.
    I have analyzed crash dumps and find out that following is causing the crash:
    page_fault_in_nonpaged_area
    anyone has any idea about this?
    Thanks in advance.

    Hi ,
    What is the OS of the cluster node ?
    Did you try to remove the protection client for troubleshooing ?
    If it is a 2008R2 cluster , please refer to this thread :
    http://social.technet.microsoft.com/Forums/en-US/32ab6a85-6002-4c3c-97ea-27cb1091e9b3/windows-cluster-server-is-getting-restarted?forum=winservergen
    Hope it helps
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Block corruption error keep on repeating in alert log file

    Hi,
    Oracle version : 9.2.0.8.0
    os : sun soalris
    error in alert log file:
    Errors in file /u01/app/oracle/admin/qtrain/bdump/qtrain_smon_24925.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-01578: ORACLE data block corrupted (file # 1, block # 19750)
    ORA-01110: data file 1: '/u01/app/oracle/admin/qtrain/dbfiles/system.dbf'system datafile is restored from backup still the error is logged in alert log file
    Inputs are appreciated.
    Thanks
    Prakash

    Hi,
    Thanks for the inputs
    OWNER                          SEGMENT_NAME                                                                      PARTITION_NAME                 SEGMENT_TYPE       TABLESPACE_NAME                 EXTENT_ID    FILE_ID   BLOCK_ID      BYTES     BLOCKS RELATIVE_FNO
    SYS                            SMON_SCN_TO_TIME                                                                                                 CLUSTER            SYSTEM                                  1          1      19749      16384          1            1
    SYS                            SMON_SCN_TO_TIME                                                                                                 CLUSTER            SYSTEM                                  2          1      19750      32768          2            1Thanks
    Prakash

  • Cannot connect to Session broker server, but can to other servers in Cluster

    Hi Everyone,
    Hopefully this is the right place to post. Have searched quite a bit through the forums (not all 19000+ pages though), and can't seem to find a similiar issue.
    I have also searched the internet and tried all solutions others with a similiar problem have.
    This is my problem:
    We have two servers running Server 2008 R2, set up as Remote Desktop Servers in a cluster setup.
    The session broker is located on the second server (This is an active server which has sessions load balanced to it). There is also a DNS round robin setup
    Problem: When sessions are allowed to be load balanced on Server2, then the users cannot connect to the cluster. The round robin seems to still send some sessions to the first server, and these seem to connect fine.
    I suspected the issue was with the WMI Respository, and so started. I found a lot of errors, but have been unable to fix them.
    I downlaoded the WMIDiag from Microsoft, and here is the report:
    48866 15:56:44 (0) ** WMIDiag v2.1 started on 15 April 2015 at 15:48.
    48867 15:56:44 (0) **
    48868 15:56:44 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
    48869 15:56:44 (0) **
    48870 15:56:44 (0) ** This script is not supported under any Microsoft standard support program or service.
    48871 15:56:44 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
    48872 15:56:44 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
    48873 15:56:44 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
    48874 15:56:44 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
    48875 15:56:44 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
    48876 15:56:44 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
    48877 15:56:44 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
    48878 15:56:44 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
    48879 15:56:44 (0) ** of the possibility of such damages.
    48880 15:56:44 (0) **
    48881 15:56:44 (0) **
    48882 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    48883 15:56:44 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
    48884 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    48885 15:56:44 (0) **
    48886 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    48887 15:56:44 (0) ** Windows Server 2008 R2 - Service pack 1 - 64-bit (7601) - User 'MIBCO\CONN.LOMBARD' on computer 'SSCRDS02'.
    48888 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    48889 15:56:44 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
    48890 15:56:44 (0) ** INFO: => 3 possible incorrect shutdown(s) detected on:
    48891 15:56:44 (0) **          - Shutdown on 05 December 2014 22:55:28 (GMT-0).
    48892 15:56:44 (0) **          - Shutdown on 12 December 2014 06:43:00 (GMT-0).
    48893 15:56:44 (0) **          - Shutdown on 27 February 2015 05:19:26 (GMT-0).
    48894 15:56:44 (0) **
    48895 15:56:44 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #1).
    48896 15:56:44 (0) ** Drive type: ......................................................................................................... SCSI (DELL PERC H700 SCSI Disk Device).
    48897 15:56:44 (0) ** There are no missing WMI system files: .............................................................................. OK.
    48898 15:56:44 (0) ** There are no missing WMI repository files: .......................................................................... OK.
    48899 15:56:44 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
    48900 15:56:44 (0) ** AFTER running WMIDiag:
    48901 15:56:44 (0) ** The WMI repository has a size of: ................................................................................... 26 MB.
    48902 15:56:44 (0) ** - Disk free space on 'C:': .......................................................................................... 297281 MB.
    48903 15:56:44 (0) **   - INDEX.BTR,                     5513216 bytes,      2015/04/15 03:52:21 PM
    48904 15:56:44 (0) **   - MAPPING1.MAP,                  76804 bytes,        2015/04/15 03:50:51 PM
    48905 15:56:44 (0) **   - MAPPING2.MAP,                  76804 bytes,        2015/04/15 03:52:21 PM
    48906 15:56:44 (0) **   - OBJECTS.DATA,                  22036480 bytes,     2015/04/15 03:52:21 PM
    48907 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    48908 15:56:44 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
    48909 15:56:44 (0) ** Windows Firewall Profile: ........................................................................................... DOMAIN.
    48910 15:56:44 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
    48911 15:56:44 (0) ** => This will prevent any WMI remote connectivity to this computer except
    48912 15:56:44 (0) **    if the following three inbound rules are ENABLED and non-BLOCKING:
    48913 15:56:44 (0) **    - 'Windows Management Instrumentation (DCOM-In)'
    48914 15:56:44 (0) **    - 'Windows Management Instrumentation (WMI-In)'
    48915 15:56:44 (0) **    - 'Windows Management Instrumentation (ASync-In)'
    48916 15:56:44 (0) **    Verify the reported status for each of these three inbound rules below.
    48917 15:56:44 (0) **
    48918 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' GROUP rule: ............................................. ENABLED.
    48919 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-Out)' rule: ............................................... ENABLED.
    48920 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ................................................ ENABLED.
    48921 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ............................................... ENABLED.
    48922 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: .............................................. ENABLED.
    48923 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    48924 15:56:44 (0) ** DCOM Status: ........................................................................................................ OK.
    48925 15:56:44 (0) ** WMI registry setup: ................................................................................................. OK.
    48926 15:56:44 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
    48927 15:56:44 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
    48928 15:56:44 (0) ** - SMS Agent Host (CCMEXEC, StartMode='Automatic')
    48929 15:56:44 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
    48930 15:56:44 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
    48931 15:56:44 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
    48932 15:56:44 (0) **          this can prevent the service/application to work as expected.
    48933 15:56:44 (0) **
    48934 15:56:44 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
    48935 15:56:44 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
    48936 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    48937 15:56:44 (0) ** WMI service DCOM setup: ............................................................................................. OK.
    48938 15:56:44 (0) ** WMI components DCOM registrations: .................................................................................. OK.
    48939 15:56:44 (0) ** WMI ProgID registrations: ........................................................................................... OK.
    48940 15:56:44 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
    48941 15:56:44 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
    48942 15:56:44 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
    48943 15:56:44 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
    48944 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    48945 15:56:44 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
    48946 15:56:44 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
    48947 15:56:44 (0) **    i.e. You can start your scripts or WMIC commands from an elevated command
    48948 15:56:44 (0) **         prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
    48949 15:56:44 (0) **         selecting 'Run as Administrator'.
    48950 15:56:44 (0) **    i.e. You can also execute the WMI scripts or WMIC commands as a task
    48951 15:56:44 (0) **         in the Task Scheduler within the right security context.
    48952 15:56:44 (0) **
    48953 15:56:44 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
    48954 15:56:44 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
    48955 15:56:44 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
    48956 15:56:44 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
    48957 15:56:44 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
    48958 15:56:44 (0) **
    48959 15:56:44 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
    48960 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\SYSTEM' DOES NOT match corresponding expected trustee rights (Actual->Default)
    48961 15:56:44 (0) **        - ACTUAL ACE:
    48962 15:56:44 (0) **          ACEType:  &h0
    48963 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    48964 15:56:44 (0) **          ACEFlags: &h4
    48965 15:56:44 (0) **                    NO_PROPAGATE_INHERIT_ACE
    48966 15:56:44 (0) **          ACEMask:  &hB
    48967 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
    48968 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
    48969 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
    48970 15:56:44 (0) **        - EXPECTED ACE:
    48971 15:56:44 (0) **          ACEType:  &h0
    48972 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    48973 15:56:44 (0) **          ACEFlags: &h0
    48974 15:56:44 (0) **          ACEMask:  &h1F
    48975 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
    48976 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
    48977 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
    48978 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
    48979 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
    48980 15:56:44 (0) **
    48981 15:56:44 (0) ** => The actual ACE has the right(s) '&h14 DCOM_RIGHT_LAUNCH_REMOTE DCOM_RIGHT_ACTIVATE_REMOTE' removed!
    48982 15:56:44 (0) **    This will cause some operations to fail!
    48983 15:56:44 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
    48984 15:56:44 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    48985 15:56:44 (0) **
    48986 15:56:44 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
    48987 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\INTERACTIVE' DOES NOT match corresponding expected trustee rights (Actual->Default)
    48988 15:56:44 (0) **        - ACTUAL ACE:
    48989 15:56:44 (0) **          ACEType:  &h0
    48990 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    48991 15:56:44 (0) **          ACEFlags: &h4
    48992 15:56:44 (0) **                    NO_PROPAGATE_INHERIT_ACE
    48993 15:56:44 (0) **          ACEMask:  &hB
    48994 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
    48995 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
    48996 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
    48997 15:56:44 (0) **        - EXPECTED ACE:
    48998 15:56:44 (0) **          ACEType:  &h0
    48999 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    49000 15:56:44 (0) **          ACEFlags: &h0
    49001 15:56:44 (0) **          ACEMask:  &h1F
    49002 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
    49003 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
    49004 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
    49005 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
    49006 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
    49007 15:56:44 (0) **
    49008 15:56:44 (0) ** => The actual ACE has the right(s) '&h14 DCOM_RIGHT_LAUNCH_REMOTE DCOM_RIGHT_ACTIVATE_REMOTE' removed!
    49009 15:56:44 (0) **    This will cause some operations to fail!
    49010 15:56:44 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
    49011 15:56:44 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    49012 15:56:44 (0) **
    49013 15:56:44 (0) **
    49014 15:56:44 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
    49015 15:56:44 (0) ** DCOM security error(s) detected: .................................................................................... 2.
    49016 15:56:44 (0) ** WMI security warning(s) detected: ................................................................................... 0.
    49017 15:56:44 (0) ** WMI security error(s) detected: ..................................................................................... 0.
    49018 15:56:44 (0) **
    49019 15:56:44 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
    49020 15:56:44 (0) ** Overall WMI security status: ........................................................................................ OK.
    49021 15:56:44 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
    49022 15:56:44 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 5.
    49023 15:56:44 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
    49024 15:56:44 (0) **   'select * from MSFT_SCMEventLogEvent'
    49025 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
    49026 15:56:44 (0) **   'SELECT * FROM __NamespaceCreationEvent'
    49027 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
    49028 15:56:44 (0) **   'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy_EmbeddedObject"'
    49029 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
    49030 15:56:44 (0) **   'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy_Config"'
    49031 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
    49032 15:56:44 (0) **   'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy"'
    49033 15:56:44 (0) **
    49034 15:56:44 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
    49035 15:56:44 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 3 NAMESPACE(S)!
    49036 15:56:44 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
    49037 15:56:44 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
    49038 15:56:44 (0) ** - ROOT/SERVICEMODEL.
    49039 15:56:44 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
    49040 15:56:44 (0) **    use an encrypted connection by specifying the PACKET PRIVACY authentication level.
    49041 15:56:44 (0) **    (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
    49042 15:56:44 (0) **    i.e. 'WMIC.EXE /NODE:"SSCRDS02" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
    49043 15:56:44 (0) **
    49044 15:56:44 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
    49045 15:56:44 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
    49046 15:56:44 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 34 ERROR(S)!
    49047 15:56:44 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49048 15:56:44 (0) **   MOF Registration: ''
    49049 15:56:44 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49050 15:56:44 (0) **   MOF Registration: ''
    49051 15:56:44 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49052 15:56:44 (0) **   MOF Registration: ''
    49053 15:56:44 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49054 15:56:44 (0) **   MOF Registration: ''
    49055 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49056 15:56:44 (0) **   MOF Registration: ''
    49057 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49058 15:56:44 (0) **   MOF Registration: ''
    49059 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49060 15:56:44 (0) **   MOF Registration: ''
    49061 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49062 15:56:44 (0) **   MOF Registration: ''
    49063 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49064 15:56:44 (0) **   MOF Registration: ''
    49065 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49066 15:56:44 (0) **   MOF Registration: ''
    49067 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49068 15:56:44 (0) **   MOF Registration: ''
    49069 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49070 15:56:44 (0) **   MOF Registration: ''
    49071 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49072 15:56:44 (0) **   MOF Registration: ''
    49073 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49074 15:56:44 (0) **   MOF Registration: ''
    49075 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_NETDataProviderforOracle_NETDataProviderforOracle, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49076 15:56:44 (0) **   MOF Registration: ''
    49077 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_NETDataProviderforOracle_NETDataProviderforOracle, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49078 15:56:44 (0) **   MOF Registration: ''
    49079 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49080 15:56:44 (0) **   MOF Registration: ''
    49081 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49082 15:56:44 (0) **   MOF Registration: ''
    49083 15:56:44 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49084 15:56:44 (0) **   MOF Registration: ''
    49085 15:56:44 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49086 15:56:44 (0) **   MOF Registration: ''
    49087 15:56:44 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49088 15:56:44 (0) **   MOF Registration: ''
    49089 15:56:44 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49090 15:56:44 (0) **   MOF Registration: ''
    49091 15:56:44 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49092 15:56:44 (0) **   MOF Registration: ''
    49093 15:56:44 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49094 15:56:44 (0) **   MOF Registration: ''
    49095 15:56:44 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49096 15:56:44 (0) **   MOF Registration: ''
    49097 15:56:44 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49098 15:56:44 (0) **   MOF Registration: ''
    49099 15:56:44 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49100 15:56:44 (0) **   MOF Registration: ''
    49101 15:56:44 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49102 15:56:44 (0) **   MOF Registration: ''
    49103 15:56:44 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49104 15:56:44 (0) **   MOF Registration: ''
    49105 15:56:44 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49106 15:56:44 (0) **   MOF Registration: ''
    49107 15:56:44 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49108 15:56:44 (0) **   MOF Registration: ''
    49109 15:56:44 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49110 15:56:44 (0) **   MOF Registration: ''
    49111 15:56:44 (0) ** - root/ccm/LocationServices, ClientInfo, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49112 15:56:44 (0) **   MOF Registration: ''
    49113 15:56:44 (0) ** - root/ccm/LocationServices, ClientInfo, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49114 15:56:44 (0) **   MOF Registration: ''
    49115 15:56:44 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
    49116 15:56:44 (0) **    a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
    49117 15:56:44 (0) **    You can refresh the WMI class provider buffer with the following command:
    49118 15:56:44 (0) **
    49119 15:56:44 (0) **    i.e. 'WINMGMT.EXE /SYNCPERF'
    49120 15:56:44 (0) **
    49121 15:56:44 (0) ** WMI MOF representations: ............................................................................................ OK.
    49122 15:56:44 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
    49123 15:56:44 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
    49124 15:56:44 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
    49125 15:56:44 (2) !! WARNING: WMI GET VALUE operation errors reported: ................................................................... 5 WARNING(S)!
    49126 15:56:44 (0) ** - Root, Instance: __EventConsumerProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    49127 15:56:44 (0) ** - Root, Instance: __EventProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    49128 15:56:44 (0) ** - Root, Instance: __EventSinkCacheControl=@, Property: ClearAfter='00000000000015.000000:000' (Expected default='00000000000230.000000:000').
    49129 15:56:44 (0) ** - Root, Instance: __ObjectProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    49130 15:56:44 (0) ** - Root, Instance: __PropertyProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    49131 15:56:44 (0) **
    49132 15:56:44 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    49133 15:56:44 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    49134 15:56:44 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    49135 15:56:44 (0) ** WMI static instances retrieved: ..................................................................................... 6304.
    49136 15:56:44 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    49137 15:56:44 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 3.
    49138 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    49139 15:56:44 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
    49140 15:56:44 (0) **   DCOM: ............................................................................................................. 0.
    49141 15:56:44 (0) **   WINMGMT: .......................................................................................................... 0.
    49142 15:56:44 (0) **   WMIADAPTER: ....................................................................................................... 0.
    49143 15:56:44 (0) **
    49144 15:56:44 (0) ** # of additional Event Log events AFTER WMIDiag execution:
    49145 15:56:44 (0) **   DCOM: ............................................................................................................. 0.
    49146 15:56:44 (0) **   WINMGMT: .......................................................................................................... 0.
    49147 15:56:44 (0) **   WMIADAPTER: ....................................................................................................... 0.
    49148 15:56:44 (0) **
    49149 15:56:44 (0) ** 34 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
    49150 15:56:44 (0) ** => This error is typically a WMI error. This WMI error is due to:
    49151 15:56:44 (0) **    - a missing WMI class definition or object.
    49152 15:56:44 (0) **      (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
    49153 15:56:44 (0) **      You can correct the missing class definitions by:
    49154 15:56:44 (0) **      - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
    49155 15:56:44 (0) **      Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
    49156 15:56:44 (0) **            (This list can be built on a similar and working WMI Windows installation)
    49157 15:56:44 (0) **            The following command line must be used:
    49158 15:56:44 (0) **            i.e. 'WMIDiag CorrelateClassAndProvider'
    49159 15:56:44 (0) **      Note: When a WMI performance class is missing, you can manually resynchronize performance counters
    49160 15:56:44 (0) **            with WMI by starting the ADAP process.
    49161 15:56:44 (0) **    - a WMI repository corruption.
    49162 15:56:44 (0) **      In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
    49163 15:56:44 (0) **      to validate the WMI repository operations.
    49164 15:56:44 (0) **    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
    49165 15:56:44 (0) **          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
    49166 15:56:44 (0) **          i.e. 'WMIDiag WriteInRepository=Root'
    49167 15:56:44 (0) **    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
    49168 15:56:44 (0) **      the WMI repository must be reconstructed.
    49169 15:56:44 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
    49170 15:56:44 (0) **          otherwise some applications may fail after the reconstruction.
    49171 15:56:44 (0) **          This can be achieved with the following command:
    49172 15:56:44 (0) **          i.e. 'WMIDiag ShowMOFErrors'
    49173 15:56:44 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
    49174 15:56:44 (0) **          ALL fixes previously mentioned.
    49175 15:56:44 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
    49176 15:56:44 (0) **
    49177 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    49178 15:56:44 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
    49179 15:56:44 (0) ** INFO: Unexpected registry key value:
    49180 15:56:44 (0) **   - Current:  HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 0
    49181 15:56:44 (0) **   - Expected: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 1
    49182 15:56:44 (0) **     From the command line, the registry configuration can be corrected with the following command:
    49183 15:56:44 (0) **     i.e. 'REG.EXE Add "HKLM\SOFTWARE\Microsoft\WBEM\CIMOM" /v "Logging" /t "REG_SZ" /d "1" /f'
    49184 15:56:44 (0) **
    49185 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    49186 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    49187 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    49188 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    49189 15:56:44 (0) **
    49190 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    49191 15:56:44 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
    49192 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    49193 15:56:44 (0) **
    49194 15:56:44 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\USERS\CONN.LOMBARD\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_2K8R2.SRV.SP1.64_SSCRDS02_2015.04.15_15.48.25.LOG' for details.
    49195 15:56:44 (0) **
    49196 15:56:44 (0) ** WMIDiag v2.1 ended on 15 April 2015 at 15:56 (W:110 E:41 S:1).
    This seems to be the biggest problem:
    48960 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\SYSTEM' DOES NOT match corresponding expected trustee rights (Actual->Default)
    This seems to be the second biggest error (and there are a few of them):
    0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    I have tried:
    winmgmt /resyncperf
    winmgmt /verifyrepository
    winmgmt /salvagerepository
    winmgmt /resetrepository
    I have also tried registering the mof files with
    MOFCOMP <FileName.mof>
    Lastly, I even disabled the WMI service, renamed the Repository folder, and had it rebuild the repository.
    I got stuck on re registering the 'NT AUTHORITY\SYSTEM' (I think it is in the Components section in Administrative tools), as I could not find clear instructions on exactly how to go about it.
    Chkdsk found no errors
    Sfc /scannow found no errors
    winmgmt /verifyrepository finds no errors.
    I'm hoping someone here might be able to steer me in the right direction to get this resolved, as I do not want to rebuild a server that hosts a connection broker and has over 100 user profiles on it, as well as some very annoying and finniky LOB apps installed,
    which will have to manually be reinstalled for each profile.

    Hi,
    Here is a blog regarding how to fix WMI issue might be useful to you:
    Fixing WMI issues Using Batch Script
    http://social.technet.microsoft.com/wiki/contents/articles/6887.fixing-wmi-issues-using-batch-script.aspx
    In addition, you mentioned Remote Desktop Servers are in a cluster setup, would you tell us how did you create the cluster?
    As far as I know, with RD Connection Broker, we don’t need to create a cluster but just add multiple RD session hosts into one collection, then RD connection Broker would redirect sessions automatically.
    Best Regards,
    Amy
    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Ccm.config issue - cluster

    <pre>Hi there,
    XI 3.1 , Linux
    We have a very strange situation.
    We built a cluster for two servers bo1 and bo2 - they had SIA nodes called SIA1 and SIA2 respectively
    A week or two ago, the BO repository became corrupted and we had to re-initalise it
    This meant re-building the cluster. This necessitated the creatiion of a new SIA node for bo2 called SIAII (not my idea!!)
    We did this using cmsdbsetup
    This appeared to work and we appeared to have a working cluster
    We noticed yesterday that a scheduled webi doc created on bo1 that was to run every 15 minutes was intermittently failing - about 3 out of 10 instances failed.
    When we dug deeper, we were able to establish that the webi doc failed when the request was passed to bo2 - indeed it appeared to bring down the wireportserver.exe (both of them)
    We re-checked the cluster via cmsdbsetup and everything looked fine.
    Then we checked the ccm.config for bo1 and bo2 and things look a little strange. I believe a colleague may edited ccm.config incorrectly - there were 2 sets of entries in ccm.config for bo2 - one for SIA2 and another for SIAII. Perhaps the wrong one was removed/edited
    Below is the comparsion of the 2 ccm.config files (bo2 on the left; bo1 on the right)
    Neither have anything ins CLUSTER_NAMESERVER=""  - is this correct
    MYSQLHOSTNAME is incorrect on both
    CMSCLUSTER="no"  ?
    On bo2 the node name is  SIANODENAME="SIA2"
    We looked at the registry entries and we can see entries for the old SIA...
    Real question here is whether the ccm.config is accessed when one member of the cluster passed a report request to the other cluster member - would this be our issue?
    SERVICENAME_AUDIT="BOE120_AUDIT"                                SERVICENAME_AUDIT="BOE120_AUDIT"
    NAMESERVER="bo2"                                              | NAMESERVER="bo1"
    DBTYPE="MySQL"                                                  DBTYPE="MySQL"
    INSTALLTYPE="new"                                               INSTALLTYPE="new"
    REINIT="yes"                                                    REINIT="yes"
    BOBJEVERSION="12.0"                                             BOBJEVERSION="12.0"
    SHUTDOWNPORT="8005"                                             SHUTDOWNPORT="8005"
    REGFILE="/home/BOXI/bobje/data/.bobj"                           REGFILE="/home/BOXI/bobje/data/.bobj"
    DBTYPE_AUDIT="MySQL"                                            DBTYPE_AUDIT="MySQL"
    CLUSTER_NAMESERVER=""                                           CLUSTER_NAMESERVER=""
    CONNECTORPORT="8080"                                            CONNECTORPORT="8080"
    SIAPORTNUMBER="6410"                                            SIAPORTNUMBER="6410"
    BOBJELANG="en"                                                  BOBJELANG="en"
    BOBJELICENSEKEY="XXXX-xxxxxx-xxxxxxxxx-xxxx"                    BOBJELICENSEKEY="XXXX-xxxxxx-xxxxxxxxx-xxxx"
    MYSQLHOSTNAME="127.0.0.1"                                       MYSQLHOSTNAME="127.0.0.1"
    PRODUCTID_NAME="BusinessObjects"                                PRODUCTID_NAME="BusinessObjects"
    PRODUCTID_VER="12.1"                                            PRODUCTID_VER="12.1"
    LOCALNAMESERVER="bo2"                                         | LOCALNAMESERVER="bo1"
    PIDDIR="/home/BOXI/bobje/serverpids"                            PIDDIR="/home/BOXI/bobje/serverpids"
    CMSCLUSTER="no"                                                 CMSCLUSTER="no"
    REDIRECTPORT="8443"                                             REDIRECTPORT="8443"
    SIANODENAME="SIA2"                                            | SIANODENAME="SIA"
    DEFAULT_NAMESERVER="bo2"                                      | DEFAULT_NAMESERVER="bo1"
    INSTALL_DIR="/home/BOXI/bobje/"                                 INSTALL_DIR="/home/BOXI/bobje/"
    BOBJEUSERNAME="toronto1"                                        BOBJEUSERNAME="toronto1"
    CMSNAMESERVER="bo2"                                           | CMSNAMESERVER="bo1"
    DATABASEUID="toronto1"                                          DATABASEUID="toronto1"
    INSTALLMYSQL="yes"                                              INSTALLMYSQL="yes"
    BOBJEDIR="/home/BOXI/bobje/"                                    BOBJEDIR="/home/BOXI/bobje/"
    BOBJEINSTALLLOCAL="system"                                      BOBJEINSTALLLOCAL="system"
    SERVICENAME="BOE120"                                            SERVICENAME="BOE120"
    CMSPORTNUMBER="6400"                                            CMSPORTNUMBER="6400"
    CLUSTERPORTNUMBER="6400"                                        CLUSTERPORTNUMBER="6400"
    SERVICEPORT="3306"                                              SERVICEPORT="3306"
    SERVICEPORT_AUDIT="3306"                                        SERVICEPORT_AUDIT="3306"
    MYSQLHOSTNAME_AUDIT="127.0.0.1"                                 MYSQLHOSTNAME_AUDIT="127.0.0.1"
    SIAIILAUNCH='"/home/BOXI/bobje/enterprise120/generic/bobjrest | SIALAUNCH='"/home/BOXI/bobje/enterprise120/generic/bobjrestar
    </pre>
    Edited by: jemstar on Jun 25, 2009 12:42 PM

    <pre>The logs are attached below - might be a registry related issue??
    ceserver.cpp:968:virtual bool CDZServer::onInitialize(): TraceLog message 1
    2009/06/25 10:40:42.468|>>|E| |16511|1137466256| |||||||||||||||**ERROR:ceserver:invalid entry General\Directories\Config in registry [ceserver.cpp;968]
    SystemHelpers.cpp:532:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 2
    2009/06/25 10:41:40.613|>>|E| |16511|1170385808| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:532: unable to resolve the USER_DOCUMENTS variable
    SystemHelpers.cpp:540:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 3
    2009/06/25 10:41:40.613|>>|E| |16511|1170385808| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:540: unable to resolve the USER_PROFILE_APP_DIR variable
    SystemHelpers.cpp:532:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 4
    2009/06/25 10:41:40.850|>>|E| |16511|1199270800| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:532: unable to resolve the USER_DOCUMENTS variable
    SystemHelpers.cpp:540:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 5
    2009/06/25 10:41:40.850|>>|E| |16511|1199270800| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:540: unable to resolve the USER_PROFILE_APP_DIR variable
    SystemHelpers.cpp:532:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 6
    2009/06/25 10:47:06.844|>>|E| |16511|1170385808| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:532: unable to resolve the USER_DOCUMENTS variable
    SystemHelpers.cpp:540:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 7
    2009/06/25 10:47:06.844|>>|E| |16511|1170385808| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:540: unable to resolve the USER_PROFILE_APP_DIR variable
    SystemHelpers.cpp:532:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 8
    2009/06/25 10:47:39.350|>>|E| |16511|1170385808| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:532: unable to resolve the USER_DOCUMENTS variable
    SystemHelpers.cpp:540:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 9
    2009/06/25 10:47:39.350|>>|E| |16511|1170385808| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:540: unable to resolve the USER_PROFILE_APP_DIR variable
    SystemHelpers.cpp:532:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 10
    2009/06/25 10:48:30.154|>>|E| |16511|1170385808| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:532: unable to resolve the USER_DOCUMENTS variable
    SystemHelpers.cpp:540:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 11
    2009/06/25 10:48:30.154|>>|E| |16511|1170385808| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:540: unable to resolve the USER_PROFILE_APP_DIR variable
    SystemHelpers.cpp:532:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 12
    2009/06/25 10:51:39.548|>>|E| |16511|1176263568| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:532: unable to resolve the USER_DOCUMENTS variable
    SystemHelpers.cpp:540:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 13
    2009/06/25 10:51:39.548|>>|E| |16511|1176263568| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:540: unable to resolve the USER_PROFILE_APP_DIR variable
    SystemHelpers.cpp:532:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 14
    2009/06/25 10:54:22.550|>>|E| |16511|1198218128| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:532: unable to resolve the USER_DOCUMENTS variable
    SystemHelpers.cpp:540:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 15
    2009/06/25 10:54:22.550|>>|E| |16511|1198218128| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:540: unable to resolve the USER_PROFILE_APP_DIR variable
    SystemHelpers.cpp:532:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 16
    2009/06/25 10:55:55.728|>>|E| |16511|1170385808| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:532: unable to resolve the USER_DOCUMENTS variable
    SystemHelpers.cpp:540:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 17
    2009/06/25 10:55:55.728|>>|E| |16511|1170385808| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:540: unable to resolve the USER_PROFILE_APP_DIR variable
    SystemHelpers.cpp:532:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 18
    2009/06/25 10:56:44.085|>>|E| |16511|1170385808| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:532: unable to resolve the USER_DOCUMENTS variable
    SystemHelpers.cpp:540:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 19
    2009/06/25 10:56:44.085|>>|E| |16511|1170385808| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:540: unable to resolve the USER_PROFILE_APP_DIR variable
    SystemHelpers.cpp:532:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 20
    2009/06/25 10:59:11.076|>>|E| |16511|1170385808| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:532: unable to resolve the USER_DOCUMENTS variable
    SystemHelpers.cpp:540:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 21
    2009/06/25 10:59:11.076|>>|E| |16511|1170385808| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:540: unable to resolve the USER_PROFILE_APP_DIR variable
    SystemHelpers.cpp:532:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 22
    2009/06/25 11:01:11.492|>>|E| |16511|1199270800| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:532: unable to resolve the USER_DOCUMENTS variable
    SystemHelpers.cpp:540:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 23
    2009/06/25 11:01:11.492|>>|E| |16511|1199270800| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:540: unable to resolve the USER_PROFILE_APP_DIR variable
    SystemHelpers.cpp:532:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 24
    2009/06/25 11:06:19.005|>>|E| |16511|1176263568| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:532: unable to resolve the USER_DOCUMENTS variable
    SystemHelpers.cpp:540:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 25
    2009/06/25 11:06:19.005|>>|E| |16511|1176263568| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:540: unable to resolve the USER_PROFILE_APP_DIR variable
    SystemHelpers.cpp:532:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 26
    2009/06/25 11:11:12.031|>>|E| |16511|1170385808| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:532: unable to resolve the USER_DOCUMENTS variable
    SystemHelpers.cpp:540:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 27
    2009/06/25 11:11:12.031|>>|E| |16511|1170385808| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:540: unable to resolve the USER_PROFILE_APP_DIR variable
    kc3xmlGenericParser.cpp:389:bool Cube::XmlTools::ValueTypedConstant::Validate(const Cube::XmlTools::ic3TokenTranslator*): TraceLog message 28
    2009/06/25 11:14:01.242|>>|E| |16511|1170385808| |||||||||||||||**ERROR:C3_GenericParser:ValueTypedConstant::Validate - Client - Invalid value : B95ED5004B624ADF927180432D8E2018 [kc3xmlGenericParser.cpp;389]
    kc3cdbdataprovider.cpp:3641:virtual BOResult cdbDataProvider::SetQuerySpec(const ibo_ptr<iboUnknown>&): TraceLog message 29
    2009/06/25 11:14:01.250|>>|E| |16511|1170385808| |||||||||||||||**ERROR:C3_Dataprovider:QuerySpec Validate failed ! [kc3cdbdataprovider.cpp;3641]
    kdgDocument.cpp:10587:void dgDocument::Check(bool, const char*, bool) const: TraceLog message 30
    2009/06/25 11:14:01.250|>>|E| |16511|1170385808| |||||||||||||||**ERROR:dgDocument:An internal error occured while dgDocument is calling pDataProvider->SetQuerySpec(pQuerySpec) [kdgDocument.cpp;10587]
    kdgDocumentEx.cpp:1589:virtual BOResult dgDocument::SetQueryMDP(const bo_wstring&, const ibo_ptr<iboUnknown>&, std::ostream&, std::ostream*): TraceLog message 31
    2009/06/25 11:14:01.251|>=|E|X|16511|1170385808| |||||||||||||||Uncaught Exception in SilentScope: dgDocumentEx:SetQueryMDP: 0.009
    kdgDocument.cpp:4342:BOResult dgDocument::SetQueryMDP(const dgCommandParser::DPCOMMAND&, std::ostream&): TraceLog message 32
    2009/06/25 11:14:01.251|>=|E|X|16511|1170385808| |||||||||||||||Uncaught Exception in SilentScope: dgDocument:SetQueryMDP: 0.009
    kdgDocument.cpp:4020:void dgDocument::UpdateQueryMDP(const dgCommandParser::DPCOMMAND&, std::ostream&): TraceLog message 33
    2009/06/25 11:14:01.251|>=|E|X|16511|1170385808| |||||||||||||||Uncaught Exception in SilentScope: dgDocument:UpdateQueryMDP: 0.009
    kdgDocument.cpp:1649:virtual BOResult dgDocument::ProcessDPCommands(std::istream&, bool, std::ostream&): TraceLog message 34
    2009/06/25 11:14:01.251|>=|E|X|16511|1170385808| |||||||||||||||Uncaught Exception in SilentScope: dgDocument:ProcessDPCommands: 0.01
    SystemHelpers.cpp:532:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 35
    2009/06/25 11:32:27.546|>>|E| |16511|1199270800| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:532: unable to resolve the USER_DOCUMENTS variable
    SystemHelpers.cpp:540:static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&): TraceLog message 36
    2009/06/25 11:32:27.547|>>|E| |16511|1199270800| |||||||||||||||in static bo_utf8string Helpers::Registry::expandUserDocumentDir(bo_utf8string&) at SystemHelpers.cpp:540: unable to resolve the USER_PROFILE_APP_DIR variable
    </pre>

  • Corrupted User Accounts in Windows Vista 64 Home Premium?

    ***FYI I'm using my desktop.
    Toshiba Satellite L305-S5908
    Model #: PSLB8U-05202F
    Windows Vista 64
    So just today, I had accidently dropped my laptop. I was logged into my user account, and it completely froze a few moments after. I had to reboot it, and when I did, I could not log in to my user account at all! I would be able to type in the password, but once I hit ENTER, it turned blank with only the Windows Vista 64 background displaying. I went on safe mode, and surprisingly, I was able to log onto the user account.
    I have another user account (that I rarely use) that I could log on to safe mode as well. However on normal start-up, I was able to log in, but then it completely froze again. The second time I tried to log onto that user account, the computer completely froze when I was about to type in the password.
    From what Toshiba support told me, the User accounts must have been corrupted from the drop, and they told me to Google "How to fix corrupted user accounts". However, from research I am supposed to create a new user account but I cannot make a new one because I cannot log into any of the user accounts at all. (They cannot help me any further because my warranty expired.)
    So, I'm turning to you forum. How do I fix this?

    I deleted the bad user accounts, and saved their files into the new user account.
    The proper way to copy a profile is detailed here.
       Fix a corrupted user profile 
    I did Disk Check again, and it got past the previous stuck point, but it is now stuck on the 524373th free cluster. Should I make a new thread dealing with the new issue I have?
    I forgot to mention that it may be necessary to run chkdsk /r many times.
    No necessity for a new thread.
    ...seems like I have to pay for it?
    Yes, SpinRite costs money. But it's a good product and the circumstances may warrant it. It might come in handy for another drive in the future as well.
    In this case, you may prefer to purchase a new drive. It may turn out that you need a new drive in any case. Certainly, you should be prepared for that by having the recovery discs.
    -Jerry

  • File corruption on SDCard when multiple files are being written from WinCE 6.0R3

    We currently have file corruption problems which we have been able to reproduce on our system which uses WinCE 6.0R3. We have an SDCard in our system which is mounted as the root FS.  When multiple files are being written to the file system we occasionally
    see file corruption with data destined from one file, ending up in another file, or in another location in the same file.  We have already written test SW that we have been able to use to reproduce the problem, and have worked with the SDCard vendor to
    check that the memory controller on the card is not the source of the problems.
    We know that the data we send to WriteFile() is correct, and that the data which eventually gets sent through the SDCard driver to the SD card is already corrupted.
    We believe that the problem is somewhere in the microsoft private sources between the high level filesystem API calls and the low level device calls that get the data onto the HW.
    We have confirmed that the cards that get corrupted are all good and this is not a case ofpoor quality flash memory in the cards. The same cards that fail under WinCE 6.0R3 never fail under the same types of testing on Windows, Mac OX, or linux.  We
    can hammer the cards with single files writes over and over, but as soon as multiple threads are writing multiple files it is only a matter of time before a corruption occurs.
    One of the big problems is that we are using the sqlcompact DB for storing some data and this DB uses a cache which get's flushed on it's own schedule. Often the DB gets corrupted because other files are being written when the DB decides to flush.
    So we can reproduce the error (with enough time), and we know that data into the windows CE stack of code is good, but it comes out to the SDcard driver corrupted.  We have tried to minimize writes to the file system, but so far we have not found a
    way to make sure only one file can be written at once. Is there a setting or an API call that we can make to force the OS into only allowing one file write at a time, or a way of seeing how the multiple files are managed in the private sources?
    Thanks
    Peter

    All QFE's have been applied we are building the image so we have some control.
    I have build an image which used the debug DLL's of the FATFS and I have enabled all of the DebugZones.  The problem is still happening. From the timings in the debug logs and the timestamps in the data which corrupts the test file I have been able
    to see that the file is corrupted AFTER the write is complete. Or at least that's how it seems.
    We finished writing the file and closed the handle. Then more data is written to other files. When we get around to verifying the file it now contains data from the files that were subsequently written.
    What I think I need to do is figure out in detail how the two files were "laid down" onto the SDCard.  If the system used the same cluster to write the 2 files then that would explain the issue.

  • Hyper-V 2012 R2 generation 2 VM corrupted system partition after restart

    Hi
    We have a cluster running on Windows Server 2012 R2 with Hyper-V feature.
    One VM that has Windows 2012 R2 Standard OS installed (generation 2) was corrupted via restart.
    VM has 3 virtual disks (VHDX) - first for system (dynamic size), second for SQL_data (fixed size) , third for SQL_logs (fixed size)
    Yesterday, I restarted VM and VM didn't come up, I got error
    - 'Boot Failed. Windows Boot Manager'
    - 'Boot Failed. EFI SCSI Device'
    Looked all three VHDX we noticed that the first one (system) was corrupted - partition and MBR are gone inside VHDX.
    Second and third one are OK, we can mount them and access all data on it.
    It looks like on first VHDX (system with SQL 2014 installed) partition was corrupted, so we can't do repair because it's says unknown partition.
    There were no updates applied to VM, corrupted partition is 40GB size (dynamical) with 18GB of data used.
    This is first generation 2 VM that we have, all others are generation 1 without any problems.
    Can anyone please explain us, how can this happened, since we did nothing inside VM, also cluster reports no errors, checking VHDX looks fine, just partition inside got corrupted.
    We like to find out what happened, before we deploy more Win2012 R2 VM (gen2) in production envirionment.
    Thank you in advance 
    Regards
    Mike

    Hi Mike ,
     " The most common causes of data corruption in the VHD file are from:
    Data corruption due to faulty / failing physical storage
    Data corruption due to transferring files over faulty / failing networks
    Maybe the following link is helpful :
    http://blogs.technet.com/b/tonyso/archive/2011/12/06/how-to-fix-a-corrupted-hyper-v-vhd-file.aspx
    Hope it helps
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • After Patch  10.2.0.4, got "voting disk  corrupted" error.

    Dear all,
    My setting is:
    OS:RHEL4.8 U8 x86
    DB:10.2.0.1
    CRS:10.2.0.1
    After I installed Patchset 10.2.0.4 and execute $CRS_HOME/install/root102.sh, I could't start clusterware anymore. After checking ocssd.log, I found some messages like this:
    [    CSSD]2010-01-07 15:53:06.519 [3086919360] >TRACE: clssscmain: local-only set to false
    [    CSSD]2010-01-07 15:53:06.562 [3086919360] >TRACE: clssnmReadNodeInfo: added node 1 (x101) to cluster
    [    CSSD]2010-01-07 15:53:06.578 [3086919360] >TRACE: clssnmReadNodeInfo: added node 2 (x102) to cluster
    [    CSSD]2010-01-07 15:53:06.580 [3086919360] >TRACE: clssnmInitNMInfo: Initialized with unique 1262850786
    [    CSSD]2010-01-07 15:53:06.586 [3086919360] >TRACE: clssNMInitialize: Initializing with OCR id (33483723)
    [    CSSD]2010-01-07 15:53:06.650 [84294560] >TRACE: clssnm_skgxninit: Compatible vendor clusterware not in use
    [    CSSD]2010-01-07 15:53:06.650 [84294560] >TRACE: clssnm_skgxnmon: skgxn init failed
    [    CSSD]2010-01-07 15:53:06.657 [3086919360] >TRACE: clssnmNMInitialize: misscount set to (60), impending reconfig threshold set to (56000)
    [    CSSD]2010-01-07 15:53:06.659 [3086919360] >TRACE: clssnmNMInitialize: Network heartbeat thresholds are: impending reconfig 30000 ms, reconfig start (misscount) 60000 ms
    [    CSSD]2010-01-07 15:53:06.669 [3086919360] >TRACE: clssnmDiskStateChange: state from 1 to 2 disk (0//ocfs/voting)
    [    CSSD]2010-01-07 15:53:06.669 [84294560] >TRACE: clssnmvDPT: spawned for disk 0 (/ocfs/voting)
    [    CSSD]2010-01-07 15:53:08.755 [84294560] >TRACE: clssnmDiskStateChange: state from 2 to 4 disk (0//ocfs/voting)
    [    CSSD]2010-01-07 15:53:08.821 [113339296] >TRACE: clssnmvKillBlockThread: spawned for disk 0 (/ocfs/voting) initial sleep interval (1000)ms
    [    CSSD]2010-01-07 15:53:08.889 [3086919360] >TRACE: clssnmFatalInit: fatal mode enabled
    [    CSSD]2010-01-07 15:53:08.999 [94784416] >TRACE: clssnmClusterListener: Spawned
    [    CSSD]2010-01-07 15:53:09.002 [94784416] >TRACE: clssnmClusterListener: Listening on (ADDRESS=(PROTOCOL=tcp)(HOST=x102-priv)(PORT=49895))
    [    CSSD]2010-01-07 15:53:09.002 [94784416] >TRACE: clssnmconnect: connecting to node(1), con(0x81bc480), flags 0x0003
    [    CSSD]2010-01-07 15:53:09.069 [3083459488] >TRACE: clssgmclientlsnr: Spawned
    [    CSSD]2010-01-07 15:53:09.072 [113339296] >ERROR: clssnmvDiskKillCheck: voting disk corrupted (0x00000000,0x00000000) (0//ocfs/voting)
    [    CSSD]2010-01-07 15:53:09.072 [113339296] >TRACE: clssnmDiskStateChange: state from 4 to 3 disk (0//ocfs/voting)
    [    CSSD]2010-01-07 15:53:09.072 [130767776] >TRACE: clssnmDiskPMT: disk offline (0//ocfs/voting)
    [    CSSD]2010-01-07 15:53:09.072 [130767776] >ERROR: clssnmDiskPMT: Aborting, 1 of 1 voting disks unavailable
    [    CSSD]2010-01-07 15:53:09.072 [130767776] >ERROR: ###################################
    [    CSSD]2010-01-07 15:53:09.072 [130767776] >ERROR: clssscExit: CSSD aborting
    [    CSSD]2010-01-07 15:53:09.072 [130767776] >ERROR: ###################################
    [    CSSD]--- DUMP GROCK STATE DB ---
    I tried to recreate my voting disk like this:
    $CRS_HOME/bin/crsctl add css votedisk /ocfs/voting1 -force
    $CRS_HOME/bin/crsctl delete css votedisk /ocfs/voting -force
    $CRS_HOME/bin/crsctl add css votedisk /ocfs/voting -force
    $CRS_HOME/bin/crsctl delete css votedisk /ocfs/voting1 -force
    Then run root102.sh again but still got the same error message about "voting disk corrupted".
    I was totally confused and don't know how to fix it.
    Please, any suggestion would be appreciated.

    Hello,
    Did u try restore the OCR?
    http://download-west.oracle.com/docs/cd/B19306_01/rac.102/b14197/votocr.htm#i1012456
    The steps to apply RAC patch were followed correctly?
    See a patchset roadmap at http://mufalani.blogspot.com/2009/06/applying-10204-patch-on-rac-systems.html
    Best Regards,
    Rodrigo Mufalani
    http://www.mrdba.com.br/mufalani

  • Hyper-V cluster: Unable to fail VM over to secondary host

    I am working on a Server 2012 Hyper-V Cluster. I am unable to fail my VMs from one node to the other using either LIVE or Quick migration.
    A force shutdown of VMHost01 will force a migration to VMHost02. And once we are on VMHost02 we can migrate back to VMHost01, but once that is done we can't move the VMs back to VMHost02 without a force shutdown.
    The following error pops up:
    Event ID: 21502 The Virtual Machine Management Service failed to establish a connection for a Virtual machine migration with host.... The connection attempt failed because the connected party did not properly respond after a period of time, or the established
    connection failed because connected host has failed to respond (0X8007274C)
    Here's what I noticed:
    VMMS.exe is running on VMHost02 however it is not listening on Port 6600. Confirmed this after a reboot by running netstat -a. We have tried setting this service to a delayed start.
    I have checked Firewall rules and Anti-Virus exclusions, and they are correct. I have not run the cluster validation test yet, because I'll need to schedule a period of downtime to do so.
    We can start/stop the VMMS.exe service just fine and without errors, but I am puzzled as to why it will not listen on Port 6600 anywhere. Anyone have any suggestions on how to troubleshoot this particular issue? 
    Thanks,
    Tho H. Le

    Just ran into the same issue in a 16-node cluster being managed by VMM. When trying to live migrate VMs using the VMM console the migration would fail with the following: Error 10698. Failover Cluster manager would report the following error code: Error
    (0x8007274C).
    + Validated Live Migration and Cluster networks. Everything checked out.
    + Looking in Hyper-V manager and migrations are enabled and correct networks displayed.
    + Found this particular Blog that mentions that the Virtual Machine Management service is not listening to port 6600
    http://blogs.technet.com/b/roplatforms/archive/2012/10/16/shared-nothing-migration-fails-0x8007274c.aspx
    Ran the following from an elivated command line:
    Netstat -ano | findstr 6600
    Node 2 did not return anything
    Node 1 returned correct output:
    TCP
    10.xxx.251.xxx:6600
    0.0.0.0:0
    LISTENING
    4540
    TCP
    10.xxx.252.xxx:6600
    0.0.0.0:0
    LISTENING
    4560
    Set Hyper-V Virtual Machine Service to delayed start.
    Restarted the service; no change.
    Checked the Event Logs for Hyper-V VMMS and noted the following events - VMMS Listener started
    for Live Migration networks, and then shortly after listener stopped.
    Removed the system from the cluster and restarted - No change
    Checked this host by running gpedit.msc - could not open console: Permission Error
    Tried to run a GPO refresh (gpupdate /force), but error returned that LocalGPO could not apply registry settings. Group Policy
    processing would not continue until this was resolved.
    Checked the local group policy folder on node 2 and it was corrupt:
    C:\Windows\System32\GroupPolicy\Machine\reg.pol showed 0K for the size.
    Copied local policy folders from Node 1 to 2, and then was able to refresh the GPOs.
    Restarting the VMMS service did not change the status of the ports.
    Restarted Server, added Live Migration networks back into Hyper-V manager and now netstat output reports that VMMS service
    is listening on 6600.

  • Unplanned failover in a Hyper-V cluster vs unplanned failover in an ordinary (not Hyper-V) cluster

    Hello!
    Please excuse me if you think my question is silly, but before deploying something  in a production environment I'd like to dot the i's  and cross the t's.
    1) Suppose there's a two node cluster with a Hyper-V role that hosts a number of highly available VM.
    If the both cluster nodes are up and running an administrator can initiate a planned failover wich will transfer all VMs
    including their system state to another node without downtime.
    In case any cluster node goes down unexpectedly the unplanned failover fires up that will transfer all VMs to another node
    WITHOUT their system state. As far as I understand this can lead to some data loss.
    http://itknowledgeexchange.techtarget.com/itanswers/how-does-live-migration-differ-from-vm-failover/
    If, for example, I have an Exchange vm and it would be transfered to the second node during unplanned failover in the Hyper-V cluster I will lose some data by design.
    2) Suppose there's a two node cluster with the Exchange clustered installation: in case one node crashes the other takes over without any data loss.
    Conclusion: it's more disaster resilient to implement some server role in an "ordinary" cluster that deploy it inside a vm in the Hyper-V cluster.
    Is it correct?
    Thank you in advance,
    Michael

    "And if this "anything in memory and any active threads" is so large that can take up to 13m15s to transfer during Live Migration it will be lost."
    First, that 13m15s required to live migrate all your VMs is not the time it takes to move individual VMs.  By default, Hyper-V is set to move a maximum of 2 VMs at a time.  You can change that, but it would be foolish to increase that value if
    all you have is a single 1GE network.  The other VMs will be queued.
    Secondly, you are getting that amount of time confused with what is actually happening.  Think of a single VM.  Let's even assume that it has so much memory and is so active that it takes 13 minutes to live migrate.  (Highly unlikely, even
    on a 1 GE NIC).  During that 13 minutes the VM takes to live migrate, the VM continues to perform normally.  In fact, if something happens in the middle of the LM, causing the LM to fail, absolutely nothing is lost because the VM is still operating
    on the original host.
    Now let's look at what happens when the host on which that VM is running fails, causing a restart of the VM on another node of the cluster.  The VM is doing its work reading and writing to its data files.  At that instance in time when the host
    fails, the VM may have some unwritten data buffers in memory.  Since the host fails, the VM crashes, losing whatever it had in memory at the instant in time.  It is not going to lose any 13 minutes of data.  In fact, if you have an application
    that is processing data at this volume, you most likely have something like SQL running.  When the VM goes down, the cluster will automatically restart the VM on another node of the cluster.  SQL will automatically replay transaction logs to recover
    to the best of its ability.
    Is there a possibility of data loss?  Yes, a very tiny possibility for a very small amount.  Is there a possibility of data corruption?  Yes, a very, very tiny possibility, just like with a physical machine.
    The amount of time required for a live migration is meaningless when it comes to potential data loss of that VM.  The potential data loss is pretty much the same as if you had it running on a physical machine, the machine crashed, and then restarted.
    "clustered applicationsDO NOT STOP working during unplanned failover (so there is no recovery time), "
    Not exactly true.  Let's use SQL as an example again.  When SQL is instsalled in a cluster, you install at a minimum one instance, but you can have multiple instances.  When the node on which the active instance is running fails, there is
    a brief pause in service while the instance starts on the other node.  Depending on transactions outstanding, last write, etc., it will take a little bit of time for the SQL instance to be ready to start handling requests on the new node.
    Yes, there is a definite difference between restarting the entire VM (just the VM is clustered) and clustering the application.  Recovery time is about the biggest issue.  As you have noted, restarting a VM, i.e. rebooting it, takes time. 
    And because it takes a longer period of time, there is a good chance that clients will be unable to access the resource for a period of time, maybe as much as 1-5 minutes depending upon a lot of different factors, whereas with a clustered application, the
    clients may be unable to access for up to a minute or so.
    However, the amount of data potentially lost is quite dependent upon the application.  SQL is designed to recover nicely in either environment, and it is likely not to lose any data.  Sequential writing applications will be dependent upon things
    like disk cache held in memory - large caches means higher probability of losing data.  No disk cache means there is not likely to be any loss of data.
    .:|:.:|:. tim

Maybe you are looking for