none
Error Installing Windows Internal Database RRS feed

  • Question

  •  

    While attempting to install the Windows Internal Database on Server 2008 Standard x64 I recieved the following errors:

     

    Windows Internal Database: Attempt to install Windows Internal Database failed with error code 0x80070667. Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.

     

    Windows System Resource Manager: Installation failed because a required role service or feature could not be installed.

     

    I attempted to install these features from the Server Manager.

     

    - Doug

    Monday, February 11, 2008 9:58 PM

Answers

  • Then I don’t know.  Only reason I mentioned that, is because other customers have download images before and experienced this problem. It seems a troubleshooting issue. Please call Microsoft and team would be able to assist you.

     

     

    Thanks.

    Pooja.

    Thursday, February 14, 2008 6:44 PM

All replies

  • Hi Doug,

     

    You have not mentioned which version of SQL server you are trying to install. If you are installing SQL Server 2005 then install it along with SP2 on Server 2008. You may want to visit link mentioned below -

    http://www.microsoft.com/sql/howtobuy/windowsvistasupport.mspx
    http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2631582&SiteID=17
    http://technet.microsoft.com/en-us/sqlserver/bb426877.aspx

     

    You may also want to take a look at below links which might be helpful for you -

    http://support.microsoft.com/kb/936302

    http://support.microsoft.com/kb/929150/

     

     

    Hope above helps.

     

    Thanks

    Pooja.


    Tuesday, February 12, 2008 7:49 PM
  •  

    I have SQL Server 2005 installed along with SP2, however it is the Windows Internal Database that I'm installing which as far as I know doesn't depend on SQL Server 2005 being present before.

     

    - Doug

    Tuesday, February 12, 2008 8:49 PM
  • Please let me know which version of WS2008 are you using?

     

    Thanks.

    Pooja.

    Wednesday, February 13, 2008 12:24 PM
  •  

    I'm using the 64-bit version of Windows Server 2008 Standard.
    Wednesday, February 13, 2008 6:34 PM
  • And what is the build number you are using? Is it RC0, RC1 or RTM?

     

     

    Thanks.

    Pooja

     

     

     

    Wednesday, February 13, 2008 10:24 PM
  •  

    Windows Server 2008 x64 Standard Edition (RTM)
    Wednesday, February 13, 2008 10:28 PM
  • The possible reason could be that you have corrupted binaries,  you got that way during the download.  Can you use those same binaries on a different server?  If so, does it have the same problems that can confirm if the binaries are corrupted?

     

     

    Thanks.

    Pooja.

    Thursday, February 14, 2008 3:55 PM
  •  

    The binaries are from the RTM DVD image, I'm not sure how they would become corrupted.

     

    - Doug

    Thursday, February 14, 2008 4:18 PM
  • Then I don’t know.  Only reason I mentioned that, is because other customers have download images before and experienced this problem. It seems a troubleshooting issue. Please call Microsoft and team would be able to assist you.

     

     

    Thanks.

    Pooja.

    Thursday, February 14, 2008 6:44 PM
  • I'm going to be installing the server onto another machine today and will see if the same problem occurs.

     

    Thanks for your help though...

     

    - Doug

    Thursday, February 14, 2008 6:58 PM
  •  

    Hey Doug,

     

    Following up with your original installation failure on the Standard Server 2008 RTM build, could you kindly elaborate on the environment of your machine (particularly server) at failure time? By environment I mean, for example, what other roles/features of server you had installed before attempting the installation of Windows Internal Database.

     

    Do mention any other applications installed/running at the time (if you recall ).

     

    Looking forward to following this up.

     

    Thanks,

     

    -Usman

    Friday, February 15, 2008 8:24 PM
  • Okay, the machine is configured as follows:

     

    Microsoft Windows Server 2008 RTM - Standard x64 Edition

    Microsoft Visual Studio 2008 Team Suite

    Microsoft Visual Studio 2008 TFS Client

    Microsoft Office Ultimate 2007

    Microsoft SQL Server 2005 Developer

    Symantec End Point Protection

    VMWare

    WinZip 11.1

    Microsoft Windows SDK 6.0a

    Microsoft Windows SDK 6.1

    Intel Matrix Storage Manager

    Adobe Acrobat Reader

     

    As far as roles / features installed.

     

    Application Server

    Web Server (IIS)

     

    .NET Framework 3.0 Features

    .NET Framework 3.0

    XPS Viewer

    WCF Activation

    HTTP Activation

    Non-HTTP Activation

    Desktop Experiance

    Group Policy Management

    Message Queuing

    Message Queuing Service

    Message Queuing Server

    Remote Server Administration Tools

    Role Administration Tools

    Web Server (IIS) Tools

    Windows PowerShell

    Windows Process Activation Service

    Process Model

    .NET Environment

    Configuration API's

    Windows Server Backup Features

    Windows Server Backup

    Command Line Tools

    Wireless LAN Service

     

    Hardware wise, its a Dell Vostro 1700 notebook with 4Gb of RAM and it is in Workgroup and not Domain configuration.

    Friday, February 15, 2008 9:14 PM
  • Alright Smile, quite detailed! Good!

     

    I'll get back to you after trying a repro of this.

     

    -Usman

     

    Saturday, February 16, 2008 1:16 AM
  • Hello,

     

    Yes I got the same thing, looking through the logs it didn't have access to my user temp directory:

    ocsetup.exe "WSSEE"  /quiet /norestart /x:" /lv* C:\Users\steven gill\AppData\Local\Temp\msi.log

     

    so I ran this in an admin command prompt:

    ocsetup.exe "WSSEE"  /quiet /norestart /x:" /lv* C:\msi.log

     

    then retried installing the FSRM feature and it went through and installed successfully after detecting that WSSEE was already installed.

     

    Hope that helps somebody!

    Sunday, February 24, 2008 6:01 PM
  • Hello Steven,

    Thanks for the post..

    I experienced the same issue. and got it resolved using the command above..

    • Proposed as answer by Alok.m Tuesday, March 6, 2012 5:40 PM
    Tuesday, March 6, 2012 5:39 PM