Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <ul> <li><p>According to the <a href="http://technet.microsoft.com/en-us/library/ee692772.aspx" rel="noreferrer">WMI FAQ</a> on TechNet, the 0x80070005 error indicates a DCOM issue:</p> <blockquote> <p><strong>0x80070005 (DCOM ACCESS_DENIED)</strong><br> This error occurs when the connected user is not recognized or is restricted in some fashion by the remote server (for example, the user might be locked out). This happens most often when accounts are in different domains. Recent changes to WMI security can also cause this error to occur:</p> <ul> <li><p>Blank passwords, formerly permitted, are not allowed in Windows XP and Windows Server 2003.</p></li> <li><p>WMI does not allow asynchronous callbacks to a Windows 98 client. A call like <strong>SWbemServices.ExecNotificationQueryAsync</strong> from a Windows 98 computer to a Windows XP computer will result in an Access Denied error returned to the Windows 98 machine.</p></li> <li><p>The DCOM configuration access setting might have been changed. </p></li> <li><p>If the target computer is running Windows XP, the Forceguest value under the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa might be set to force the Guest account off (value is zero).</p></li> </ul> </blockquote> <p><em>(Although Windows XP is mentioned, this may be applied to Windows 7 as well.)</em><br> <br/></p></li> <li><p>The 0x800706BA error, in its rurn, indicates a firewall issue:</p> <blockquote> <p><strong>0x800706xx (DCOM RPC error)</strong><br> This often occurs when a firewall is configured on the remote computer. You will need to open the appropriate ports on the firewall to permit remote administration using DCOM.</p> </blockquote> <p>Try enabling the <em>Remote administration</em> exception in Windows Firewall on the remote computer and see if it helps. To do this from the command line, run the following command in the elevated command prompt:</p> <pre><code>netsh advfirewall firewall set rule group="remote admin" new enable=yes </code></pre> <p><br/> You can also find the DCOM, UAC, Windows Firewall and other settings required for remote WMI access in the <a href="http://msdn.microsoft.com/en-us/library/aa822854.aspx" rel="noreferrer">Connecting to WMI Remotely Starting with Windows Vista</a> article on MSDN.<br> <br/></p></li> <li><p>Also, since <em>Samuel</em> is a nondomain account, you need to grant this account DCOM <em>Remote Access</em>, <em>Remote Launch</em> and <em>Remote Activation</em> permissions on the remote computer as described <a href="http://msdn.microsoft.com/en-us/library/aa393266.aspx#setting_dcom_security_to_allow_a_user_to_access_a_computer_remotely" rel="noreferrer">here</a>.</p></li> </ul>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload