Installation Error Messages (Windows Embedded Standard 2009)

4/23/2012

The following table shows the error messages you might encounter and the resolutions to correct them when installing Windows Embedded Standard.

Error message Description Resolution

Migration of product from Evaluation to Retail is not supported. Please remove the existing installation to continue.

The attempted migration is not supported.

Remove the Evaluation copy of Windows Embedded Standard.

Migration of product from Retail to Evaluation is not supported. Please remove the existing installation to continue.

The attempted migration is not supported.

Remove the Retail copy of Windows Embedded Standard.

The dialog "Please wait while the Setup Wizard prepares to guide you through the installation. Detecting available SQL servers" stays for more than 5-10 minutes.

The installer attempts to query remote SQL Server(s), and there is a delay in the response from these server(s).

To skip the check, run the following command:

msiexec /I <path-to-WindowsEmbeddedStandard.msi> NOENUMREMOTESQLSERVER=1

Windows Embedded Standard setup requires WindowsEmbeddedStandardR1DatabasePatch.msp be run before WindowsEmbeddedStandard.msi

In a migration scenario, this update is required.

Run Setup.exe to apply the update.

Connection to the SQL Server (server name) failed.

Code: 80004005

Message: Unspecified

Source: Microsoft OLE DB Provider for SQL Server

Description: [DBNETLIB][ConnectionOpen (Connect()).] SQL Server does not exist or access denied.

The selected SQL Server is either not valid or not running. Select a different SQL Server or select none.

If you select the server as none, you will not be able to install the local Windows Embedded Standard database.

Reboot the computer, or manually restart SQL Server Service using one of the following methods:

  • Open Control Panel, click Administrative Tools, and then Services. Locate the instance of SQL server on which the Mantis database exists. Check if this service is running. If not, start this service.
    Bb521687.note(en-US,WinEmbedded.51).gifNote:
     SQL Server instance names are not restricted to MSSQLSERVER. The Mantis database may exist on a SQL server with a different instance name.
  • Confirm that you have installed SQL Server version 2005 or later.

Specified SQL Server cannot be used for Windows Embedded Standard database.

SQL Server: (servername)/(instancename)

The current user does not have permission to create a database on the selected SQL server. Use the SQL database tools to grant the user permission to create a database.

Confirm that your user account has permissions to create a database.

On Windows Vista or later operating systems, run Setup.exe to trigger User Account Control (UAC) prompt.

Specified SQL Server cannot be used for Windows Embedded Standard database.

SQL Server: (local)

The selected SQL Server is not supported. To continue, please select a supported SQL Server. See the Installation Guide for a list of supported SQL Servers.

MS SQL 2000 and Microsoft database engines are not supported in Windows Embedded Standard.

Uninstall MS SQL 2000 and Microsoft database engines, and install MS SQL 2005 or higher versions of database engine.

The current user does not have permission to create a database on the selected SQL server. Use the SQL database tools to grant the user permission to create a database.

Necessary permissions for creating a database are required.

Confirm and appropriately set your user-privileges, or contact your system administrator.

The current user does not have permission to create a database on the selected SQL server. Use the SQL database tools to grant the user permission to create a database or alternatively, launch setup from the DVD to run in privileged mode.

This may happen for Windows Embedded Standard on Windows Vista or later operating systems if you attempt to repair your installation from the Control Panel. The Repair option is available when you select Change under Programs and Features.

On Windows Vista or later operating systems, run Repair using Setup.exe to trigger UAC prompt.

Setup cannot access the SQL server. Setup cannot proceed. - Error Code: -2147467259, Message: Unspecified error, Source: Microsoft OLE DB Provider for SQL Server, Description: [DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access denied.

Setup cannot locate or access the SQL Server.

Confirm that SQL Server is installed and running.

Connection to the SQL server (local) failed. Code: 80004050 Message: Unspecified error, Source: Microsoft OLE DB Provider for SQL Server, Description: [DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access denied.

This can happen on a Windows XP SP2 system when you install the default instance of SQL Server, and install Windows Embedded Standard using the Custom option. The Custom option only displays (local) as a selection for Server Name. MDAC OLEDB uses TCP/IP protocol when you connect through (local). By default, the TCP/IP protocol for MSSQLSERVER is disabled.

To resolve this, do one of the following: 1. Enable TCP/IP protocol in the SQL Server Configuration Manager, or, 2. Install Windows Embedded Standard using the Typical option, and enter the machine name for SQL Server Name.

The installation source for this product is not available. Verify that the source exists and that you can access it.

On Windows Vista or later operating systems, if UAC is turned on, you cannot repair or change the installation from Programs and Features under Control Panel.

On Windows Vista or later operating systems, Repair or Change your installation using Setup.exe from the DVD.

Selected SQL Server is not valid. Please select a different SQL Server or select none.

This can happen if the installed local SQL Server is not running. The option none will only be available in the drop-down list if you have not installed a local database.

Confirm that the SQL Server is installed and running.

Open file - Security Warning Dialog

Do you want to run this file?

Name: …\MUI\LANGCS.EXEPublisher: Microsoft Corporation

Type: Application

From: Z:\...\MUI\LANGCS.EXE

This can happen at the end of Setup execution phase if you run the installation from the network share on a computer that is not joined to the domain.

Run the installation from the DVD or from the domain network share.

Windows Embedded Standard Error: WeUpdate D:\Setup\XPESP3.EXE failed. Return value = 0x40. Check the log file C:\%TEMP%\WindowsEmbeddedStandard_WEUpdate.log.

The WindowsEmbeddedStandard_WEUpdate.log file contains the following:

Windows XP Embedded Service Pack 3 Installer

Cannot connect to the database - please check the database.

Setup cannot continue.

No objects or files were imported to the database (local).

WEUpdate Exiting with return code: 64

**** End Of Run ****

This can happen during the migration. Windows Embedded Standard runs WeUpdates in sequential order. MantisSQLDB database has the option AUTO_CLOSE = True. Whenever Windows Embedded Standard runs, the WeUpdate SQL engine opens the database MantisSQLDB, and closes it at the end. It can take 5-10 minutes to start the database after XPEFP2007.exe.

Wait for 5-10 minutes and click Retry to run WeUpdate again.

Warning 25101. Performing this action will delete all Windows Embedded Standard custom settings. If the component database is installed on your local machine, it is recommended that you make a backup since all custom components will be deleted.

This is an informational message.

Back up your component database and custom settings.

PIDKEY is not specified.

When you run the installation using reduced UI mode, you must provide the PIDKEY property. For additional information on User Interface Levels, refer to this Microsoft Web site.

Add PIDKEY=<product code> to the command line.

PIDKEY is not valid for the product.

When you run the installation using reduced UI mode, you must provide the PIDKEY property.

Check the sticker or contact the retailer for the valid product key.

Failed to connect to SQL database. (-2147467259 master)

The local database was installed but SQL Server was either uninstalled or is not running during the uninstallation.

Do one of the following:

1. Run the following command:

msiexec /x {B4222DEE-71BD-11DC-8BA7-C1C855D89593} SKIPUNINSTALLSQLDATA=1

2. Install/start SQL Server and manually drop MantisSQLDB or MantisSQLDBEval database after the uninstallation.

See Also

Other Resources

Troubleshooting the Installation