SQL Server 2005 and 2008 Setup Failures (Compressed DATA Directory)
We are always looking at customer issue reports in order to improve our software and your experience. The SQL Server Setup development team has identified numerous Watson reports of failed setups due to the compression state of the DATA directory.
Shown below is a failure I reproduced on my local machine. The DATA directory has been marked for compression but the (master, model, msdb and tempdb) are individual left uncompressed. I did this by starting the instance and compressing the DATA directory, skipping any in-use file. SQL Server starts and stops properly and setup generates the following error.
Error Number : 28062 (0x6d9e)
Error Description : MSP Error: 28062 SQL Server Setup cannot install files to the compressed or encrypted folder: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\. To continue, make sure that your installation directories are not compressed or encrypted, or specify a different directory, and then run SQL Server Setup again.
Solution: The resolution is to remove compression from the DATA directory and execute setup again.
Starting with SQL Server 2005 when the database is opened, if it is in read/write mode and the file is compressed it is considered a fatal error and the database remains closed. The only exception to this is a user instance and those files will be expanded and opened.
- I tested by compressing the files in the directory but not the entire directory itself. SQL Server detected a system database was compressed and failed to start.
- I tested by compressing the DATA directory but not the system database files. SQL Server started but failed to open pubs and adventure works.
Below is an example of a failure on startup when I only compressed TEMPDB.
2009-02-20 13:57:24.56 spid9s Error: 5118, Severity: 16, State: 1.
2009-02-20 13:57:24.56 spid9s The file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\tempdb.mdf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.
2009-02-20 13:57:24.56 spid9s Error: 5118, Severity: 16, State: 1.
2009-02-20 13:57:24.56 spid9s The file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\tempdb.mdf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.
2009-02-20 13:57:24.62 spid9s Error: 1802, Severity: 16, State: 4.
2009-02-20 13:57:24.62 spid9s CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
2009-02-20 13:57:24.62 spid9s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
Windows/Microsoft Update
When installing a SQL Server patch using Windows/Microsoft update you may receive the 0x6d9e error.
Important: Note the KB article number reported in the message. The files associated with the fix contain the KB number in the name. The files are located in you Program Files\Microsoft SQL Server\<<version>>\Setup Bootstrap\Log\Hotfix directories. On 64 bit systems you can have them in Program Files and Program Files (x86).
If you view the update history it provides a link to a more detailed description.
Notice that the error code is 0x6d9e and can be used to search the detailed SQL Server setup logs for additional details.
Go to the log directory and sort by the date modified. The summary.txt with the most recent date will contain more error details about the installation. Shown below is the error text from the compressed DATA directory failure. Notice that the instance name is provided in the log message and detailed log is noted as well.
Product : Database Services (SQL2005WOW)
Product Version (Previous): 3310
Product Version (Final) :
Status : Failure
Log File : C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB955706_sqlrun_sql.msp.log
Error Number : 28062
Error Description : MSP Error: 28062 SQL Server Setup cannot install files to the compressed or encrypted folder: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\. To continue, make sure that your installation directories are not compressed or encrypted, or specify a different directory, and then run SQL Server Setup again.
Opening the detailed log file the text indicates the location that is compressed incorrectly.
MSI (s) (E4!08) [11:23:43:488]: Product: Microsoft SQL Server 2005 -- Error 28062. SQL Server Setup cannot install files to the compressed or encrypted folder: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\. To continue, make sure that your installation directories are not compressed or encrypted, or specify a different directory, and then run SQL Server Setup again.
Error 28062. SQL Server Setup cannot install files to the compressed or encrypted folder: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\. To continue, make sure that your installation directories are not compressed or encrypted, or specify a different directory, and then run SQL Server Setup again.
<EndFunc Name='LaunchFunction' Return='28062' GetLastError='0'>
SQL Express
A common cause of this error is an install of the SQL Express edition and then compression of the Program Files folder. The DATA directory is marked compressed and will fail the setup check.
SQL Server 2008
DATA Directory: SQL Server 2008 can fail with a similar error and the resolution is the same.
Other Directories: SQL Server 2008 has a known issue where is incorrectly checks all installation paths (TOOLS included) and if any of are marked compressed the setup will generate the error. Make sure all setup destinations are uncompressed when installing SQL Server 2008. This may include the Program Files (x86) on 64 bit installations for the 32 bit only components.
Bob Dorr
SQL Server Principal Escalation Engineer
Comments
Anonymous
February 24, 2009
The comment has been removedAnonymous
February 25, 2009
Can you post more details to the e-mail account for this blog so we can better address your concerns?Anonymous
October 29, 2009
Microsoft SQL Server 2005 Service Pack 3 were not installed.Anonymous
November 02, 2009
i keep receiving a 6d9e error when installing this update supplied by mircosoft. I took compression off of the folder. please give directionAnonymous
November 15, 2009
Uuuuuuuuuuuuuuuuuuuuh, I just turned off the system restore feature in XP and found that this was what was keeping SSAS Service from starting. If anyone else is having trouble getting Analysis Services to start on XP with SQL Server 2008 R2 Nov CTP this may be their problem. Anyhow it finally is started. :)Anonymous
November 27, 2009
You didn't explain clearly how to fix it.Anonymous
November 27, 2009
You didn't rxplsin clearly on how to fix it.Anonymous
January 10, 2010
This is awful post. And the solution is to... ???Anonymous
January 13, 2010
usless. How do I uncompress or encryt the folder. Or how do I stop the update from installing.Anonymous
February 06, 2010
how do i fix it!!!!!!! thats what everyone here needs to know!!!!Anonymous
March 17, 2010
Two things: How do I find the offending files/folders? How do I fix the problem and eliminate the error?Anonymous
March 24, 2010
if the problem is in getting the printer to work, then we all need to know the steps in order, so we can fix the problem, but we are unable to print the steps out to follow, so what do we do? All you show here is what the problem is, but not how to fix it? What good is this doing for the person that needs to fix the problem?Anonymous
April 27, 2010
Ditto. We want the steps on how to decompress the compressed data.Anonymous
May 29, 2010
been more than a month since i asked how to find the compressed files or folders and uncompress them. are you guys sleeping?Anonymous
May 29, 2010
been a month since i asked how to find and fix compressed files and folders. are you guys asleep?Anonymous
January 27, 2011
The comment has been removedAnonymous
February 19, 2011
Couldn't we just roll back to previous restore point?Anonymous
March 03, 2011
Thank You Donna! Your suggestion worked! (Win 7 Pro, 64bit)Anonymous
March 05, 2011
How do you direct the download to a different location following error 6D9E? Microsoft SQL Server 2005 Express Edition Service Pack 4 (KB2463332) And how do you find the precise element that needs de-encrypted or decompressed? And then how do you decompress it?Anonymous
June 29, 2011
I have a windows update (Microsoft SQL Server 2005 Express Edition Service Pack 4) to install and every time I try to install it I get the 6D9E error. I am no computer whiz kid and I am completely baffled by this and the help pages might as well be written in Japanese, can you possible email me on dwmcgregor@hotmail.com with an idiots guide on how to cure this please? Cheers Dave McGregorAnonymous
July 22, 2011
TYVM Donna, Maybe Microsoft should hire U @ Least U Addressed what EVERYONE was asking Microsoft Just Said What to do (in a Foreign Language, as far as I was concerned), BUT NEVER Let Anyone Know HOW to do it!! Thank You Again, Donna!! ;) The Maupin'sAnonymous
August 05, 2011
Although one solution is to de-compress the drive I'm sure no one wants to do this can we have a solution that doesn't involve de-compressing the driveAnonymous
February 01, 2012
Thank you Donna. This is a case of needing to know your audience to provide an adequate answer. We are not all engineers. : )Anonymous
February 17, 2012
@Donna:Thanks a lot it worked for me too ...the article is a total bogus.Anonymous
August 31, 2012
je une grosse problème de windows uap et microsoftAnonymous
December 09, 2012
j'ai un probleme de mise à jour mon ordinateur a démarré