locked
Need help - Web Server Role/Feature not installing, Code: 0x800f0922 RRS feed

  • Question

  • Hello,

    This seems to be a recurring problem:

    I'm trying to completely reinstall Web Server Core and Web Server features.

    I attempt to install Wordpress via WPI, which crashes due to needing to install dependencies.

    I then install Web Server Code and Web Server features, via Add Roles and Features in Server Mananger.

    This then gives the error code:

    0x800f0922

    I think I uninstalled everything, is there any chance that the old installations (which are hopefully removed) are conflicting with the new install?

    Anyone have any ideas?

    Septoiz

    Edit: Running a Server 2012 R2 OS as a Virtual Server with vmware, reinstalling the whole server is therefore potentially possible, but is definitely a worst case scenario.
    • Edited by septoiz Wednesday, February 10, 2016 3:04 PM Added OS
    Wednesday, February 10, 2016 3:02 PM

Answers

  • DotNet may be broken.

    https://support.microsoft.com/en-us/kb/2698555

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    • Proposed as answer by Alvwan Wednesday, February 17, 2016 7:29 AM
    • Marked as answer by Amy Wang_ Friday, February 19, 2016 7:18 AM
    Wednesday, February 10, 2016 4:14 PM
  • Hi,

    Here are few troubleshooting tips that you can use to explore a similar deployment issue:

    Get a log with DISM : To get additional information, use the DISM tool and get a clean log.

    • Go to %windir%\logs\DISM, rename the existing DISM.log file o the name of your choice.
    • Open a command prompt and run the following command :
           Dism  /online  /enable-feature /featurename:WebAccess
    • After the command fail, open the new DISM.log file and look for your      error. It may help you understand what is going on.

    Cleanup the database : your component database may be corrupted so this first repair step would be to clean it.

    • Open a command prompt and run the following command :
           Dism  /online  /Cleanup-Image /RestoreHealth
    • The logs will be in the following locations : %windir%\logs\DISM and      %windidr%\logs\cbs
    • Look for any information regarding your problem in the log files.

    Similar case for your reference:

    http://blogs.technet.com/b/dcaro/archive/2012/12/17/installing-remote-destop-web-access-role-on-windows-server-2012.aspx

    Best Regards,

    Alvin Wang


    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 tnmff@microsoft.com.

    • Proposed as answer by Alvwan Wednesday, February 17, 2016 7:29 AM
    • Marked as answer by Amy Wang_ Friday, February 19, 2016 7:18 AM
    Thursday, February 11, 2016 3:43 AM

All replies

  • DotNet may be broken.

    https://support.microsoft.com/en-us/kb/2698555

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    • Proposed as answer by Alvwan Wednesday, February 17, 2016 7:29 AM
    • Marked as answer by Amy Wang_ Friday, February 19, 2016 7:18 AM
    Wednesday, February 10, 2016 4:14 PM
  • Hi,

    Here are few troubleshooting tips that you can use to explore a similar deployment issue:

    Get a log with DISM : To get additional information, use the DISM tool and get a clean log.

    • Go to %windir%\logs\DISM, rename the existing DISM.log file o the name of your choice.
    • Open a command prompt and run the following command :
           Dism  /online  /enable-feature /featurename:WebAccess
    • After the command fail, open the new DISM.log file and look for your      error. It may help you understand what is going on.

    Cleanup the database : your component database may be corrupted so this first repair step would be to clean it.

    • Open a command prompt and run the following command :
           Dism  /online  /Cleanup-Image /RestoreHealth
    • The logs will be in the following locations : %windir%\logs\DISM and      %windidr%\logs\cbs
    • Look for any information regarding your problem in the log files.

    Similar case for your reference:

    http://blogs.technet.com/b/dcaro/archive/2012/12/17/installing-remote-destop-web-access-role-on-windows-server-2012.aspx

    Best Regards,

    Alvin Wang


    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 tnmff@microsoft.com.

    • Proposed as answer by Alvwan Wednesday, February 17, 2016 7:29 AM
    • Marked as answer by Amy Wang_ Friday, February 19, 2016 7:18 AM
    Thursday, February 11, 2016 3:43 AM