From: mchua on 17 Jul 2008 10:07 I was trying to install this update to no avail. Error code returned is 2B08. I had try to search for KB on this error code but return no results. Now I cannot RAS in to my corpnet because of security violation for not installing this update. I am stuck. Any assistance you can offer is much appreciated. Thank you!
From: PA Bear [MS MVP] on 17 Jul 2008 14:03 Tip from a pro: http://msmvps.com/blogs/bradley/archive/2008/07/17/patching-this-month-sbs-2003-sp2-standard.aspx Or you could... Start a free Windows Update support incident request: https://support.microsoft.com/oas/default.aspx?gprid=6527 Support for Windows Update: http://support.microsoft.com/gp/wusupport For home users, no-charge support is available by calling 1-866-PCSAFETY in the United States and in Canada or by contacting your local Microsoft subsidiary. There is no-charge for support calls that are associated with security updates. When you call, clearly state that your problem is related to a Security Update and cite the update's KB number(s). For more information about how to contact your local Microsoft subsidiary for security update support issues, visit the International Support Web site: http://support.microsoft.com/common/international.aspx For enterprise customers, support for security updates is available through your usual support contacts. -- ~Robear Dyer (PA Bear) MS MVP-Windows (IE, OE, Security, Shell/User) AumHa VSOP & Admin; DTS-L.net mchua wrote: > I was trying to install this update to no avail. Error code returned is > 2B08. I had try to search for KB on this error code but return no > results. > Now I cannot RAS in to my corpnet because of security violation for not > installing this update. I am stuck. Any assistance you can offer is > much > appreciated. > > Thank you!
From: kavi_nash on 18 Jul 2008 06:25 Found possible solutions at last!!! When you face this problem, the first thing you have to do is to go through the latest log file Summary.txt under the directory C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\ and search for any failures (Status : Failure). We can solve the issue directly from this log file. Here is what I have observed in the log file in different machines and the possible solutions : Case 1: ---------------------------------------------------------------------------------- Product : SQL Server Database Services 2005 (SQLEXPRESS) Product Version (Previous): 3042 Product Version (Final) : Status : Failure Log File : C:\Program Files\Microsoft SQL Server \90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB948109_sqlrun_sql.msp.log SQL Express Features : Error Number : 1646 Error Description : Unable to install Windows Installer MSP file ---------------------------------------------------------------------------------- Possible Solution: Reboot your machine before doing any of the following changes. In the registry editor, go through the following key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion \Installer\UserData\S-1-5-18\Products\7DDFFFA258DE09A4C825D59ABECDB9F8 and search for Uninstallable key. Change the value to 1 if it is 0. Reinstall the patch and it should be successful now. Case 2: ---------------------------------------------------------------------------------- Product Installation Status Product : SQL Server Database Services 2005 (MSSQLSERVER) Product Version (Previous): 3054 Product Version (Final) : Status : Failure Log File : C:\Program Files\Microsoft SQL Server \90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB948109_sqlrun_sql.msp.log Error Number : 29506 Error Description : MSP Error: 29506 SQL Server Setup failed to modify security permissions on file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user Administrator. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive. ---------------------------------------------------------------------------------- Possible Solution: Reboot your machine before doing any of the following changes. Login to management studio for the default instance(MSSQLSERVER) and have a look at what all database we are having. We should not have any other file other than database, certificates under C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL \Data\. Try moving all the files under this directory to a temp folder. Leave the files which are in use. It moved around 10 files which are not in use in my case. Also assign Full permission to the logged in user to this folder. Start the installation and choose the default instance. It should be successful. Case 3: ---------------------------------------------------------------------------------- Product Installation Status Product : SQL Server Database Services 2005 (MSSQLSERVER) Product Version (Previous): 3054 Product Version (Final) : Status : Failure Log File : C:\Program Files\Microsoft SQL Server \90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB948109_sqlrun_sql.msp.log Error Number : 29538 Error Description : MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: C: \Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\distmdl1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again. ---------------------------------------------------------------------------------- Possible Solution: Reboot your machine before doing any of the following changes. Verify that distmdl.ldf and distmdl.mdf files are present under C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data \ and grant administrator permissions for these files to the logged in account. Please feel free to contact me if you face similar kind of issues.
From: PA Bear [MS MVP] on 18 Jul 2008 15:53 Thanks for sharing this information with the Community here. kavi_nash wrote: > Found possible solutions at last!!! > > When you face this problem, the first thing you have to do is to go > through the latest log file Summary.txt under the directory C:\Program > Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\ and search > for any failures (Status : Failure). We can solve the issue directly > from this log file. > > Here is what I have observed in the log file in different machines and > the possible solutions : > > � Case 1: > ---------------------------------------------------------------------------------- > Product : SQL Server Database Services 2005 > (SQLEXPRESS) > Product Version (Previous): 3042 > Product Version (Final) : > Status : Failure > Log File : C:\Program Files\Microsoft SQL Server > \90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB948109_sqlrun_sql.msp.log > SQL Express Features : > Error Number : 1646 > Error > Description : Unable to install Windows Installer MSP file > ---------------------------------------------------------------------------------- > > > Possible Solution: Reboot your machine before doing any of the > following changes. In the registry editor, go through the following > key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion > \Installer\UserData\S-1-5-18\Products\7DDFFFA258DE09A4C825D59ABECDB9F8 > and search for Uninstallable key. Change the value to 1 if it is 0. > Reinstall the patch and it should be successful now. > > > � Case 2: > ---------------------------------------------------------------------------------- > Product Installation Status > Product : SQL Server Database Services 2005 > (MSSQLSERVER) > Product Version (Previous): 3054 > Product Version (Final) : > Status : Failure > Log File : C:\Program Files\Microsoft SQL Server > \90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB948109_sqlrun_sql.msp.log > Error Number : 29506 > Error Description : MSP Error: 29506 SQL Server Setup failed > to modify security permissions on file C:\Program Files\Microsoft SQL > Server\MSSQL.1\MSSQL\Data\ for user Administrator. To proceed, verify > that the account and domain running SQL Server Setup exist, that the > account running SQL Server Setup has administrator privileges, and > that exists on the destination drive. > ---------------------------------------------------------------------------------- > > > Possible Solution: Reboot your machine before doing any of the > following changes. Login to management studio for the default > instance(MSSQLSERVER) and have a look at what all database we are > having. We should not have any other file other than database, > certificates under C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL > \Data\. Try moving all the files under this directory to a temp > folder. Leave the files which are in use. It moved around 10 files > which are not in use in my case. Also assign Full permission to the > logged in user to this folder. Start the installation and choose the > default instance. It should be successful. > > > � Case 3: > ---------------------------------------------------------------------------------- > Product Installation Status > Product : SQL Server Database Services 2005 > (MSSQLSERVER) > Product Version (Previous): 3054 > Product Version (Final) : > Status : Failure > Log File : C:\Program Files\Microsoft SQL Server > \90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB948109_sqlrun_sql.msp.log > Error Number : 29538 > Error Description : MSP Error: 29538 SQL Server Setup did not > have the administrator permissions required to rename a file: C: > \Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\distmdl1.ldf. > To continue, verify that the file exists, and either grant > administrator permissions to the account currently running Setup or > log in with an administrator account. Then run SQL Server Setup again. > ---------------------------------------------------------------------------------- > > Possible Solution: Reboot your machine before doing any of the > following changes. Verify that distmdl.ldf and distmdl.mdf files are > present under C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data > \ and grant administrator permissions for these files to the logged in > account. > > Please feel free to contact me if you face similar kind of issues.
|
Pages: 1 Prev: Solved: KB932471 Next: Having problems with one update!?! |