Showing posts with label express. Show all posts
Showing posts with label express. Show all posts

Monday, March 26, 2012

Feedback Requested - What Content Do You Want to see for SQL Server Express?

We’re in the process of assessing the content that exists to help people learn and use SQL Server Express. This includes demos, tutorials, whitepapers, Webcasts, Starter Kits, and any other type of content you could imagine. So this is a great chance to TELL US WHAT YOU WANT! We’ll integrate your feedback and make sure that we try and address the most requested areas of content. Please be as specific as you can.

Hi Mark,

I would like to have a demo that shows me how make a diagram from that data in a SQL Server table.

Greetings from Germany,

VBFan

|||I think a crash course in SQL with examples would be great. Also a quick overview of database design and normalization theory could help a beginner get started on the right track.|||I'm looking for an app that will track all computers in my institution. It will need to track them by company property number, and also contain computer name, MAC Address, special software, sensitive functions, etc. I will need to be able to create reports from this data.|||

For very new users some sort of hand-holding for the early stages would be useful. Once you've installed SQL Server Express, it runs but there's no front end and it's not at all obvious how you talk to the beast if your only experience of databases is Access or similar. This is made slightly more difficult in the case of SQL Server Express because BOL tells you that the command sqlcmd will connect you, but in fact it won't -- you need to use sqlcmd -S .\sqlexpress if you accepted the default installation (which is what a raw newbie is going to do).

I think it'd be nice to have something that told you exactly how to create a database (with, say, just two related tables), add data to it, query it, delete data, and then delete the whole database. The database doesn't have to be at all useful: the problem for newbies is finding out how to make things happen and then check that those things really did happen.

Also, something that took you through how the roles work, so you can make sure you're the dbadmin on your database, and get a grasp of how to set up users who're less privileged.

Oh, and maybe something about how to avoid getting log files that seem to get bigger and bigger...

|||

M M Mason wrote:

For very new users some sort of hand-holding for the early stages would be useful. Once you've installed SQL Server Express, it runs but there's no front end and it's not at all obvious how you talk to the beast if your only experience of databases is Access or similar. This is made slightly more difficult in the case of SQL Server Express because BOL tells you that the command sqlcmd will connect you, but in fact it won't -- you need to use sqlcmd -S .\sqlexpress if you accepted the default installation (which is what a raw newbie is going to do).

You can use SQL Management Studio Express for GUI based server management.

|||

Mark,

I am a fresh newbie with hardly any comprehension towards setting up and congifuring SQL Server 2005 express edition and looking through these forums, all I really see are advanced topics and out-of-my-league for now sort of information. I need to know how to set up and configure a SQL Database. I'm not even sure if I have one, and if it doesn't come with SQL Server xpress edition then I doubt I do. But as of now, I'm lost from the very start. I'm a quick learner though, so with this information for setting up and configuring a database I might could pick up on SQL's logic and get a deeper understanding of its programming.

Hope you respond and if not, HOPE SOMEONE DOES!

Thanks,

Michael.

Feedback Requested - What Content Do You Want to see for SQL Server Express?

We’re in the process of assessing the content that exists to help people learn and use SQL Server Express. This includes demos, tutorials, whitepapers, Webcasts, Starter Kits, and any other type of content you could imagine. So this is a great chance to TELL US WHAT YOU WANT! We’ll integrate your feedback and make sure that we try and address the most requested areas of content. Please be as specific as you can.

Hi Mark,

I would like to have a demo that shows me how make a diagram from that data in a SQL Server table.

Greetings from Germany,

VBFan

|||I think a crash course in SQL with examples would be great. Also a quick overview of database design and normalization theory could help a beginner get started on the right track.|||I'm looking for an app that will track all computers in my institution. It will need to track them by company property number, and also contain computer name, MAC Address, special software, sensitive functions, etc. I will need to be able to create reports from this data.|||

For very new users some sort of hand-holding for the early stages would be useful. Once you've installed SQL Server Express, it runs but there's no front end and it's not at all obvious how you talk to the beast if your only experience of databases is Access or similar. This is made slightly more difficult in the case of SQL Server Express because BOL tells you that the command sqlcmd will connect you, but in fact it won't -- you need to use sqlcmd -S .\sqlexpress if you accepted the default installation (which is what a raw newbie is going to do).

I think it'd be nice to have something that told you exactly how to create a database (with, say, just two related tables), add data to it, query it, delete data, and then delete the whole database. The database doesn't have to be at all useful: the problem for newbies is finding out how to make things happen and then check that those things really did happen.

Also, something that took you through how the roles work, so you can make sure you're the dbadmin on your database, and get a grasp of how to set up users who're less privileged.

Oh, and maybe something about how to avoid getting log files that seem to get bigger and bigger...

|||

M M Mason wrote:

For very new users some sort of hand-holding for the early stages would be useful. Once you've installed SQL Server Express, it runs but there's no front end and it's not at all obvious how you talk to the beast if your only experience of databases is Access or similar. This is made slightly more difficult in the case of SQL Server Express because BOL tells you that the command sqlcmd will connect you, but in fact it won't -- you need to use sqlcmd -S .\sqlexpress if you accepted the default installation (which is what a raw newbie is going to do).

You can use SQL Management Studio Express for GUI based server management.

|||

Mark,

I am a fresh newbie with hardly any comprehension towards setting up and congifuring SQL Server 2005 express edition and looking through these forums, all I really see are advanced topics and out-of-my-league for now sort of information. I need to know how to set up and configure a SQL Database. I'm not even sure if I have one, and if it doesn't come with SQL Server xpress edition then I doubt I do. But as of now, I'm lost from the very start. I'm a quick learner though, so with this information for setting up and configuring a database I might could pick up on SQL's logic and get a deeper understanding of its programming.

Hope you respond and if not, HOPE SOMEONE DOES!

Thanks,

Michael.

Friday, March 23, 2012

Feedback Requested - What Content Do You Want to see for SQL Server Express?

We’re in the process of assessing the content that exists to help people learn and use SQL Server Express. This includes demos, tutorials, whitepapers, Webcasts, Starter Kits, and any other type of content you could imagine. So this is a great chance to TELL US WHAT YOU WANT! We’ll integrate your feedback and make sure that we try and address the most requested areas of content. Please be as specific as you can.

Hi Mark,

I would like to have a demo that shows me how make a diagram from that data in a SQL Server table.

Greetings from Germany,

VBFan

|||I think a crash course in SQL with examples would be great. Also a quick overview of database design and normalization theory could help a beginner get started on the right track.|||I'm looking for an app that will track all computers in my institution. It will need to track them by company property number, and also contain computer name, MAC Address, special software, sensitive functions, etc. I will need to be able to create reports from this data.|||

For very new users some sort of hand-holding for the early stages would be useful. Once you've installed SQL Server Express, it runs but there's no front end and it's not at all obvious how you talk to the beast if your only experience of databases is Access or similar. This is made slightly more difficult in the case of SQL Server Express because BOL tells you that the command sqlcmd will connect you, but in fact it won't -- you need to use sqlcmd -S .\sqlexpress if you accepted the default installation (which is what a raw newbie is going to do).

I think it'd be nice to have something that told you exactly how to create a database (with, say, just two related tables), add data to it, query it, delete data, and then delete the whole database. The database doesn't have to be at all useful: the problem for newbies is finding out how to make things happen and then check that those things really did happen.

Also, something that took you through how the roles work, so you can make sure you're the dbadmin on your database, and get a grasp of how to set up users who're less privileged.

Oh, and maybe something about how to avoid getting log files that seem to get bigger and bigger...

