Names exposed

When sending an email to a group I requasted that all members names not be exposed. Today I found out that they are and one friend is a well know writer and would not like having his email address shared with any one. How can I stop this from happening again. Thanks.

Instead of doing this which I pretty much do not understand, I merely changed his name But thanks anyway.

Similar Messages

  • Server Names exposed while accessing SAP Portal

    We are using FireFox browser to access the SAP Portal application.We are running SAP EnterPrise Portal on NW 7.01. Our Production SAP portal is exposed to
    internet.
    After the users log into the system, using Firefox browser, the server name is seen in the status bar of the
    browser. This is a security threat, as the server names are exposed.
    This issue is not there if we access the sameusing Internet explorer.

    Abdul,
    See this:
    http://help.sap.com/saphelp_nw04s/helpdata/en/b6/8b9aea8d7c11d5bdd8006094191908/frameset.htm
    The suspect is "User Mapping Type". It is probably set to "admin", instead of "admin, user". That is why you do not see the system when logged in as one of the users.
    Also make sure users have permissions in PCD to the system.
    If does not help, check other suspect as SAP help suggests:
    The selected principal does not have end-user permissions for the system.
    The system's logon method does not require any user mapping data for the system (such as "SAPLogonTicket" for a system that is not the SAP reference system).
    The system's user mapping type is not set correctly or not set at all.
    There is no system alias defined for the system.
    There is no system landscape registered, for example, the one contained in Enterprise Portal.
    Regards,
    Slava

  • Turn a text database search result into a clickable .pdf link to specific images

    Hello and Good Afternoon all. 
    This is baffling me to no end, pretty desperate at this point. 
    I have a successfully implemented a search and results page from my database table 'products'.  The results page displays a field from this table as products, msds, datasheet, description.  I would like the msds & datasheet results to be clickable links to files in my images/pdf/msds folder or the images/pdf/datasheet folder. 
    The links are specific filenames such as msds-product.pdf or datasheet-product.pdf..  How can I get these links to open the exact filename that comes up in my search result?  I can make it open the entire folder but I want just the specific file. 
    I don't write code very well - thank you for any help you can provide.  Cindy

    Hi Murray - Here is the exact code in DW on the results page with file names exposed in live view.  I am concerned about not properly implementing this statement - where exactly should I insert?
    <form action="data_search.php" method="get" name="data_results_form" id="data_results_form">
             <p> </p>
             <?php do { ?>
                  <table width="75%" border="0" align="center" cellpadding="5" cellspacing="5" summary="MSDS & Datasheet search results page.  You may click on the hyperlinks to download pdf for each document.">
                       <tr>
                            <td> </td>
                            <td> </td>
                            <td> </td>
                            <td> </td>
                       </tr>
                       <tr>
                            <td style="color: #686666">Product</td>
                            <td style="color: #686666">MSDS</td>
                            <td style="color: #686666">Datasheet</td>
                            <td style="color: #686666">Description</td>
                       </tr>
                       <tr>
                            <td style="color: #23276A; font-family: Gotham, 'Helvetica Neue', Helvetica, Arial, sans-serif; font-style: normal; font-size: 16px;"><?php echo $row_Recordset_results['product']; ?></td>
                            <td style="font-size: 16px"><a href="images/pdf/msds/"".pdf"><?php echo $row_Recordset_results['msds']; ?></a></td>
                            <td style="font-size: 16px"><?php echo $row_Recordset_results['datasheet']; ?></td>
                            <td style="font-size: 16px"><?php echo $row_Recordset_results['description']; ?></td>
                       </tr>
                  </table>
                  <?php } while ($row_Recordset_results = mysql_fetch_assoc($Recordset_results)); ?>
        </form>

  • Problem in Web service callable object!!

    Hi,
    I have created a function module in R/3, and made it RFC enabled.Now i am trying to use this webservice in creating CO for web service.Now when i test it, i am getting this error:
    Web service method http://<hostname>.<fully qualified domain name>.com:8001/sap/bc/soap/wsdl11?services=ZADDITION&sap-client=400&sap-user=<user ID>&sap-password=<Password>
    invocation failed: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://<hostname>.<fully qualified domainname>.com:8001/sap/bc/soap/rfc"; nested exception is:
    com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://<hostname>.<fully qualified domain name>.com:8001/sap/bc/soap/rfc"
    What can be the reason??
    any help will be highly apprecaiated!!
    Thanks & Regards
    Ameya

    Hi,
    Yes i am getting error Could not find logical destination interfaces, check the <b>WSIL URL</b> inserted in visual admin.
    Look.,
    1)my function module name is ZADDITION,(RFC enabled)
    2)IN transaction  WSADMIN, i got the URL as
    default_host/sap/bc/srt/rfc/sap/ZADDITION
    in visual Admin i put this url
    http://<host><fully qualified domain name>:8001/sap/bc/srt/rfc/sap/ZADDITION?sap-client=800&wsdl=1.1,
    please tell me this host name is R/3 server or the portal server?
    IN visual admin i put the above stated url,inserted SID,client,language, Basic Authentication,given UIDPW,
    Then in Design time i was able to fine Logical destination name : Exposing,
    then i clicked on search. but nothing happened
    What can be the problem..is there any problem in my url??
    please guide me, i think we have almost solved this..You have helpd me a lot..
    Regards,
    Ameya

  • Need to make date validation to remove overlab

    I have a problem in date validation
    I will tell you the scenario
    I have department table as a master table and under this department there is some teachers.
    Eeach teacher have Start Hiring Date and End Hiring Date .
    I want to prevent to insert a new teacher with Start Hiring date or End hiring date between any period inserted before in this department .
    This means in any period there is only one hired teacher
    how can I do this validation

    Assumed that you are using ADF BC, I reproduced your use case, and tried this. you can also try it,
        CREATE TABLE test_department
        (      id      numeric(10)      not null,
             name      varchar2(50) not null,
             CONSTRAINT dpt_pk PRIMARY KEY (id)
        CREATE TABLE teachers
        (      id      numeric(10) PRIMARY KEY     ,
             dept_id      numeric(10)      not null,
              start_date date,
              end_date date,
             CONSTRAINT fk_emp  FOREIGN KEY (dept_id)
               REFERENCES test_department(id)
    insert into test_department values (1,'Math');
    insert into teachers values(1,1,to_date('1/1/2010','DD/MM/YYYY'),to_date('31/12/2010','DD/MM/YYYY'));add a validate entity method to you TeacherImpl class.
        public boolean validateTeachers()
            TestDepartmentImpl deptImpl = this.getTestDepartment(); // TestDepartment is the accessor name exposed in TeachersImpl class
            RowIterator iter = deptImpl.getTeachers(); //Teachers is the accessor name exposed in DepartmentImpl class
            boolean flag = true;
            while (iter.hasNext())
                    TeachersImpl currentTeacher = (TeachersImpl)iter.next();
                    if (!currentTeacher.getId().equals(this.getId())) //skip the current teacher from comparison
                        if (this.getStartDate().compareTo(currentTeacher.getStartDate()) >
                            0 && this.getEndDate().compareTo(currentTeacher.getEndDate())<0)
                              flag=false;
            return flag;
        }

  • Incorrect data type when writing to FPGA Read/Write Control

    I have run in to a problem this morning that is causing me substantial headache.  I am programming a CompactRIO chassis running in FPGA mode (not using the scan engine) with LabVIEW 2012.  I am using the FPGA Read/Write Control function to pass data from the RT Host to the FPGA Target.  The data the RT host is sending comes from a Windows host machine (acting as the UI) and is received by the RT Host through a network published variable.
    The network published shared variable (shared between the RT and Windows system) is a Type Def cluster containing several elements, one of which is a Type Def cluster of fixed point numerics.  The RT system reads this shared variable and breaks out the individual elements to pass along to various controls on the FPGA code's front panel.  The FPGA's front panel contains a type def cluster (the same type def cluster, actually) of fixed point numerics.
    The problem comes in the RT code.  After I read the shared variable I unbundle the cluster by name, exposing the sub-cluster of fixed point numerics.  I then drop an FPGA Read/Write Control on the RT block diagram and wire up the FPGA reference.  I left click on the FPGA Read/Write Control and select the cluster of fixed point numerics.  I wire these together and get a coercion dot.  Being a coercion dot hater, I hover over it the dot and see that the wire data type is correct (type def cluster of fixed point numerics), but the terminal data type is listed as a cluster containing a Boolean, code integer and source string, also known as an error cluster.  I delete the wire and check the terminal data type on the Read/Write Control, which is now correctly listed as a type def cluster of fixed point numerics.  Rewiring it causes the terminal to revert back to the error cluster.  I delete the wire again and right click on the terminal to add a control.  Sure enough, a type def cluster of fixed point numerics appears.  Right clicking and adding an indicator to the unbundle attached to the network shared variable produces the proper result.  So, until they are attached to each other, everything works fine.  When I wire these two nodes together, one spontaneously changes to a error cluster.
    Any thoughts would be appreciated.

    My apologies I never got back to responding on this.  I regret that now because I got it to work but never posted how.  I ran in to the exact same problem today and returned to this post to read the fix.  It wasn't there, so I had to go through it all over again.
    The manifestation of the problem this time was that I was now reading from the Read/Write FPGA front panel control and writing to a network published shared variable.  Both of these (the published shared variable and the front panel control) were based on a strict type defined cluster, just like in the original post.  In this instance, it was a completely different cluster in a completely different project, so it was not a one-off thing.
    In addition to getting the coercion dot (one instance becoming an error cluster, recall), LabVIEW would completely explode this time around.  If I saved the VI after changing type definition (I was adding to the cluster) I would get the following error:
    Compile error.  Report this problem to N.I. Tech Support.  Copy cvt,csrc=0xFF
    LabVIEW would then crash hard and shutdown without completing the save.  FYI, I'm running LabVIEW 12.0f3 32-bit.
    If I would then reopen the RT code, the same crash would occur immediately, ad nauseam.  The only way to get the RT code to open was to change the type defined cluster back to the way it was (prior to adding the new element).
    I didn't realize it last time around (what originally prompted this post), but I believe I was adding to a type def cluster when this occurred the first time.
    So, how did I fix it this time around? By this point I tried many, many different things, so it is possible that something else fixed it.  However, I believe that all I had to do was to build the FPGA code that the RT code was referencing.  I didn't even have to deploy it or run it... I just had to build it.  My guess is that the problem was the FPGA Reference vi (needed to communicate with the FPGA) is configured (in my case) to reference a bit file.  When the development FPGA Main.vi ceases to match the bit file, I think that bad things happen.  LabVIEW seems to get confused because the FPGA Main.vi development code is up and shows the new changes (and hence has the updated type def), but when you ask the RT code to do something substantial (Open, Save, etc), it refers to the old bit file that has not yet been updated.  That is probably why the error getting thrown was a compile error.
    I'm going to have to do an additional round of changes, so I will test this theory.  Hopefully I will remember to update this post with either a confirmation or a retraction.

  • [svn:fx-trunk] 12982: Fix for issue with exposing accessible names for combobox list items

    Revision: 12982
    Revision: 12982
    Author:   [email protected]
    Date:     2009-12-15 20:44:23 -0800 (Tue, 15 Dec 2009)
    Log Message:
    Fix for issue with exposing accessible names for combobox list items
    QE notes: none
    Doc notes: none
    Bugs: n/a
    Reviewer: Gordon
    Tests run: checkintests
    Is noteworthy for integration: no
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/ComboBoxAccImpl.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/ListBaseAccImpl.as

    Add this to the end of your nav p CSS selector at Line 209 of your HTML file, after 'background-repeat...':
    margin-bottom: -2px;
    Your nav p will then look like this:
    nav p {
              font-size: 90%;
              font-weight: bold;
              color: #FFC;
              background-color: #090;
              text-align: right;
              padding-top: 5px;
              padding-right: 20px;
              padding-bottom: 5px;
              border-bottom-width: 2px;
              border-bottom-style: solid;
              border-bottom-color: #060;
              background-image: url(images/background.png);
              background-repeat: repeat-x;
              margin-bottom: -2px;

  • JDBC Datasource creation via ANT doesn't expose the JNDI name

    I'm using the wlconfig ANT task to create a Datasource (& JDBC connectionpool) on the weblogic server. The datasource is created fine, and I can test it using the console.
    The problem is that the provided JNDI name isn't exposed in the JNDI tree. This seems to be related to the fact that the following element is generated in the config/jdbc/CP-PoolName-2164-jdbc.xml
    &lt;jdbc-data-source&gt;
    &lt;name&gt;PoolName&lt;/name&gt;
    &lt;internal-properties&gt;
    *&lt;property&gt;*
    *&lt;name&gt;LegacyType&lt;/name&gt;*
    *&lt;value&gt;1&lt;/value&gt;*
    *&lt;/property&gt;*
    When removing the LegacyType 1 property from the JDBC config xml, the JNDI name is exposed fine.
    I've used the instructions located at [http://edocs.bea.com/wls/docs100/programming/ant_tasks.html] where an example of a JDBCConnectionPool creation is provided.
    The 10.3 documentation doesn't include the example anymore, but I'm having the problem both on BEA Weblogic 10.0 and Oracle Weblogic 10.3
    &lt;wlconfig url="t3://localhost:7001" username="weblogic" password="weblogic"&gt;
    bq. &lt;query domain="base_domain" type="Server" name="AdminServer" property="adminserver"/&gt;
    bq. &lt;create type="JDBCConnectionPool" name="MediumSecureOnlineNode1Pool" property="customPool1"&gt;
    bq. bq. &lt;set attribute="CapacityIncrement" value="1"/&gt; \\ &lt;set attribute="DriverName" value="oracle.jdbc.OracleDriver"/&gt; \\ &lt;set attribute="InitialCapacity" value="1"/&gt; \\ &lt;set attribute="MaxCapacity" value="10"/&gt; \\ &lt;set attribute="Password" value="pass"/&gt; \\ &lt;set attribute="Properties" value="user=username"/&gt; \\ &lt;set attribute="RefreshMinutes" value="0"/&gt; \\ &lt;set attribute="ShrinkPeriodMinutes" value="15"/&gt; \\ &lt;set attribute="ShrinkingEnabled" value="true"/&gt; \\ &lt;set attribute="TestConnectionsOnCreate" value="true"/&gt; \\ &lt;set attribute="TestConnectionsOnRelease" value="true"/&gt; \\ &lt;set attribute="TestConnectionsOnReserve" value="true"/&gt; \\ &lt;set attribute="TestTableName" value="SQL SELECT 1 FROM DUAL"/&gt; \\ &lt;set attribute="URL" value="jdbc:oracle:thin:@localhost:1521"/&gt; \\ &lt;set attribute="Targets" value="${adminserver}"/&gt;
    &lt;/create&gt;
    As we would like to automate the process of configuring our weblogic instances using ANT, is there a way to create JDBC datasources that don't have the LegacyType 1 element included in the config ?

    Curious if you were ever able to find a resolution to this issue?
    I am facing the same thing now with our Ant scripts and WL10.3 connection pools/datasources.
    I would like to either specify a different LegacyType or suppress it altogether. Any help would be appreciated.
    Many thanks,
    Steve

  • Frontend Server Name is Exposed during Lyncdiscover Query

    Hi,
    Pls see Yellow Text in below image, my FE Name is Exposed on Internet during LyncDiscover.domainname.com
    We are running Lync 2013 Standard Single Server Setup. My Pool Name is same as FrontEnd Server FQDN.
    I only want to expose webext.domainname.com FQDN, wondering where is the issue?
    Best Regards, Ranjit Singh

    Hi Ranjit Singh,
    The internal website is published on ports 80/443, while the external site is published on 8080/4443. It is recommend to use a reverse proxy server, such as TMG 2010 or IIS ARR, to publish the
    external website and redirect 80/443 from the web to the FE server over 8080/4443.
    If you do not use a reverse proxy, this can cause external Lync users unable to access the web services, such as Address Book, Conferencing URL, etc.
    Best regards,
    Eric
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Application error happening at least twice a day. Faulting applicaiton name: wmiprvse.exe

    We're experiencing an issue with one of our Windows Server 2008R2 Standard Edition SP1 servers where an Application error occurs at least twice, and sometimes up to 5 or 6 times per day.  The following error is what we see.  Any help would be greatly
    appreciated, and I'll be checking back frequently to check for updates and provide more info whenever needed.  Thanks!
    General:
    Faulting application name: wmiprvse.exe, version: 6.1.7601.17514, time stamp: 0x4ce79d42
    Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c8f9
    Exception code: 0xc0000374
    Fault offset: 0x00000000000c40f2
    Faulting process id: 0x1bbc
    Faulting application start time: 0x01cd5d65dbeb2e7c
    Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Details:
    System
    Provider
    [ Name]
    Application Error
    EventID
    1000
    [ Qualifiers]
    0
    Level
    2
    Task
    100
    Keywords
    0x80000000000000
    TimeCreated
    [ SystemTime]
    2012-07-09T08:34:39.000000000Z
    EventRecordID
    6812
    Channel
    Application
    Computer
    {FQDN}
    Security
    EventData
    wmiprvse.exe
    6.1.7601.17514
    4ce79d42
    ntdll.dll
    6.1.7601.17514
    4ce7c8f9
    c0000374
    00000000000c40f2
    1bbc
    01cd5d65dbeb2e7c
    C:\Windows\system32\wbem\wmiprvse.exe
    C:\Windows\SYSTEM32\ntdll.dll
    ebe1621c-c9a0-11e1-a1d4-5cf3fce8cef6
    ETA:  I also ran the wmidiag.exe tool from Microsoft.  I saw it as a suggestion on another forum and ran it.  I don't know if it has any bearing here, but this is the log in case it's helpful
    show
    06604 14:51:25 (0) ** WMIDiag v2.1 started on Tuesday, July 10, 2012 at 14:40.
    06605 14:51:25 (0) ** 
    06606 14:51:25 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
    06607 14:51:25 (0) ** 
    06608 14:51:25 (0) ** This script is not supported under any Microsoft standard support program or service.
    06609 14:51:25 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
    06610 14:51:25 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
    06611 14:51:25 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
    06612 14:51:25 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
    06613 14:51:25 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
    06614 14:51:25 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
    06615 14:51:25 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
    06616 14:51:25 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
    06617 14:51:25 (0) ** of the possibility of such damages.
    06618 14:51:25 (0) ** 
    06619 14:51:25 (0) ** 
    06620 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06621 14:51:25 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
    06622 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06623 14:51:25 (0) ** 
    06624 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06625 14:51:25 (0) ** Windows Server 2008 R2 - Service pack 1 - 64-bit (7601) - User {Username} on computer {ComputerName}.
    06626 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06627 14:51:25 (0) ** Environment: ........................................................................................................ OK.
    06628 14:51:25 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #1).
    06629 14:51:25 (0) ** Drive type: ......................................................................................................... SCSI (IBM ServeRAID M5015 SCSI Disk Device).
    06630 14:51:25 (0) ** There are no missing WMI system files: .............................................................................. OK.
    06631 14:51:25 (0) ** There are no missing WMI repository files: .......................................................................... OK.
    06632 14:51:25 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
    06633 14:51:25 (0) ** AFTER running WMIDiag:
    06634 14:51:25 (0) ** The WMI repository has a size of: ................................................................................... 90 MB.
    06635 14:51:25 (0) ** - Disk free space on 'C:': .......................................................................................... 75295 MB.
    06636 14:51:25 (0) **   - INDEX.BTR,                     15818752 bytes,     7/10/2012 2:38:58 PM
    06637 14:51:25 (0) **   - MAPPING1.MAP,                  242388 bytes,       7/10/2012 2:33:33 PM
    06638 14:51:25 (0) **   - MAPPING2.MAP,                  242388 bytes,       7/10/2012 2:38:58 PM
    06639 14:51:25 (0) **   - OBJECTS.DATA,                  77570048 bytes,     7/10/2012 2:38:58 PM
    06640 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06641 14:51:25 (2) !! WARNING: Windows Firewall: .......................................................................................... DISABLED.
    06642 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06643 14:51:25 (0) ** DCOM Status: ........................................................................................................ OK.
    06644 14:51:25 (0) ** WMI registry setup: ................................................................................................. OK.
    06645 14:51:25 (0) ** INFO: WMI service has dependents: ................................................................................... 1 SERVICE(S)!
    06646 14:51:25 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
    06647 14:51:25 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
    06648 14:51:25 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
    06649 14:51:25 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
    06650 14:51:25 (0) **          this can prevent the service/application to work as expected.
    06651 14:51:25 (0) ** 
    06652 14:51:25 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
    06653 14:51:25 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
    06654 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06655 14:51:25 (0) ** WMI service DCOM setup: ............................................................................................. OK.
    06656 14:51:25 (0) ** WMI components DCOM registrations: .................................................................................. OK.
    06657 14:51:25 (0) ** WMI ProgID registrations: ........................................................................................... OK.
    06658 14:51:25 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
    06659 14:51:25 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
    06660 14:51:25 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
    06661 14:51:25 (2) !! WARNING: Some WMI providers EXE/DLL file(s) are missing: ............................................................ 18 WARNING(S)!
    06662 14:51:25 (0) ** - ROOT/QLOGIC_CMPI, QLogic_NIC_Provider, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{28A5F598-F699-4A6B-B9F9-8C7EB9B7359F}:QLogic_NIC_Provider
    06663 14:51:25 (0) ** - ROOT/QLOGIC_CMPI, QLogic_FCHBA_Provider, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{0AE588DD-D2E9-41EB-BCD1-8BF474187EC5}:QLogic_FCHBA_Provider
    06664 14:51:25 (0) ** - ROOT/IBMSD, ADPT_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{B007445E-6AF0-4CBD-9009-809F071FCE69}:ADPT_Module
    06665 14:51:25 (0) ** - ROOT/IBMSD, IBM_PA_Providers, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{2244E0FA-D37A-4F6E-82FB-92F1DB78716D}:IBM_PA_Providers
    06666 14:51:25 (0) ** - ROOT/IBMSD, EndpointRegistrationProviderModule, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{BF833E81-33AA-40ED-B74A-329F006DB4F8}:EndpointRegistrationProviderModule
    06667 14:51:25 (0) ** - ROOT/CIMV2, SBLIM_Data_Gatherer, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{0D03AF80-A160-44EF-9E8B-318201F41693}:SBLIM_Data_Gatherer
    06668 14:51:25 (0) ** - ROOT/ADPT, ADPT_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{B007445E-6AF0-4CBD-9009-809F071FCE69}:ADPT_Module
    06669 14:51:25 (0) ** - ROOT/PG_INTEROP, SBLIM_Data_Gatherer, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{0D03AF80-A160-44EF-9E8B-318201F41693}:SBLIM_Data_Gatherer
    06670 14:51:25 (0) ** - ROOT/PG_INTEROP, LSIESG_SMIS13_HHR_ProviderModule, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{E21064DD-757A-4F2D-B798-81CDFF03B48C}:LSIESG_SMIS13_HHR_ProviderModule
    06671 14:51:25 (0) ** - ROOT/PG_INTEROP, emulex_fc_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{27734403-1E6C-4BC7-B97D-1FE9657B35EC}:emulex_fc_provider_Module
    06672 14:51:25 (0) ** - ROOT/PG_INTEROP, emulex_ucna_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{68D3C192-F517-41CC-B852-BA74A8D05A85}:emulex_ucna_provider_Module
    06673 14:51:25 (0) ** - ROOT/IBMSE, emulex_fc_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{27734403-1E6C-4BC7-B97D-1FE9657B35EC}:emulex_fc_provider_Module
    06674 14:51:25 (0) ** - ROOT/IBMSE, IBM_PA_Providers, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{2244E0FA-D37A-4F6E-82FB-92F1DB78716D}:IBM_PA_Providers
    06675 14:51:25 (0) ** - ROOT/IBMSE, emulex_ucna_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{68D3C192-F517-41CC-B852-BA74A8D05A85}:emulex_ucna_provider_Module
    06676 14:51:25 (0) ** - ROOT/LSI_MR_1_3_0, LSIESG_SMIS13_HHR_ProviderModule, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{E21064DD-757A-4F2D-B798-81CDFF03B48C}:LSIESG_SMIS13_HHR_ProviderModule
    06677 14:51:25 (0) ** - ROOT/EMULEX, emulex_fc_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{27734403-1E6C-4BC7-B97D-1FE9657B35EC}:emulex_fc_provider_Module
    06678 14:51:25 (0) ** - ROOT/EMULEX, emulex_ucna_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{68D3C192-F517-41CC-B852-BA74A8D05A85}:emulex_ucna_provider_Module
    06679 14:51:25 (0) ** - ROOT/BROCADE, brcdprovider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{48898EFD-0F9A-4657-B03D-FF400A7D2CDE}:brcdprovider_Module
    06680 14:51:25 (0) ** => This will make any operations related to the WMI class supported by the provider(s) to fail.
    06681 14:51:25 (0) **    This can be due to:
    06682 14:51:25 (0) **    - the de-installation of the software.
    06683 14:51:25 (0) **    - the deletion of some files.
    06684 14:51:25 (0) ** => If the software has been de-installed intentionally, then this information must be
    06685 14:51:25 (0) **    removed from the WMI repository. You can use the 'WMIC.EXE' command to remove
    06686 14:51:25 (0) **    the provider registration data.
    06687 14:51:25 (0) **    i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\BROCADE path __Win32Provider Where Name='brcdprovider_Module' DELETE'
    06688 14:51:25 (0) ** => If not, you must restore a copy of the missing provider EXE/DLL file(s) as indicated by the path.
    06689 14:51:25 (0) **    You can retrieve the missing file from:
    06690 14:51:25 (0) **    - A backup.
    06691 14:51:25 (0) **    - The Windows CD.
    06692 14:51:25 (0) **    - Another Windows installation using the same version and service pack level of the examined system.
    06693 14:51:25 (0) **    - The original CD or software package installing this WMI provider.
    06694 14:51:25 (0) ** 
    06695 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06696 14:51:25 (0) ** INFO: User Account Control (UAC): ................................................................................... DISABLED.
    06697 14:51:25 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
    06698 14:51:25 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
    06699 14:51:25 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
    06700 14:51:25 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
    06701 14:51:25 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
    06702 14:51:25 (0) ** 
    06703 14:51:25 (0) ** Overall DCOM security status: ....................................................................................... OK.
    06704 14:51:25 (0) ** Overall WMI security status: ........................................................................................ OK.
    06705 14:51:25 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
    06706 14:51:25 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 2.
    06707 14:51:25 (0) ** - ROOT/SUBSCRIPTION, CommandLineEventConsumer.Name="BVTConsumer".
    06708 14:51:25 (0) **   'SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99'
    06709 14:51:25 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
    06710 14:51:25 (0) **   'select * from MSFT_SCMEventLogEvent'
    06711 14:51:25 (0) ** 
    06712 14:51:25 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
    06713 14:51:25 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 3 NAMESPACE(S)!
    06714 14:51:25 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
    06715 14:51:25 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
    06716 14:51:25 (0) ** - ROOT/SERVICEMODEL.
    06717 14:51:25 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
    06718 14:51:25 (0) **    use an encrypted connection by specifying the PACKET PRIVACY authentication level.
    06719 14:51:25 (0) **    (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
    06720 14:51:25 (0) **    i.e. 'WMIC.EXE /NODE:"{ComputerName}" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
    06721 14:51:25 (0) ** 
    06722 14:51:25 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
    06723 14:51:25 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
    06724 14:51:25 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 30 ERROR(S)!
    06725 14:51:25 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06726 14:51:25 (0) **   MOF Registration: ''
    06727 14:51:25 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06728 14:51:25 (0) **   MOF Registration: ''
    06729 14:51:25 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06730 14:51:25 (0) **   MOF Registration: ''
    06731 14:51:25 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06732 14:51:25 (0) **   MOF Registration: ''
    06733 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06734 14:51:25 (0) **   MOF Registration: ''
    06735 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06736 14:51:25 (0) **   MOF Registration: ''
    06737 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06738 14:51:25 (0) **   MOF Registration: ''
    06739 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06740 14:51:25 (0) **   MOF Registration: ''
    06741 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06742 14:51:25 (0) **   MOF Registration: ''
    06743 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06744 14:51:25 (0) **   MOF Registration: ''
    06745 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06746 14:51:25 (0) **   MOF Registration: ''
    06747 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06748 14:51:25 (0) **   MOF Registration: ''
    06749 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06750 14:51:25 (0) **   MOF Registration: ''
    06751 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06752 14:51:25 (0) **   MOF Registration: ''
    06753 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06754 14:51:25 (0) **   MOF Registration: ''
    06755 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06756 14:51:25 (0) **   MOF Registration: ''
    06757 14:51:25 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06758 14:51:25 (0) **   MOF Registration: ''
    06759 14:51:25 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06760 14:51:25 (0) **   MOF Registration: ''
    06761 14:51:25 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06762 14:51:25 (0) **   MOF Registration: ''
    06763 14:51:25 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06764 14:51:25 (0) **   MOF Registration: ''
    06765 14:51:25 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06766 14:51:25 (0) **   MOF Registration: ''
    06767 14:51:25 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06768 14:51:25 (0) **   MOF Registration: ''
    06769 14:51:25 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06770 14:51:25 (0) **   MOF Registration: ''
    06771 14:51:25 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06772 14:51:25 (0) **   MOF Registration: ''
    06773 14:51:25 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06774 14:51:25 (0) **   MOF Registration: ''
    06775 14:51:25 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06776 14:51:25 (0) **   MOF Registration: ''
    06777 14:51:25 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06778 14:51:25 (0) **   MOF Registration: ''
    06779 14:51:25 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06780 14:51:25 (0) **   MOF Registration: ''
    06781 14:51:25 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06782 14:51:25 (0) **   MOF Registration: ''
    06783 14:51:25 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06784 14:51:25 (0) **   MOF Registration: ''
    06785 14:51:25 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
    06786 14:51:25 (0) **    a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
    06787 14:51:25 (0) **    You can refresh the WMI class provider buffer with the following command:
    06788 14:51:25 (0) ** 
    06789 14:51:25 (0) **    i.e. 'WINMGMT.EXE /SYNCPERF'
    06790 14:51:25 (0) ** 
    06791 14:51:25 (0) ** WMI MOF representations: ............................................................................................ OK.
    06792 14:51:25 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
    06793 14:51:25 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
    06794 14:51:25 (2) !! WARNING: WMI EXECQUERY operation errors reported: ................................................................... 2 WARNING(S)!
    06795 14:51:25 (0) ** - Root/CIMV2, 'Select * From Win32_PointingDevice WHERE Status = "OK"' did not return any instance while AT LEAST 1 instance is expected.
    06796 14:51:25 (0) ** - Root/CIMV2, 'Select * From Win32_Keyboard' did not return any instance while AT LEAST 1 instance is expected.
    06797 14:51:25 (0) ** 
    06798 14:51:25 (2) !! WARNING: WMI GET VALUE operation errors reported: ................................................................... 5 WARNING(S)!
    06799 14:51:25 (0) ** - Root, Instance: __EventConsumerProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    06800 14:51:25 (0) ** - Root, Instance: __EventProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    06801 14:51:25 (0) ** - Root, Instance: __EventSinkCacheControl=@, Property: ClearAfter='00000000000015.000000:000' (Expected default='00000000000230.000000:000').
    06802 14:51:25 (0) ** - Root, Instance: __ObjectProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    06803 14:51:25 (0) ** - Root, Instance: __PropertyProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    06804 14:51:25 (0) ** 
    06805 14:51:25 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    06806 14:51:25 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    06807 14:51:25 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    06808 14:51:25 (0) ** WMI static instances retrieved: ..................................................................................... 2072.
    06809 14:51:25 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    06810 14:51:25 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
    06811 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06812 14:51:25 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
    06813 14:51:25 (0) **   DCOM: ............................................................................................................. 0.
    06814 14:51:25 (0) **   WINMGMT: .......................................................................................................... 0.
    06815 14:51:25 (0) **   WMIADAPTER: ....................................................................................................... 0.
    06816 14:51:25 (0) ** 
    06817 14:51:25 (0) ** # of additional Event Log events AFTER WMIDiag execution:
    06818 14:51:25 (0) **   DCOM: ............................................................................................................. 0.
    06819 14:51:25 (0) **   WINMGMT: .......................................................................................................... 0.
    06820 14:51:25 (0) **   WMIADAPTER: ....................................................................................................... 0.
    06821 14:51:25 (0) ** 
    06822 14:51:25 (0) ** 30 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
    06823 14:51:25 (0) ** => This error is typically a WMI error. This WMI error is due to:
    06824 14:51:25 (0) **    - a missing WMI class definition or object.
    06825 14:51:25 (0) **      (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
    06826 14:51:25 (0) **      You can correct the missing class definitions by:
    06827 14:51:25 (0) **      - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
    06828 14:51:25 (0) **      Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
    06829 14:51:25 (0) **            (This list can be built on a similar and working WMI Windows installation)
    06830 14:51:25 (0) **            The following command line must be used:
    06831 14:51:25 (0) **            i.e. 'WMIDiag CorrelateClassAndProvider'
    06832 14:51:25 (0) **      Note: When a WMI performance class is missing, you can manually resynchronize performance counters
    06833 14:51:25 (0) **            with WMI by starting the ADAP process.
    06834 14:51:25 (0) **    - a WMI repository corruption.
    06835 14:51:25 (0) **      In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
    06836 14:51:25 (0) **      to validate the WMI repository operations.
    06837 14:51:25 (0) **    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
    06838 14:51:25 (0) **          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
    06839 14:51:25 (0) **          i.e. 'WMIDiag WriteInRepository=Root'
    06840 14:51:25 (0) **    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
    06841 14:51:25 (0) **      the WMI repository must be reconstructed.
    06842 14:51:25 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
    06843 14:51:25 (0) **          otherwise some applications may fail after the reconstruction.
    06844 14:51:25 (0) **          This can be achieved with the following command:
    06845 14:51:25 (0) **          i.e. 'WMIDiag ShowMOFErrors'
    06846 14:51:25 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
    06847 14:51:25 (0) **          ALL fixes previously mentioned.
    06848 14:51:25 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
    06849 14:51:25 (0) ** 
    06850 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06851 14:51:25 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
    06852 14:51:25 (0) ** INFO: Unexpected registry key value:
    06853 14:51:25 (0) **   - Current:  HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 0
    06854 14:51:25 (0) **   - Expected: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 1
    06855 14:51:25 (0) **     From the command line, the registry configuration can be corrected with the following command:
    06856 14:51:25 (0) **     i.e. 'REG.EXE Add "HKLM\SOFTWARE\Microsoft\WBEM\CIMOM" /v "Logging" /t "REG_SZ" /d "1" /f'
    06857 14:51:25 (0) ** 
    06858 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06859 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06860 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06861 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06862 14:51:25 (0) ** 
    06863 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06864 14:51:25 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
    06865 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06866 14:51:25 (0) ** 
    06867 14:51:25 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\USERS\{Username}\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_2K8R2.SRV.SP1.64_{ComputerName}_2012.07.10_14.40.25.LOG' for details.
    06868 14:51:25 (0) ** 
    06869 14:51:25 (0) ** WMIDiag v2.1 ended on Tuesday, July 10, 2012 at 14:51 (W:103 E:51 S:1).

    Following might help
    A Wmiprvse.exe process crashes in Windows Server 2008 R2 when you use the WMI interface to query the hardware status on a computer that supports the IPMI standard
    http://support.microsoft.com/kb/2280777
    I do not represent the organisation I work for, all the opinions expressed here are my own.
    This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
    I saw this in my googling.  Listed as the cause on the hotfix page is the following: "This
    problem occurs because the Ipmiprv.dll module leads the Wmiprvse.exe process to crash. This behavior depends on certain hardware sensor types when the sensor is enumerated."  The
    faulting module for that hotfix is ipmiprv.dll, and our faulting module is ntdll.dll.  I'm thinking that this hotfix isn't applicable, but I'm open to hearing why I'm incorrect if I am.
    Seth Johnson

  • How to configure SharePoint HNSC with a reverse proxy server so that HNSC Share Point URLs are not exposed to end users.

    Could you please let me know how SharePoint HNSC can be configured with a reverse proxy server so that HNSC Share Point URLs are not exposed to end users.
    In normal path based site collections/web applications, reverse proxy configuration can be done using alternate access mappings with  Public URL = "proxy URL", internal = "HNSC Share Point URL" so that share point sends response back
    to Public URL = "proxy URL".
    In Host Named Site Collections,  alternate access mappings  are not supported. Each HNSC is designed to have only one URL in each zone. Zone is one of the five zones(Default,Intranet,Internet,Custom,Extranet) with each of which only one alternate
    URL is associated.  This is what we are able to get using power shell command "Set-SPSiteUrl", but this will not help us to get the response back to proxy URL after a request sent to share point because we could not find any mechanism in share
    point HNSC to respond  to a different URL(proxy URL). Consequently, Share Point URLs are exposed to  external users.
    Below share point article in MSDN blog is symmetrical to what we are observing with Share Point 2013 and Proxy Server. It mentions that internal HNSC URLs can’t be hidden using any proxy server. If  hiding the internal Share Point URLS is a requirement,
    it suggests to use a web application instead of host named site collections.
    Though I’m also observing the same behavior with Share Point 2013 HNSC, Could you please confirm my understanding is correct.
    http://blogs.msdn.com/b/kaevans/archive/2012/03/27/what-every-sharepoint-admin-needs-to-know-about-host-named-site-collections.aspx
    Excerpt from above article-
    "Host Named Site Collections Only Use One Host Name
    Continuing on the discussion on AAMs and host named site collections, you cannot use multiple host names to address a site collection in SharePoint 2010. Because host-named site collections have a single URL, they do not support alternate access mappings and
    are always considered to be in the Default zone.  This is important if you are using a reverse proxy to provide access to external users. Products like Unified Access Gateway 2010 allow external users to authenticate to your gateway and access a site
    as http://uag.sharepoint.com and forward the call to http://portal.sharepoint.com. Remember that URL rewriting is not permitted. Further, a site collection can only respond to one host name. This means if you are using a reverse proxy, it must forward the
    calls to the same URL.  If your networking team has a policy against exposing internal URLs externally, you must instead use web applications and extend the web application using an alternate access mapping."<u5:p></u5:p>

    Hi Satish,
    You are right that only one URL is allowed for each zone of the host-name site collections in both SharePoint 2010 and SharePoint 2013.
    It is by design that each host-name site collection only support one URL for each zone.
    The article below is about RTM version of SharePoint, and it is the same for SharePoint 2013 with the latest CU.
    https://support.microsoft.com/en-us/kb/2826457
    So to make the URL of HNSC not exposed to external users is not supported, you need to use path-based sites instead.
    Best regards.
    Thanks
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Expose doesn't work anymore. Please help!

    I recently installed the latest software update for my Macbook and just noticed that Expose no longer works. I tried changing the corner that would activate Expose but have had no luck in getting it to work.
    If anyone has any thoughts or suggestions that I could try, they would be most appreciated!
    -Greg
    MacBook   Mac OS X (10.4.7)  

    OK - just tried printing on 10.2.8 and no problem. Was able to get into the Print Center (X.2) and from there the Lexmark configure option worked fine - checked fluid levels, did the alignment, can print in "econo" mode. I notice that X.2 has an application called Print Center while in X.4 this app is called Printer Setup Utility. Are these the same animals or different? The windows on the two are similar but different:
    Both have the heading Printer List
    X.2 Print Center
    Options - Make Default, Add, Delete, Configure (note Configure pulls up the Lexmark Utility application and allows you to check fluids, etc.)
    X.4 Printer Setup Utility
    Options - Make Default, Add, Delete, Utility (same icon as Configure in X.2), Colour Sync, Show Info. Note that clicking on the Utility icon produces a "Lexmark utility unexpectedly quit" message
    Double clicking on the Printer Name on each produces a different result:
    X.2 - brings up the printer status (i.e Job printing) window
    X.4 - brings up the printer status window with options of Utility (clicking on this pulls up the "unexpectedly quit" message) and Supply Levels (clicking on this produces an "information not available" message)
    I'm thinking that the problem might be in the Printer Setup Utility that appears to have changed in X.4???? Thoughts?
    Dave
    iBook   Mac OS X (10.2.x)   eMac OS X (10.4.3)

  • HT4689 With mission control in Mountain Lion, is there a setting that displays a document name when it is selected?

    For example, if I have 4 word documents open, and go to mission control so they are all displayed, can I turn a feature on that displays the document name when my mouse is over each document?
    Like in the picture, if I have my mouse over a document, the name of the document isn't displayed.  Can I change this?

    Hey! 
    I just got a new mac and was trying to figure out the same thing today!! I went from an older version to this 10.9.  I called apple support, the tech had no idea what I was talking about.  I was transferred to a manager who told me that it is not feature available on the new models.  After a 40 minute conversation I was about to let it go and then I saw this post and became determined LOL ... and I figured it out (SMH apple support).  So here is how you do you it:
    system preferences > trackpad > you want to make sure the "App Expose" is checked off > and you're done!!
    I am not able to upload a 2 photos so I will post a second screenshot of what it looks like once the preferences are set.

  • How can i give 2 different names for the same attribute in querypannelVC

    Hi
    I have a View criteria and exposing as a query panel.In the VC, we are using one VO attribute instance twice"FullName".We have a requirement of display 2 different names for this attribute in the query panel Ui.Attached the VC screenshot.
    Ex:Present in the Query panel Ui fields are displaying like
    FullName
    FullName
    Requirement:
    Owner
    Assignee
    Thanks in Advance,
    Naga

    Hi Thanks for the reply..So are you saying like add the same "FullName" attribute twice with different Alias Names(Owner,Assignee) ?But here we are having the FullName as common and depends upon role we are displaying "Owner" or "Assignee".If i create two instances for same attribute will it not be like redundancy ?

  • Field name lengths

    The field name lengths in the Citadel database are approaching 80 characters when Citadel adds the total path to each field. I am saving data from a process running on computer #1 to computer #2. I am using OPC and to select the analog input values require an extremely long length to the field names.
    i.e.
    "\\Dispatchbd1\Freq_Process\FreqOPC.'OPC DAQ Items'.'Analog Input'.'PHS Narrow Freq'" is just one of my field names. When you have 75 values in a database that you want to look at this long name gets discouraging. Any help would be appreciated.

    Hi Wapa,
    You are right the names are a bit long. Citadel stores the absolute names (includes computer and process name), to make sure the names are unique. For example if process1 and process2 have both Pot1 and you are storing the data to the same database, unless you log it with a process name and computer name you would get a conflict - (if there is just Pot1 you would not know from which process).
    So, the computer and process parts are always there. The Item name has to be also included, but you have more choise there. The member ('OPC DAQ Items'.'Analog Input'.''PHS Narrow Freq') can be aliased to anything you want (and is valid). Go to the Edit database - select the item in the second window - select the datatype - type in alias (for example item1) - check the log to
    historical database and hit save (you are going to get a warning - don't worry about it, just make sure the alias (item1) you typed is is not already an existing item - because of the folder structure exposed by DAQ OPC you'll be fine).
    Now instaed of using "\\Dispatchbd1\Freq_Process\FreqOPC.'OPC DAQ Items'.'Analog Input'.'PHS Narrow Freq'" you can go with "\\Dispatchbd1\Freq_Process\FreqOPC.item1" - you can stop loggin the original member.
    If you need to go even shorter, you can create an expression object for every member you want to log and then log the expression. Then you get to something like:
    "\\Dispatchbd1\Freq_Process\Exp1"
    I hope this helps.
    Martin

Maybe you are looking for