Share via

Getting the below error when running the powershell commands remotly with elivated shell permissions

Anonymous
2023-10-16T14:30:31+00:00

We have a Windows 2019 server which have DNS server installed on it. and we run some powershell commands remotly on this server with elivated shell permissions, it was working fine until last week and all of the sudden we are getting the below error.

Task Execution Failed on Attempt 1 Element not found. (Exception from HRESULT: 0x80070490)


1) i ran sfc scan and it did not fixed the issue

2) i restored the server to older version and it did not fix the issue. 

There was no update the server. there was no change in the server when it worked state to not worked state
Windows for business | Windows Server | Performance | Application technologies and compatibility

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Anonymous
    2024-12-21T12:35:55+00:00

    Get-Clipboard : İstenen Pano işlemi başarılı olmadı.

    At C:\Users\Mustafa Kaya\AppData\Local\Temp\zUGcLxHRKqFprby.ps1:54 char:16

    • $clipper = Get-Clipboard 
      
    •            ~~~~~~~~~~~~~ 
      
      • CategoryInfo : NotSpecified: (:) [Get-Clipboard], ExternalException
      • FullyQualifiedErrorId : System.Runtime.InteropServices.ExternalException,Microsoft.PowerShell.Commands.GetClipbo
      ardCommand

    HATASI NEDİR

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-10-19T03:19:17+00:00

    Hello

    Thank you for posting in Microsoft Community forum!

    The error message "Element not found. (Exception from HRESULT: 0x80070490)" is often associated with issues related to COM (Component Object Model) and can be tricky to diagnose. However, one common cause of this error is missing or corrupted COM components or registry entries. Here are steps you can take to address this issue:

    Check COM Components:

    • Open the "Component Services" management console. You can do this by pressing Windows + R, typing dcomcnfg, and hitting Enter.
    • In the Component Services window, expand "Component Services," "Computers," and then "My Computer."
    • Right-click on "DCOM Config" and select "Properties."
    • Go through the list of components and see if any have issues. Pay attention to components that may be related to the tasks you're trying to execute.
    • If you identify any problematic components, try to reconfigure or repair them if possible.

    Registry Check:

    • Some COM components are registered in the Windows Registry. Check for any issues related to these components:
    • Press Windows + R, type regedit, and press Enter.
    • Navigate to HKEY_CLASSES_ROOT\Wow6432Node\CLSID for 32-bit components, or HKEY_CLASSES_ROOT\CLSID for 64-bit components.
    • Check if there are any orphaned or problematic entries related to the COM components. If found, you may need to clean them up.

    Windows Update:

    • Ensure your system is up to date with the latest Windows updates. Sometimes, Microsoft releases updates that address COM-related issues.

    Check PowerShell Execution Policies:

    • Make sure your PowerShell script execution policy is not too restrictive. You can check it by running Get-ExecutionPolicy in PowerShell. If it's set to "Restricted," you might need to change it to "RemoteSigned" or "Unrestricted" using Set-ExecutionPolicy.

    Reinstall Affected Components:

    • If you've identified specific COM components causing the issue, you may need to reinstall them. Consult the documentation or the provider of the components for guidance on how to do this.

    Check Group Policies:

    • Review any Group Policies that might affect the execution of PowerShell scripts or COM components. Ensure there are no policies that restrict or block these actions.

    Best Regards,

    Wesley Li

    1 person found this answer helpful.
    0 comments No comments