|||

M M Mason wrote:

For very new users some sort of hand-holding for the early stages would be useful. Once you've installed SQL Server Express, it runs but there's no front end and it's not at all obvious how you talk to the beast if your only experience of databases is Access or similar. This is made slightly more difficult in the case of SQL Server Express because BOL tells you that the command sqlcmd will connect you, but in fact it won't -- you need to use sqlcmd -S .\sqlexpress if you accepted the default installation (which is what a raw newbie is going to do).

You can use SQL Management Studio Express for GUI based server management.

|||

Mark,

I am a fresh newbie with hardly any comprehension towards setting up and congifuring SQL Server 2005 express edition and looking through these forums, all I really see are advanced topics and out-of-my-league for now sort of information. I need to know how to set up and configure a SQL Database. I'm not even sure if I have one, and if it doesn't come with SQL Server xpress edition then I doubt I do. But as of now, I'm lost from the very start. I'm a quick learner though, so with this information for setting up and configuring a database I might could pick up on SQL's logic and get a deeper understanding of its programming.

Hope you respond and if not, HOPE SOMEONE DOES!

Thanks,

Michael.

Wednesday, March 21, 2012

Faulty insert into sql express database

Hello All,

I have an InfoPath form that submits data to a .NET webservice. The webservice parses the infopath form and inserts the data into a database. The database is SQL Server EXPRESS.

I have however run into some problems. The InfoPath form is within SharePoint and I noticed that when I submit the data, it only shows up in the database as a new record 9 out of 10 times. That is for every 10 submissions of the form, there are only about 9 new records in the database. The ID field (an autoincrement field) also skips a number indicating the the transaction may have failed.

However, when I test the form on my local PC, it inserts a new record for every submission.

The webservice and database are on a remote server not my local.

Does anyone have any ideas? Could it be a deficiency of SQL Server Express?

Any ideas, answers or suggestions would be much appreciated.

Hi Hugo,

I would suggest looking at the log files on the remote server where SQL Express is installed to see if there is any information about the failure there. I doubt any failure is the sole responsibility of SQL Express, it is probably a combination of issues from many sources.

Mike

Monday, March 19, 2012

FAT32->NTFS (after SQL Server 2005 Express installation)

I have FAT32 system on my machine and SQL Server 2005 Express installed on it.

Is there will be any problem in SQL Server 2005 Express (in terms of server machine and client machine) if I change my FAT system from FAT32 to NTFS ?

Thanks

Typically you have to format your drive to switch file systems. You'd have to re-install all your software after this, including SQL Express. If you have user databases, you'll need to save copies of them somewhere before formating your disk. Once you've got the system switched over to NTSF, SQL Express will work fine.

If you're using a third party tool to switch file systems without formating, I can't make any claims as to what will happen with SQL Express as we don't test that.

Mike

|||

Thanks Mike.

For unexpacted I should go through Format HDD (or partiation) as NTFS system -way.

Friday, February 24, 2012

Failure to install SQL Express SP2 on Vista Home Premium

Hi,

I have been trying to install SQL Express SP2 (SQLEXPR32.exe) on a Window Vista Home Premium for past 2 days . After failing I tried installing SQLEXPR_ADV. (Maybe I have a corrupted download, desperate enough to try anything.). However it keeps showing the following error:

SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.

I have search through the forums. One of the possibilities is due to a WMI repository corruption. Tried fixing it, but the problem still persists. (Maybe I am doing it the wrong way , I have downloaded the WMIDiag scripts, not too sure if i ran it correctly).

Below is the installation summary:


Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Home Edition (Build 6000)
Time : Thu Mar 15 02:13:51 2007

ATLANTIS : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
Machine : ATLANTIS
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_ATLANTIS_SQLSupport_1.log
--
Machine : ATLANTIS
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_ATLANTIS_SQLNCLI_1.log
--
Machine : ATLANTIS
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_ATLANTIS_SqlWriter_1.log
--
Machine : ATLANTIS
Product : SQL Server Database Services
Error : SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
--
Machine : ATLANTIS
Product : Microsoft SQL Server 2005
Product Version : 9.2.3042.00
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_ATLANTIS_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
Error Number : 29513
--

What are the other possibilities and fixes? Please help.

Thanks a million.

This is a problem with WMI, either the repository is messed up or WMI is not correctly registered. You can find a post on how to repair WMI here and a blog posting about manually installing sqlmgmproviderxpsp2up.mof here.

Mike

|||

Hi,

Thanks for the feedback. I have tried both methods.

Initially, it keep on showing "Access is Denied" and missing file command whenever I go to command prompt and use the "mofcomp" command.

However thanks to your advice, I realised the problem is due to WMI corruption or a missing sqlmgmproviderxp2up.mof file.

Hence I copied the sqlmgmproviderxp2up.mof file from my WindowXp laptop to my Vista Desktop, and then I ran the "mofcomp" command. And it works

Thanks again.

|||

hello, i'm still having the same issue....i try on install sql express edition on windows vista home premium edition but get the following error any suggestions...

Failure to install SQL Express SP2 on Vista Home Premium

Hi,

I have been trying to install SQL Express SP2 (SQLEXPR32.exe) on a Window Vista Home Premium for past 2 days . After failing I tried installing SQLEXPR_ADV. (Maybe I have a corrupted download, desperate enough to try anything.). However it keeps showing the following error:

SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.

I have search through the forums. One of the possibilities is due to a WMI repository corruption. Tried fixing it, but the problem still persists. (Maybe I am doing it the wrong way , I have downloaded the WMIDiag scripts, not too sure if i ran it correctly).

Below is the installation summary:


Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Home Edition (Build 6000)
Time : Thu Mar 15 02:13:51 2007

ATLANTIS : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
Machine : ATLANTIS
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_ATLANTIS_SQLSupport_1.log
--
Machine : ATLANTIS
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_ATLANTIS_SQLNCLI_1.log
--
Machine : ATLANTIS
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_ATLANTIS_SqlWriter_1.log
--
Machine : ATLANTIS
Product : SQL Server Database Services
Error : SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
--
Machine : ATLANTIS
Product : Microsoft SQL Server 2005
Product Version : 9.2.3042.00
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_ATLANTIS_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
Error Number : 29513
--

What are the other possibilities and fixes? Please help.

Thanks a million.

This is a problem with WMI, either the repository is messed up or WMI is not correctly registered. You can find a post on how to repair WMI here and a blog posting about manually installing sqlmgmproviderxpsp2up.mof here.

Mike

|||

Hi,

Thanks for the feedback. I have tried both methods.

Initially, it keep on showing "Access is Denied" and missing file command whenever I go to command prompt and use the "mofcomp" command.

However thanks to your advice, I realised the problem is due to WMI corruption or a missing sqlmgmproviderxp2up.mof file.

Hence I copied the sqlmgmproviderxp2up.mof file from my WindowXp laptop to my Vista Desktop, and then I ran the "mofcomp" command. And it works

Thanks again.

|||

hello, i'm still having the same issue....i try on install sql express edition on windows vista home premium edition but get the following error any suggestions...

failure to install SQL Agent for SQL Express

I just tried to install the file:

D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe SQLAgent.exe by running it from a command prompt.

and got an error that the system could not find the file or one of its components. It is a farily new install. I do not think I've lost any files any time.

What is the problem?

Thanks.

SQL Express does not include SQL Agent, you need to purchase at least SQL Server Workgroup to get that component.

Mike

Failure to authendicate domain/users

