March 26, 2012 at 6:37 am
carmellabanker (3/26/2012)
(Right) So, this is 2008, not 2008 R2?Website solution | Web development Company | Web application
Yes this is 2008, not 2008 R2.
Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]
March 26, 2012 at 6:59 am
maybe you should disable any antivirus services running there, at times MS forefront stop exe executions thinking it's a virus. also try to see if your exe is not corrupt, did u try to download it again?
April 2, 2012 at 4:40 pm
I have the same problem... any solutions? Thanks
April 16, 2012 at 3:21 pm
April 18, 2012 at 3:20 pm
After about an hour on the phone with a Microsoft tech they solved it for me. It turns out that it is the same error mentioned in the above link, but I had already started in with Microsoft before seeing the response. However I thought it might be helpful for others if I detailed the steps the tech took to get to the solution.
1) First we tried the basics (everything I had already tried).
b) Manually extracted it, ran it, failed.
c) Checked the eventvwr and SQL logs, nothing there.
I should probably note that when working on a problem I’ve found it is always a good idea go through the basics again. When I first start in on a problem, then if I get stumped and start getting other people to look at it I always start back at the beginning. I've noticed over the years that 90% of the time when you have a complicated or difficult to solve problem, the solution is usually something easy that got missed during the first, second or even third pass. When you bring in someone new and go through the really easy stuff, sometimes you will discover something that you did wrong, or just plain missed.
2) Next he sent me a copy of procmon.exe (part of Sysinternals).
I'm not going to go into too much detail about this product since
b) there is a lot of online documentation about it.
I do have some experience with Sysinternals and was privileged to attend Argenis Fernandez's session on Sysinternals during the 2011 Pass Summit. Unfortunately I wasn't familiar enough with them to think of trying this on my own.
b) The MS tech had me filter out everything but programs called setup.exe
c) I ran setup.exe from the extracted SP code.
d) Procmon now displayed everything that setup.exe had done (almost 2000 events) including opening and closing registry entries, opening and closing files and the results of each action.
Here is an excerpt from the output:
"5:16:11.1602021 PM","setup.exe","4780","ReadFile","C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\security.config","SUCCESS","Offset: 43,831, Length: 4,251"
"5:16:11.1603700 PM","setup.exe","4780","ReadFile","C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\security.config","SUCCESS","Offset: 48,082, Length: 4,185"
"5:16:11.1605846 PM","setup.exe","4780","ReadFile","C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\security.config","SUCCESS","Offset: 52,267, Length: 954"
"5:16:11.1606593 PM","setup.exe","4780","ReadFile","C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\security.config","END OF FILE","Offset: 53,221, Length: 7,491"
"5:16:11.1607052 PM","setup.exe","4780","CloseFile","C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\security.config","SUCCESS",""
"5:16:11.1612310 PM","setup.exe","4780","WriteFile","C:\Documents and Settings\uf9a94\Local Settings\Temp\2\SqlSetup.log","FAST IO DISALLOWED","Offset: 4,208, Length: 136"
"5:16:11.1613335 PM","setup.exe","4780","WriteFile","C:\Documents and Settings\uf9a94\Local Settings\Temp\2\SqlSetup.log","SUCCESS","Offset: 4,208, Length: 136"
"5:16:11.1614378 PM","setup.exe","4780","WriteFile","C:\Documents and Settings\uf9a94\Local Settings\Temp\2\SqlSetup.log","FAST IO DISALLOWED","Offset: 4,344, Length: 4"
"5:16:11.1615377 PM","setup.exe","4780","WriteFile","C:\Documents and Settings\uf9a94\Local Settings\Temp\2\SqlSetup.log","SUCCESS","Offset: 4,344, Length: 4"
If you look in the last half you will note that there are WriteFile entries to a SqlSetup.log. A log file I’ve never heard of before personally. Here is the output of the file.
04/16/2012 17:16:11.091 ======================================================================
04/16/2012 17:16:11.091 Setup launched
04/16/2012 17:16:11.091 Attempting to determine media source
04/16/2012 17:16:11.091 Media source value not specified on command line argument.
04/16/2012 17:16:11.091 Setup is launched from media directly so default the value to the current folder.
04/16/2012 17:16:11.091 Media source: D:\2K8SP304/16/2012 17:16:11.091 Attempt to determine media layout based on file 'D:\2K8SP3\mediainfo.xml'.
04/16/2012 17:16:11.138 Media layout is detected as: Core
04/16/2012 17:16:11.138 Media LCID is detected as: 1033
04/16/2012 17:16:11.138 Not a slip stream media, so continuing to run setup.exe from media.
04/16/2012 17:16:11.138 /? or /HELP or /ACTION=HELP specified: false
04/16/2012 17:16:11.138 Help display: false
04/16/2012 17:16:11.138 Checking to see if we need to install .Net version 2.0
04/16/2012 17:16:11.138 Determining the cluster status of the local machine.
04/16/2012 17:16:11.138 The local machine is not configured as a cluster node.
04/16/2012 17:16:11.138 Attempting to find media for .Net version 2.0
04/16/2012 17:16:11.154 .Net version 2.0 is installed
04/16/2012 17:16:11.154 RedistMSI::GetExpectedBuildRevision - Setup expects MSI 4.5.6001.22159 at the minimum
04/16/2012 17:16:11.154 Attempting to get Windows Installer version
04/16/2012 17:16:11.154 Windows Installer version detected: 4.5.6001.22159
04/16/2012 17:16:11.154 RedistMSI::IsVistaRTM - Not Vista RTM build
04/16/2012 17:16:11.154 Required version of Windows Installer is already installed
04/16/2012 17:16:11.154 Patch related actions cannot be run from the local setup.exe, so continuing to run setup.exe from media.
04/16/2012 17:16:11.154 Attempt to initialize SQL setup code group
04/16/2012 17:16:11.154 Attempting to determine security.config file path
04/16/2012 17:16:11.154 Checking to see if policy file exists
04/16/2012 17:16:11.154 .Net security policy file does exist
04/16/2012 17:16:11.154 Attempting to load .Net security policy file
04/16/2012 17:16:11.170 Error: Cannot load .Net security policy file
04/16/2012 17:16:11.170 Error: InitializeSqlSetupCodeGroupCore(32bit) failed
04/16/2012 17:16:11.170 Error: InitializeSqlSetupCodeGroup failed: 0x80004005
04/16/2012 17:16:11.170 Setup closed with exit code: 0x80004005
04/16/2012 17:16:11.170 ======================================================================
It made for an interesting read regardless, but at the bottom we finally find the error. “Cannot load .Net security policy file.”
If you look in the procmon output again you will find the path for .net security.
C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG.
The tech now had me go to the directory 1 up from the CONFIG
directory.
C:\Windows\Microsoft.NET\Framework\v2.0.50727
and execute the command
caspol.exe -machine –reset
CASPOL.EXE is the “Code Access Security Policy Tool” and is documented by MS here: http://msdn.microsoft.com/en-us/library/cb6t8dtz(v=vs.80).aspx
After that was completed my patching ran with no problems.
Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]
October 2, 2012 at 1:35 pm
Thanks! caspol.exe fixed it for me 🙂
May 23, 2013 at 8:09 am
caspol.exe -machine -reset
was giving me an error about the switch -reset not being an alternative.
May 23, 2013 at 1:15 pm
Kenneth: Glad you got the mystery solved and thank you for posting the solution.
October 27, 2014 at 4:48 pm
I have the same issue with SQL 2008 R2 SP3, and found a KB about passing parameters to the self-extractor. http://support.microsoft.com/kb/912203
It didn't behave as it says, but was helpful. Passing parameters for "/log:" and "/extract", it prompted me for an extract path and prepopulated it with a folder different from the one I passed and different from the default temp, and allowed me to change it. This time the unzipped output persisted. HTH
Gary
December 16, 2014 at 8:49 am
It should be noted that this still happens with many service pack installs, but most of us need to add the 64 bit component:
'if you have 64 bit then use Framework64.'
I have seen lot of URL mentioning C:\Windows\Microsoft.NET\Framework\v2.0.50727\caspol.exe -machine -reset
http://shashanksrivastavasqldba.blogspot.be/2012/10/issue-4-applying-sp2-on-sql-server-2008.html
Viewing 10 posts - 31 through 39 (of 39 total)
You must be logged in to reply to this topic. Login to reply