I have several access databases in mind to migrate to SQL server. I installed MS SQL 2005 Express on my machine. I will have procedures to run with authorizations beyond that of a common user, such as database administrative work where server agent is not available, I may rely on users' log-on prompt to do some maintenance work. However, I cannot get the EXEC AS 'Domain\User' to work. The procedures can be created OK. But whenever they are called, the following message shows up:

Msg 15404, Level 16, State 19, Procedure XXX, Line 0
Could not obtain information about Windows NT group/user 'Domain\User', error code 0xea.

I tried to tweak with the account under which the server service is running. There are three options under built-in account: Local system, Local service, and Network Service. My understanding is that Network Service will use the log-on of the current user of the computer. I have admin right of the computer. None of the three options work. Additionally, when I specify an account (my own account), it's the same thing.

The procedure xp_logininfo always fails when I query a specific domain\user.

The ADHelper is configured to run manually.

I could not think of other ways to get a possible solution. Any help is much appreciated.

hi,

try having a look at http://support.microsoft.com/kb/834124/en-us

regards

|||

Hi, there,

I did several times. The problem is that the article does not contain an explanation of state 19. It has explanations for state 21 and above. Do you have any idea what state 19 relates to?

Thanks,

Failure setting security rights on user account SQLServer2005BrowserUser${computerName}

I'm trying to install SQL Server 2005 Express on a Windows 2000 server, but I'm getting the following error message:

"Failure setting security rights on user account SQLServer2005BrowserUser${computerName}"

Can anyone help me please?

Help!! Need to get the sql server installed so I can demo to my client!

Sunday, February 19, 2012

Failure installing SQL Server Express on a Pentium M device

I am currently trying to track down why one of our users is getting an error attempting to install SQL Server Express on their machine.

The symptoms are that SQL Server Express warns about the minimum hardware requirement not being met, the installation proceeds, but is not able to start the SQL Server service, and fails with the following error in the SQLSetupXXXX_MACHINENAME_Core(local).log file.

Error: Action "ReportChainingResults" threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 1067
Error Code: 0x8007042b (1067)
Windows Error Text: The process terminated unexpectedly.

Source File Name: sqlchaining\sqlchainingactions.cpp
Compiler Timestamp: Thu Sep 1 22:23:05 2005
Function Name: sqls::ReportChainingResults::perform
Source Line Number: 3097

From all the information I can gather, this error occurs when the processor does NOT support cache prefetching, such as a Pentium II or a dubious Pentium III compatible CPU. I would have thought that Pentium M CPU's would all support cache prefetching, I am developing on a Pentium M CPU myself with NO dramas.

The CPU we are having problems with is a low-end one, Pentium M 1.4GHz, and it is an Advent laptop. Does anyone know why we would be seeing this error on this machine? Is there a way of turning cache prefetching off say in the BIOS, and would a non-technical user be likely to do that (say for preserving battery life or something like that)? Or is there another reason why SQl Server is not installing?

Any help would be appreciated.

Thanks.

Interesting thing happened today with respects to this problem.

We were originally starting an install of SQL Server Express as a pre-requisite to an InstallShield installer that installs our main application. This works fine on all the machines we've tested on.

Today I was able to successfully step our client (the one with the Pentium M on an Advent Laptop mentioned in the previous post), through downloading the SQL Express installer from the MS website, and then installing it manually (creating our specific instance, and using our particular settings etc...), and this worked fine. The user was then able to install our main application and run it successfully.

I don't understand why we got the above error (which from all I can tell is to do with cache pre-fetching), when installing it from our installer, but was able to install successfully by downloading it from MS.

Any thoughts?

|||

The core log file is really just a log of the master setup and doesn't contain specific details about why a sub-product failed. If you see an error again, you should look at the file %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\Log\summary.txt. It should give a quick summary of the install and be able to point you to the detailed log file for further information. If you then open the detailed log file, typically you can find the error by searching for the string "value 3" and then examining the 20 or so lines above and below the location that you found. Sometimes it will be an error executing a script or launching SQL Server, so you might also want to look at the ERRORLOG in %ProgramFiles%\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG. (MSSQL.1 might actually have some other number on the end, it depends on how many instances of SQL you have installed).

-Jeffrey.

|||

Thanks for the information Jeffrey, I'll go back and look through all the log files.

Cheers.

|||Scott,

Am I to understand from your post that you found a way to install SQL Express 2005 on a machine that does not support certain PIII features? I am desperately hoping to get it running on a Pentium II machine.

Thanks,

Zach First
|||

No Zach, the Pentium M is a Pentium 4 based processor, which is why I was so dismayed that I was getting the same error messages as we had seen when tracking down another clients install problem which ended up being a Pentium III compatibility issue. What Jeffrey was telling me is that I just wasn't looking at the error logs in enough detail. To be honest I still haven't found the reason why the first few attempts to install SQL Express on a pentium M machine didn't work, and with limited time and resources have moved onto other issues.

I would suggest that you give up any hope of trying to get SQL Express (or any SKU of SQL Server 2005) running on a pentium II device, The minimum hardware requirement is a pentium III for a number of reasons, one of which is cache prefetching, and without the instruction set to support it SQL Server 2005 WILL NOT RUN.

Sorry for the bad news.

Failure installing SQL Server 2005 SP 1

Windows XP Pro
SQL Server 2005 Express
SQL Server 2005 Standard

I installed the service pack for SQL Server Express first.
Then I tried to install the service pack for SQL Server. I got the error message, "A recently applied update, KB913090, failed to install.", while it was upgrading the Setup Support Files.

Jonathan Allen

Log follows...

04/22/2006 10:52:34.781 ================================================================================
04/22/2006 10:52:34.875 Hotfix package launched
04/22/2006 10:53:47.546 Attempting to install instance: SQL Server Native Client
04/22/2006 10:53:47.578 Attempting to install target: RADICALJAY
04/22/2006 10:53:47.593 Attempting to install file: sqlncli.msi
04/22/2006 10:53:47.687 Attempting to install file: \\RADICALJAY\c$\b1f5502657526de4ed0c\HotFixSqlncli\Files\sqlncli.msi
04/22/2006 10:53:47.687 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
04/22/2006 10:53:47.703 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
04/22/2006 10:53:47.718 Failed to read registry key: Debug
04/22/2006 10:53:49.578 MSP returned 0: The action completed successfully.
04/22/2006 10:53:49.765 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
04/22/2006 10:53:49.781 Failed to read registry key: Debug
04/22/2006 10:53:49.781 Successfully installed file: \\RADICALJAY\c$\b1f5502657526de4ed0c\HotFixSqlncli\Files\sqlncli.msi
04/22/2006 10:53:49.796 Successfully installed target: RADICALJAY
04/22/2006 10:53:49.812 Successfully installed instance: SQL Server Native Client
04/22/2006 10:53:49.828
04/22/2006 10:53:49.828 Product Status Summary:
04/22/2006 10:53:49.843 Product: SQL Server Native Client
04/22/2006 10:53:49.859 SQL Server Native Client (RTM ) - Success
04/22/2006 10:53:49.859
04/22/2006 10:53:49.875 Product: Setup Support Files
04/22/2006 10:53:49.890 Setup Support Files (RTM ) - Not Applied
04/22/2006 10:53:49.890
04/22/2006 10:53:49.906 Product: Database Services
04/22/2006 10:53:49.921 Database Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:49.937 Analysis Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:49.937 Reporting Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:49.953
04/22/2006 10:53:49.968 Product: Database Services
04/22/2006 10:53:49.968 Database Services (SP1 2047 ENU) - NA
04/22/2006 10:53:49.984 Details: Instances of SQL Server Express cannot be updated by using this Service Pack installer. To update instances of SQL Server Express, use the SQL Server Express Service Pack installer.
04/22/2006 10:53:50.000
04/22/2006 10:53:50.015 Product: Notification Services
04/22/2006 10:53:50.015 Notification Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:50.031
04/22/2006 10:53:50.046 Product: Integration Services
04/22/2006 10:53:50.046 Integration Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:50.062
04/22/2006 10:53:50.078 Product: Client Components
04/22/2006 10:53:50.093 Client Components (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:50.093
04/22/2006 10:53:50.109 Product: MSXML 6.0 Parser
04/22/2006 10:53:50.125 MSXML 6.0 Parser (RTM ) - Not Applied
04/22/2006 10:53:50.125
04/22/2006 10:53:50.140 Product: SQLXML4
04/22/2006 10:53:50.156 SQLXML4 (RTM ) - Not Applied
04/22/2006 10:53:50.171
04/22/2006 10:53:50.171 Product: Backward Compatibility
04/22/2006 10:53:50.187 Backward Compatibility (RTM ) - Not Applied
04/22/2006 10:53:50.203
04/22/2006 10:53:50.203 Product: Microsoft SQL Server VSS Writer
04/22/2006 10:53:50.218 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
04/22/2006 10:53:50.234

This appears to be the log from trying to apply SP1 to your Express instance.

04/22/2006 10:53:49.968 Database Services (SP1 2047 ENU) - NA
04/22/2006 10:53:49.984 Details: Instances of SQL Server Express cannot be updated by using this Service Pack installer. To update instances of SQL Server Express, use the SQL Server Express Service Pack installer.

Can you share out the msp log from the second attempt? The logs are in the %windir%\hotfix folder. If you do a search for "return value 3", that may lead you to the failed component log.

Thanks,
Samuel Lester (MSFT)

|||

This is the new log file from the Service Pack GUI...

04/23/2006 23:12:21.656 ================================================================================
04/23/2006 23:12:21.671 Hotfix package launched
04/23/2006 23:13:02.750 Attempting to install instance: SQL Server Native Client
04/23/2006 23:13:02.796 Attempting to install target: RADICALJAY
04/23/2006 23:13:02.812 Attempting to install file: sqlncli.msi
04/23/2006 23:13:03.031 Attempting to install file: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlncli\Files\sqlncli.msi
04/23/2006 23:13:03.031 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
04/23/2006 23:13:03.046 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
04/23/2006 23:13:03.062 Failed to read registry key: Debug
04/23/2006 23:13:05.468 MSP returned 0: The action completed successfully.
04/23/2006 23:13:05.656 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
04/23/2006 23:13:05.687 Failed to read registry key: Debug
04/23/2006 23:13:05.703 Successfully installed file: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlncli\Files\sqlncli.msi
04/23/2006 23:13:05.718 Successfully installed target: RADICALJAY
04/23/2006 23:13:05.718 Successfully installed instance: SQL Server Native Client
04/23/2006 23:13:05.734
04/23/2006 23:13:05.750 Product Status Summary:
04/23/2006 23:13:05.750 Product: SQL Server Native Client
04/23/2006 23:13:05.765 SQL Server Native Client (RTM ) - Success
04/23/2006 23:13:05.781
04/23/2006 23:13:05.796 Product: Setup Support Files
04/23/2006 23:13:05.796 Setup Support Files (RTM ) - Not Applied
04/23/2006 23:13:05.812
04/23/2006 23:13:05.828 Product: Database Services
04/23/2006 23:13:05.828 Database Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.843 Analysis Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.859 Reporting Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.875
04/23/2006 23:13:05.875 Product: Database Services
04/23/2006 23:13:05.890 Database Services (SP1 2047 ENU) - NA
04/23/2006 23:13:05.906 Details: Instances of SQL Server Express cannot be updated by using this Service Pack installer. To update instances of SQL Server Express, use the SQL Server Express Service Pack installer.
04/23/2006 23:13:05.906
04/23/2006 23:13:05.921 Product: Notification Services
04/23/2006 23:13:05.937 Notification Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.953
04/23/2006 23:13:05.953 Product: Integration Services
04/23/2006 23:13:05.968 Integration Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.984
04/23/2006 23:13:05.984 Product: Client Components
04/23/2006 23:13:06.000 Client Components (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:06.031
04/23/2006 23:13:06.046 Product: MSXML 6.0 Parser
04/23/2006 23:13:06.046 MSXML 6.0 Parser (RTM ) - Not Applied
04/23/2006 23:13:06.062
04/23/2006 23:13:06.078 Product: SQLXML4
04/23/2006 23:13:06.078 SQLXML4 (RTM ) - Not Applied
04/23/2006 23:13:06.093
04/23/2006 23:13:06.109 Product: Backward Compatibility
04/23/2006 23:13:06.109 Backward Compatibility (RTM ) - Not Applied
04/23/2006 23:13:06.125
04/23/2006 23:13:06.140 Product: Microsoft SQL Server VSS Writer
04/23/2006 23:13:06.156 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
04/23/2006 23:13:06.156

I didn't find "return value 3", but this was interesting...

"C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_SqlSupport.msp.log"

=== Verbose logging started: 4/23/2006 23:13:06 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (30:E8) [23:13:06:375]: Resetting cached policy values
MSI (c) (30:E8) [23:13:06:375]: Machine policy value 'Debug' is 0
MSI (c) (30:E8) [23:13:06:375]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (c) (30:E8) [23:13:06:375]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (30:E8) [23:13:06:375]: Grabbed execution mutex.
MSI (c) (30:E8) [23:13:06:375]: Cloaking enabled.
MSI (c) (30:E8) [23:13:06:375]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (30:E8) [23:13:06:390]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (18:88) [23:13:06:390]: Grabbed execution mutex.
MSI (s) (18:9C) [23:13:06:390]: Resetting cached policy values
MSI (s) (18:9C) [23:13:06:390]: Machine policy value 'Debug' is 0
MSI (s) (18:9C) [23:13:06:390]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (s) (18:9C) [23:13:06:390]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (18:9C) [23:13:06:390]: End dialog not enabled
MSI (s) (18:9C) [23:13:06:390]: Original package ==> c:\WINDOWS\Installer\2b422ff9.msi
MSI (s) (18:9C) [23:13:06:390]: Package we're running from ==> c:\WINDOWS\Installer\2b422ff9.msi
MSI (s) (18:9C) [23:13:06:390]: APPCOMPAT: looking for appcompat database entry with ProductCode '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'.
MSI (s) (18:9C) [23:13:06:390]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (18:9C) [23:13:06:390]: MSCOREE not loaded loading copy from system32
MSI (s) (18:9C) [23:13:06:500]: File will have security applied from OpCode.
MSI (s) (18:9C) [23:13:06:593]: Original patch ==> \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp
MSI (s) (18:9C) [23:13:06:593]: Patch we're running from ==> C:\WINDOWS\Installer\7d5500e.msp
MSI (s) (18:9C) [23:13:06:593]: SOFTWARE RESTRICTION POLICY: Verifying patch --> '\\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp' against software restriction policy
MSI (s) (18:9C) [23:13:06:593]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (18:9C) [23:13:06:593]: SOFTWARE RESTRICTION POLICY: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp is not digitally signed
MSI (s) (18:9C) [23:13:06:609]: SOFTWARE RESTRICTION POLICY: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp is permitted to run at the 'unrestricted' authorization level.
MSI (s) (18:9C) [23:13:06:625]: SequencePatches starts. Product code: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}, Product version: 9.00.2047.00, Upgrade code: {3A91FA19-A197-467C-850F-0AFE90899371}, Product language 1033
MSI (s) (18:9C) [23:13:06:625]: PATCH SEQUENCER WARNING: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp patch will not be sequenced because it does not contain any transform that may apply to product!
MSI (s) (18:9C) [23:13:06:625]: SequencePatches returns success.
MSI (s) (18:9C) [23:13:06:625]: Final Patch Application Order:
MSI (s) (18:9C) [23:13:06:625]: Other Patches:
MSI (s) (18:9C) [23:13:06:625]: Unknown\Absent: {EE92F683-5F5C-4970-BB0B-9AC591B60268} - \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp
MSI (s) (18:9C) [23:13:06:625]: Product: Microsoft SQL Server Setup Support Files (English) - Update '{EE92F683-5F5C-4970-BB0B-9AC591B60268}' could not be installed. Error code 1642. Additional information is available in the log file C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_SqlSupport.msp.log.

MSI (s) (18:9C) [23:13:06:625]: Note: 1: 1708
MSI (s) (18:9C) [23:13:06:625]: Note: 1: 2729
MSI (s) (18:9C) [23:13:06:671]: Note: 1: 2729
MSI (s) (18:9C) [23:13:06:671]: Product: Microsoft SQL Server Setup Support Files (English) -- Installation failed.

MSI (s) (18:9C) [23:13:06:671]: Attempting to delete file C:\WINDOWS\Installer\7d5500e.msp
MSI (s) (18:9C) [23:13:06:671]: MainEngineThread is returning 1642
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer an
d that you have the correct upgrade patch.
c:\WINDOWS\Installer\2b422ff9.msi
MSI (c) (30:E8) [23:13:06:671]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (30:E8) [23:13:06:671]: MainEngineThread is returning 1642
=== Verbose logging stopped: 4/23/2006 23:13:06 ===

|||i got the same error message.|||

We're getting a KB article ready for this.

SP1 fails with "Unable to install Windows Installer MSP file" for "Setup Support Files"
Workaround:

1/ Save the registry contents of:
KeyName: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Bootstrap\MSIRefCount
Value: Uninstall

2/ Uninstall SqlSupport.msi from Add/Remove control panel
3/ Install SqlSupport.msi version 1399 from the RTM media.
4/ Restore the registry contents that were saved in step 1.

|||That did the trick.|||

Thanks Jeffrey!

This worked for me as well. I posted visual instructions on my blog at VSTeamSystemCentral.com.

:{> Andy

|||

Worked for me too. Thanks,

Jonathan

|||

Works for me, too!

THANK YOU!

Robert.

|||

I downloaded SP2 this week and I'm getting what appears to be the same error...was this not resolved as part of the SP2 release? Do the same steps above apply for SP2?

Thanks

Failure installing SQL Server 2005 SP 1

Windows XP Pro
SQL Server 2005 Express
SQL Server 2005 Standard

I installed the service pack for SQL Server Express first.
Then I tried to install the service pack for SQL Server. I got the error message, "A recently applied update, KB913090, failed to install.", while it was upgrading the Setup Support Files.

Jonathan Allen

Log follows...

04/22/2006 10:52:34.781 ================================================================================
04/22/2006 10:52:34.875 Hotfix package launched
04/22/2006 10:53:47.546 Attempting to install instance: SQL Server Native Client
04/22/2006 10:53:47.578 Attempting to install target: RADICALJAY
04/22/2006 10:53:47.593 Attempting to install file: sqlncli.msi
04/22/2006 10:53:47.687 Attempting to install file: \\RADICALJAY\c$\b1f5502657526de4ed0c\HotFixSqlncli\Files\sqlncli.msi
04/22/2006 10:53:47.687 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
04/22/2006 10:53:47.703 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
04/22/2006 10:53:47.718 Failed to read registry key: Debug
04/22/2006 10:53:49.578 MSP returned 0: The action completed successfully.
04/22/2006 10:53:49.765 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
04/22/2006 10:53:49.781 Failed to read registry key: Debug
04/22/2006 10:53:49.781 Successfully installed file: \\RADICALJAY\c$\b1f5502657526de4ed0c\HotFixSqlncli\Files\sqlncli.msi
04/22/2006 10:53:49.796 Successfully installed target: RADICALJAY
04/22/2006 10:53:49.812 Successfully installed instance: SQL Server Native Client
04/22/2006 10:53:49.828
04/22/2006 10:53:49.828 Product Status Summary:
04/22/2006 10:53:49.843 Product: SQL Server Native Client
04/22/2006 10:53:49.859 SQL Server Native Client (RTM ) - Success
04/22/2006 10:53:49.859
04/22/2006 10:53:49.875 Product: Setup Support Files
04/22/2006 10:53:49.890 Setup Support Files (RTM ) - Not Applied
04/22/2006 10:53:49.890
04/22/2006 10:53:49.906 Product: Database Services
04/22/2006 10:53:49.921 Database Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:49.937 Analysis Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:49.937 Reporting Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:49.953
04/22/2006 10:53:49.968 Product: Database Services
04/22/2006 10:53:49.968 Database Services (SP1 2047 ENU) - NA
04/22/2006 10:53:49.984 Details: Instances of SQL Server Express cannot be updated by using this Service Pack installer. To update instances of SQL Server Express, use the SQL Server Express Service Pack installer.
04/22/2006 10:53:50.000
04/22/2006 10:53:50.015 Product: Notification Services
04/22/2006 10:53:50.015 Notification Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:50.031
04/22/2006 10:53:50.046 Product: Integration Services
04/22/2006 10:53:50.046 Integration Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:50.062
04/22/2006 10:53:50.078 Product: Client Components
04/22/2006 10:53:50.093 Client Components (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:50.093
04/22/2006 10:53:50.109 Product: MSXML 6.0 Parser
04/22/2006 10:53:50.125 MSXML 6.0 Parser (RTM ) - Not Applied
04/22/2006 10:53:50.125
04/22/2006 10:53:50.140 Product: SQLXML4
04/22/2006 10:53:50.156 SQLXML4 (RTM ) - Not Applied
04/22/2006 10:53:50.171
04/22/2006 10:53:50.171 Product: Backward Compatibility
04/22/2006 10:53:50.187 Backward Compatibility (RTM ) - Not Applied
04/22/2006 10:53:50.203
04/22/2006 10:53:50.203 Product: Microsoft SQL Server VSS Writer
04/22/2006 10:53:50.218 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
04/22/2006 10:53:50.234

This appears to be the log from trying to apply SP1 to your Express instance.

04/22/2006 10:53:49.968 Database Services (SP1 2047 ENU) - NA
04/22/2006 10:53:49.984 Details: Instances of SQL Server Express cannot be updated by using this Service Pack installer. To update instances of SQL Server Express, use the SQL Server Express Service Pack installer.

Can you share out the msp log from the second attempt? The logs are in the %windir%\hotfix folder. If you do a search for "return value 3", that may lead you to the failed component log.

Thanks,
Samuel Lester (MSFT)

|||

This is the new log file from the Service Pack GUI...

04/23/2006 23:12:21.656 ================================================================================
04/23/2006 23:12:21.671 Hotfix package launched
04/23/2006 23:13:02.750 Attempting to install instance: SQL Server Native Client
04/23/2006 23:13:02.796 Attempting to install target: RADICALJAY
04/23/2006 23:13:02.812 Attempting to install file: sqlncli.msi
04/23/2006 23:13:03.031 Attempting to install file: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlncli\Files\sqlncli.msi
04/23/2006 23:13:03.031 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
04/23/2006 23:13:03.046 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
04/23/2006 23:13:03.062 Failed to read registry key: Debug
04/23/2006 23:13:05.468 MSP returned 0: The action completed successfully.
04/23/2006 23:13:05.656 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
04/23/2006 23:13:05.687 Failed to read registry key: Debug
04/23/2006 23:13:05.703 Successfully installed file: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlncli\Files\sqlncli.msi
04/23/2006 23:13:05.718 Successfully installed target: RADICALJAY
04/23/2006 23:13:05.718 Successfully installed instance: SQL Server Native Client
04/23/2006 23:13:05.734
04/23/2006 23:13:05.750 Product Status Summary:
04/23/2006 23:13:05.750 Product: SQL Server Native Client
04/23/2006 23:13:05.765 SQL Server Native Client (RTM ) - Success
04/23/2006 23:13:05.781
04/23/2006 23:13:05.796 Product: Setup Support Files
04/23/2006 23:13:05.796 Setup Support Files (RTM ) - Not Applied
04/23/2006 23:13:05.812
04/23/2006 23:13:05.828 Product: Database Services
04/23/2006 23:13:05.828 Database Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.843 Analysis Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.859 Reporting Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.875
04/23/2006 23:13:05.875 Product: Database Services
04/23/2006 23:13:05.890 Database Services (SP1 2047 ENU) - NA
04/23/2006 23:13:05.906 Details: Instances of SQL Server Express cannot be updated by using this Service Pack installer. To update instances of SQL Server Express, use the SQL Server Express Service Pack installer.
04/23/2006 23:13:05.906
04/23/2006 23:13:05.921 Product: Notification Services
04/23/2006 23:13:05.937 Notification Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.953
04/23/2006 23:13:05.953 Product: Integration Services
04/23/2006 23:13:05.968 Integration Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.984
04/23/2006 23:13:05.984 Product: Client Components
04/23/2006 23:13:06.000 Client Components (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:06.031
04/23/2006 23:13:06.046 Product: MSXML 6.0 Parser
04/23/2006 23:13:06.046 MSXML 6.0 Parser (RTM ) - Not Applied
04/23/2006 23:13:06.062
04/23/2006 23:13:06.078 Product: SQLXML4
04/23/2006 23:13:06.078 SQLXML4 (RTM ) - Not Applied
04/23/2006 23:13:06.093
04/23/2006 23:13:06.109 Product: Backward Compatibility
04/23/2006 23:13:06.109 Backward Compatibility (RTM ) - Not Applied
04/23/2006 23:13:06.125
04/23/2006 23:13:06.140 Product: Microsoft SQL Server VSS Writer
04/23/2006 23:13:06.156 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
04/23/2006 23:13:06.156

I didn't find "return value 3", but this was interesting...

"C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_SqlSupport.msp.log"

=== Verbose logging started: 4/23/2006 23:13:06 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (30:E8) [23:13:06:375]: Resetting cached policy values
MSI (c) (30:E8) [23:13:06:375]: Machine policy value 'Debug' is 0
MSI (c) (30:E8) [23:13:06:375]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (c) (30:E8) [23:13:06:375]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (30:E8) [23:13:06:375]: Grabbed execution mutex.
MSI (c) (30:E8) [23:13:06:375]: Cloaking enabled.
MSI (c) (30:E8) [23:13:06:375]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (30:E8) [23:13:06:390]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (18:88) [23:13:06:390]: Grabbed execution mutex.
MSI (s) (18:9C) [23:13:06:390]: Resetting cached policy values
MSI (s) (18:9C) [23:13:06:390]: Machine policy value 'Debug' is 0
MSI (s) (18:9C) [23:13:06:390]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (s) (18:9C) [23:13:06:390]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (18:9C) [23:13:06:390]: End dialog not enabled
MSI (s) (18:9C) [23:13:06:390]: Original package ==> c:\WINDOWS\Installer\2b422ff9.msi
MSI (s) (18:9C) [23:13:06:390]: Package we're running from ==> c:\WINDOWS\Installer\2b422ff9.msi
MSI (s) (18:9C) [23:13:06:390]: APPCOMPAT: looking for appcompat database entry with ProductCode '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'.
MSI (s) (18:9C) [23:13:06:390]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (18:9C) [23:13:06:390]: MSCOREE not loaded loading copy from system32
MSI (s) (18:9C) [23:13:06:500]: File will have security applied from OpCode.
MSI (s) (18:9C) [23:13:06:593]: Original patch ==> \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp
MSI (s) (18:9C) [23:13:06:593]: Patch we're running from ==> C:\WINDOWS\Installer\7d5500e.msp
MSI (s) (18:9C) [23:13:06:593]: SOFTWARE RESTRICTION POLICY: Verifying patch --> '\\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp' against software restriction policy
MSI (s) (18:9C) [23:13:06:593]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (18:9C) [23:13:06:593]: SOFTWARE RESTRICTION POLICY: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp is not digitally signed
MSI (s) (18:9C) [23:13:06:609]: SOFTWARE RESTRICTION POLICY: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp is permitted to run at the 'unrestricted' authorization level.
MSI (s) (18:9C) [23:13:06:625]: SequencePatches starts. Product code: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}, Product version: 9.00.2047.00, Upgrade code: {3A91FA19-A197-467C-850F-0AFE90899371}, Product language 1033
MSI (s) (18:9C) [23:13:06:625]: PATCH SEQUENCER WARNING: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp patch will not be sequenced because it does not contain any transform that may apply to product!
MSI (s) (18:9C) [23:13:06:625]: SequencePatches returns success.
MSI (s) (18:9C) [23:13:06:625]: Final Patch Application Order:
MSI (s) (18:9C) [23:13:06:625]: Other Patches:
MSI (s) (18:9C) [23:13:06:625]: Unknown\Absent: {EE92F683-5F5C-4970-BB0B-9AC591B60268} - \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp
MSI (s) (18:9C) [23:13:06:625]: Product: Microsoft SQL Server Setup Support Files (English) - Update '{EE92F683-5F5C-4970-BB0B-9AC591B60268}' could not be installed. Error code 1642. Additional information is available in the log file C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_SqlSupport.msp.log.

MSI (s) (18:9C) [23:13:06:625]: Note: 1: 1708
MSI (s) (18:9C) [23:13:06:625]: Note: 1: 2729
MSI (s) (18:9C) [23:13:06:671]: Note: 1: 2729
MSI (s) (18:9C) [23:13:06:671]: Product: Microsoft SQL Server Setup Support Files (English) -- Installation failed.

MSI (s) (18:9C) [23:13:06:671]: Attempting to delete file C:\WINDOWS\Installer\7d5500e.msp
MSI (s) (18:9C) [23:13:06:671]: MainEngineThread is returning 1642
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer an
d that you have the correct upgrade patch.
c:\WINDOWS\Installer\2b422ff9.msi
MSI (c) (30:E8) [23:13:06:671]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (30:E8) [23:13:06:671]: MainEngineThread is returning 1642
=== Verbose logging stopped: 4/23/2006 23:13:06 ===

|||i got the same error message.|||

We're getting a KB article ready for this.

SP1 fails with "Unable to install Windows Installer MSP file" for "Setup Support Files"
Workaround:

1/ Save the registry contents of:
KeyName: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Bootstrap\MSIRefCount
Value: Uninstall

2/ Uninstall SqlSupport.msi from Add/Remove control panel
3/ Install SqlSupport.msi version 1399 from the RTM media.
4/ Restore the registry contents that were saved in step 1.

|||That did the trick.|||

Thanks Jeffrey!

This worked for me as well. I posted visual instructions on my blog at VSTeamSystemCentral.com.

:{> Andy

|||

Worked for me too. Thanks,

Jonathan

|||

Works for me, too!

THANK YOU!

Robert.

|||

I downloaded SP2 this week and I'm getting what appears to be the same error...was this not resolved as part of the SP2 release? Do the same steps above apply for SP2?

Thanks

Failure installing SQL Server 2005 SP 1

Windows XP Pro
SQL Server 2005 Express
SQL Server 2005 Standard

I installed the service pack for SQL Server Express first.
Then I tried to install the service pack for SQL Server. I got the error message, "A recently applied update, KB913090, failed to install.", while it was upgrading the Setup Support Files.

Jonathan Allen

Log follows...

04/22/2006 10:52:34.781 ================================================================================
04/22/2006 10:52:34.875 Hotfix package launched
04/22/2006 10:53:47.546 Attempting to install instance: SQL Server Native Client
04/22/2006 10:53:47.578 Attempting to install target: RADICALJAY
04/22/2006 10:53:47.593 Attempting to install file: sqlncli.msi
04/22/2006 10:53:47.687 Attempting to install file: \\RADICALJAY\c$\b1f5502657526de4ed0c\HotFixSqlncli\Files\sqlncli.msi
04/22/2006 10:53:47.687 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
04/22/2006 10:53:47.703 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
04/22/2006 10:53:47.718 Failed to read registry key: Debug
04/22/2006 10:53:49.578 MSP returned 0: The action completed successfully.
04/22/2006 10:53:49.765 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
04/22/2006 10:53:49.781 Failed to read registry key: Debug
04/22/2006 10:53:49.781 Successfully installed file: \\RADICALJAY\c$\b1f5502657526de4ed0c\HotFixSqlncli\Files\sqlncli.msi
04/22/2006 10:53:49.796 Successfully installed target: RADICALJAY
04/22/2006 10:53:49.812 Successfully installed instance: SQL Server Native Client
04/22/2006 10:53:49.828
04/22/2006 10:53:49.828 Product Status Summary:
04/22/2006 10:53:49.843 Product: SQL Server Native Client
04/22/2006 10:53:49.859 SQL Server Native Client (RTM ) - Success
04/22/2006 10:53:49.859
04/22/2006 10:53:49.875 Product: Setup Support Files
04/22/2006 10:53:49.890 Setup Support Files (RTM ) - Not Applied
04/22/2006 10:53:49.890
04/22/2006 10:53:49.906 Product: Database Services
04/22/2006 10:53:49.921 Database Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:49.937 Analysis Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:49.937 Reporting Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:49.953
04/22/2006 10:53:49.968 Product: Database Services
04/22/2006 10:53:49.968 Database Services (SP1 2047 ENU) - NA
04/22/2006 10:53:49.984 Details: Instances of SQL Server Express cannot be updated by using this Service Pack installer. To update instances of SQL Server Express, use the SQL Server Express Service Pack installer.
04/22/2006 10:53:50.000
04/22/2006 10:53:50.015 Product: Notification Services
04/22/2006 10:53:50.015 Notification Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:50.031
04/22/2006 10:53:50.046 Product: Integration Services
04/22/2006 10:53:50.046 Integration Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:50.062
04/22/2006 10:53:50.078 Product: Client Components
04/22/2006 10:53:50.093 Client Components (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:50.093
04/22/2006 10:53:50.109 Product: MSXML 6.0 Parser
04/22/2006 10:53:50.125 MSXML 6.0 Parser (RTM ) - Not Applied
04/22/2006 10:53:50.125
04/22/2006 10:53:50.140 Product: SQLXML4
04/22/2006 10:53:50.156 SQLXML4 (RTM ) - Not Applied
04/22/2006 10:53:50.171
04/22/2006 10:53:50.171 Product: Backward Compatibility
04/22/2006 10:53:50.187 Backward Compatibility (RTM ) - Not Applied
04/22/2006 10:53:50.203
04/22/2006 10:53:50.203 Product: Microsoft SQL Server VSS Writer
04/22/2006 10:53:50.218 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
04/22/2006 10:53:50.234

This appears to be the log from trying to apply SP1 to your Express instance.

04/22/2006 10:53:49.968 Database Services (SP1 2047 ENU) - NA
04/22/2006 10:53:49.984 Details: Instances of SQL Server Express cannot be updated by using this Service Pack installer. To update instances of SQL Server Express, use the SQL Server Express Service Pack installer.

Can you share out the msp log from the second attempt? The logs are in the %windir%\hotfix folder. If you do a search for "return value 3", that may lead you to the failed component log.

Thanks,
Samuel Lester (MSFT)

|||

This is the new log file from the Service Pack GUI...

04/23/2006 23:12:21.656 ================================================================================
04/23/2006 23:12:21.671 Hotfix package launched
04/23/2006 23:13:02.750 Attempting to install instance: SQL Server Native Client
04/23/2006 23:13:02.796 Attempting to install target: RADICALJAY
04/23/2006 23:13:02.812 Attempting to install file: sqlncli.msi
04/23/2006 23:13:03.031 Attempting to install file: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlncli\Files\sqlncli.msi
04/23/2006 23:13:03.031 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
04/23/2006 23:13:03.046 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
04/23/2006 23:13:03.062 Failed to read registry key: Debug
04/23/2006 23:13:05.468 MSP returned 0: The action completed successfully.
04/23/2006 23:13:05.656 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
04/23/2006 23:13:05.687 Failed to read registry key: Debug
04/23/2006 23:13:05.703 Successfully installed file: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlncli\Files\sqlncli.msi
04/23/2006 23:13:05.718 Successfully installed target: RADICALJAY
04/23/2006 23:13:05.718 Successfully installed instance: SQL Server Native Client
04/23/2006 23:13:05.734
04/23/2006 23:13:05.750 Product Status Summary:
04/23/2006 23:13:05.750 Product: SQL Server Native Client
04/23/2006 23:13:05.765 SQL Server Native Client (RTM ) - Success
04/23/2006 23:13:05.781
04/23/2006 23:13:05.796 Product: Setup Support Files
04/23/2006 23:13:05.796 Setup Support Files (RTM ) - Not Applied
04/23/2006 23:13:05.812
04/23/2006 23:13:05.828 Product: Database Services
04/23/2006 23:13:05.828 Database Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.843 Analysis Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.859 Reporting Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.875
04/23/2006 23:13:05.875 Product: Database Services
04/23/2006 23:13:05.890 Database Services (SP1 2047 ENU) - NA
04/23/2006 23:13:05.906 Details: Instances of SQL Server Express cannot be updated by using this Service Pack installer. To update instances of SQL Server Express, use the SQL Server Express Service Pack installer.
04/23/2006 23:13:05.906
04/23/2006 23:13:05.921 Product: Notification Services
04/23/2006 23:13:05.937 Notification Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.953
04/23/2006 23:13:05.953 Product: Integration Services
04/23/2006 23:13:05.968 Integration Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.984
04/23/2006 23:13:05.984 Product: Client Components
04/23/2006 23:13:06.000 Client Components (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:06.031
04/23/2006 23:13:06.046 Product: MSXML 6.0 Parser
04/23/2006 23:13:06.046 MSXML 6.0 Parser (RTM ) - Not Applied
04/23/2006 23:13:06.062
04/23/2006 23:13:06.078 Product: SQLXML4
04/23/2006 23:13:06.078 SQLXML4 (RTM ) - Not Applied
04/23/2006 23:13:06.093
04/23/2006 23:13:06.109 Product: Backward Compatibility
04/23/2006 23:13:06.109 Backward Compatibility (RTM ) - Not Applied
04/23/2006 23:13:06.125
04/23/2006 23:13:06.140 Product: Microsoft SQL Server VSS Writer
04/23/2006 23:13:06.156 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
04/23/2006 23:13:06.156

I didn't find "return value 3", but this was interesting...

"C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_SqlSupport.msp.log"

=== Verbose logging started: 4/23/2006 23:13:06 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (30:E8) [23:13:06:375]: Resetting cached policy values
MSI (c) (30:E8) [23:13:06:375]: Machine policy value 'Debug' is 0
MSI (c) (30:E8) [23:13:06:375]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (c) (30:E8) [23:13:06:375]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (30:E8) [23:13:06:375]: Grabbed execution mutex.
MSI (c) (30:E8) [23:13:06:375]: Cloaking enabled.
MSI (c) (30:E8) [23:13:06:375]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (30:E8) [23:13:06:390]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (18:88) [23:13:06:390]: Grabbed execution mutex.
MSI (s) (18:9C) [23:13:06:390]: Resetting cached policy values
MSI (s) (18:9C) [23:13:06:390]: Machine policy value 'Debug' is 0
MSI (s) (18:9C) [23:13:06:390]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (s) (18:9C) [23:13:06:390]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (18:9C) [23:13:06:390]: End dialog not enabled
MSI (s) (18:9C) [23:13:06:390]: Original package ==> c:\WINDOWS\Installer\2b422ff9.msi
MSI (s) (18:9C) [23:13:06:390]: Package we're running from ==> c:\WINDOWS\Installer\2b422ff9.msi
MSI (s) (18:9C) [23:13:06:390]: APPCOMPAT: looking for appcompat database entry with ProductCode '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'.
MSI (s) (18:9C) [23:13:06:390]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (18:9C) [23:13:06:390]: MSCOREE not loaded loading copy from system32
MSI (s) (18:9C) [23:13:06:500]: File will have security applied from OpCode.
MSI (s) (18:9C) [23:13:06:593]: Original patch ==> \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp
MSI (s) (18:9C) [23:13:06:593]: Patch we're running from ==> C:\WINDOWS\Installer\7d5500e.msp
MSI (s) (18:9C) [23:13:06:593]: SOFTWARE RESTRICTION POLICY: Verifying patch --> '\\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp' against software restriction policy
MSI (s) (18:9C) [23:13:06:593]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (18:9C) [23:13:06:593]: SOFTWARE RESTRICTION POLICY: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp is not digitally signed
MSI (s) (18:9C) [23:13:06:609]: SOFTWARE RESTRICTION POLICY: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp is permitted to run at the 'unrestricted' authorization level.
MSI (s) (18:9C) [23:13:06:625]: SequencePatches starts. Product code: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}, Product version: 9.00.2047.00, Upgrade code: {3A91FA19-A197-467C-850F-0AFE90899371}, Product language 1033
MSI (s) (18:9C) [23:13:06:625]: PATCH SEQUENCER WARNING: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp patch will not be sequenced because it does not contain any transform that may apply to product!
MSI (s) (18:9C) [23:13:06:625]: SequencePatches returns success.
MSI (s) (18:9C) [23:13:06:625]: Final Patch Application Order:
MSI (s) (18:9C) [23:13:06:625]: Other Patches:
MSI (s) (18:9C) [23:13:06:625]: Unknown\Absent: {EE92F683-5F5C-4970-BB0B-9AC591B60268} - \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp
MSI (s) (18:9C) [23:13:06:625]: Product: Microsoft SQL Server Setup Support Files (English) - Update '{EE92F683-5F5C-4970-BB0B-9AC591B60268}' could not be installed. Error code 1642. Additional information is available in the log file C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_SqlSupport.msp.log.

MSI (s) (18:9C) [23:13:06:625]: Note: 1: 1708
MSI (s) (18:9C) [23:13:06:625]: Note: 1: 2729
MSI (s) (18:9C) [23:13:06:671]: Note: 1: 2729
MSI (s) (18:9C) [23:13:06:671]: Product: Microsoft SQL Server Setup Support Files (English) -- Installation failed.

MSI (s) (18:9C) [23:13:06:671]: Attempting to delete file C:\WINDOWS\Installer\7d5500e.msp
MSI (s) (18:9C) [23:13:06:671]: MainEngineThread is returning 1642
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer an
d that you have the correct upgrade patch.
c:\WINDOWS\Installer\2b422ff9.msi
MSI (c) (30:E8) [23:13:06:671]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (30:E8) [23:13:06:671]: MainEngineThread is returning 1642
=== Verbose logging stopped: 4/23/2006 23:13:06 ===

|||i got the same error message.|||

We're getting a KB article ready for this.

SP1 fails with "Unable to install Windows Installer MSP file" for "Setup Support Files"
Workaround:

1/ Save the registry contents of:
KeyName: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Bootstrap\MSIRefCount
Value: Uninstall

2/ Uninstall SqlSupport.msi from Add/Remove control panel
3/ Install SqlSupport.msi version 1399 from the RTM media.
4/ Restore the registry contents that were saved in step 1.

|||That did the trick.|||

Thanks Jeffrey!

This worked for me as well. I posted visual instructions on my blog at VSTeamSystemCentral.com.

:{> Andy

|||

Worked for me too. Thanks,

Jonathan

|||

Works for me, too!

THANK YOU!

Robert.

|||

I downloaded SP2 this week and I'm getting what appears to be the same error...was this not resolved as part of the SP2 release? Do the same steps above apply for SP2?

Thanks

Failure installing sql server 2005 express on vista ultimate x64, error 29506

Whenever I try to install SQL Server 2005 Express Edition on my Vista Ultimate x64 platform I get error 29506. All I could find on the web was that this is probably due to an access control problem. I have tried installing it as the local administrator, as a member of domain admins, and as the domain administrator. All get the same error. My domain is a Small Business Server domain. This may be part of the problem, but I can't imagine how.

When trying to force access to the domain administrator, I also seem to get an access problem.

Any suggestions?

First off I would try the sp1 version, but other then that the SP2 is the next supported release on Vista, there is a ctp release but the final release has not been made...

When installing VS Express you need to run the install under elevated permissions, I do this by running a command prompt as an administrator (Right clicking on the icon and selelcting run as admin), then run the exec by using the command prompt.

|||

Steve:

Were you ever able to get this issue resolved?

Thanks!

Rory O. Cahill

Failure installing sql server 2005 express on vista ultimate x64, error 29506

Whenever I try to install SQL Server 2005 Express Edition on my Vista Ultimate x64 platform I get error 29506. All I could find on the web was that this is probably due to an access control problem. I have tried installing it as the local administrator, as a member of domain admins, and as the domain administrator. All get the same error. My domain is a Small Business Server domain. This may be part of the problem, but I can't imagine how.

When trying to force access to the domain administrator, I also seem to get an access problem.

Any suggestions?

First off I would try the sp1 version, but other then that the SP2 is the next supported release on Vista, there is a ctp release but the final release has not been made...

When installing VS Express you need to run the install under elevated permissions, I do this by running a command prompt as an administrator (Right clicking on the icon and selelcting run as admin), then run the exec by using the command prompt.

Failure during insatallation of the SQL Express

Hello,

I am getting this message:

Setup failed because Service MSSQL$SQLExpress is disabled for the current hardware profile.Services must be set with the current Hardware Profile logon property profile enabled.

Any idea how to resolve this problem?

Thanks,
Eitan

Here are a few prior suggestions that seem to fix this problem:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=881197&SiteID=1

Thanks,
Sam Lester (MSFT)