Answered by:
Error when installing installation support files on 2008 R2

Question
-
I am installing SQL Server 2008 R2 on a Server 2008 R2 machine. I run setup as administrator and I get to the Install Support Files step. It goes through several of the "workflow" steps. When it gets to "ExecuteStandardTimingsWorkflow" step, it throws an error:
"SQL Server Setup failure.
Attempted to Read or Write protected memory. This is often an indication that other memory is corrupt.."
I ran this on several other physical as well as virtual machines and I get the same problem. With SQL 2005, there is a similar issue where it tries to install to a compressed directory and throws the error.
If this is the same situation, If I can find out what is being installed where during ExecuteStandardTimingsWorkflow I can check that, but if it is something simpler, please advise.
Saturday, June 26, 2010 3:14 PM
Answers
-
Well I am not sure if you can externally download it. WI 5.0 comes with Win7 & Win 2008 R2
You may try to re-register WI services though
Open an elevated command prompt using "RunAs Administrator"
Now type: msiexec /regserver
Prashant [MSFT] -- This posting is provided "AS IS" with no warranties, and confers no rights.- Marked as answer by JayRollins Tuesday, July 20, 2010 4:16 PM
Thursday, July 1, 2010 10:24 AM
All replies
-
About the error:
"Attempted to Read or Write protected memory. This is often an indication that other memory is corrupt.."
I have usually seen this during an upgrade scenario for Reporting services from SQL 2005 to 2008. the upgrade goes succeessful. However upon upgrade you are not ble to browse the Report Server URL after upgrading to SSRS 2008 .
This is caused by virtual directories in IIS having the same name and TCP port numbers as the virtual directories specified within the SSRS configuration
Resolution is simple;
Remove the Reports and ReportServer virtual directories in IIS to ensure there are no conflict between those virtual directories and the ones in Reporting Service. Then recreate the virtual directories in the SSRS Config Manager.
Not sure if this is your case. Worth checking once..
Prashant [MSFT] -- This posting is provided "AS IS" with no warranties, and confers no rights.Sunday, June 27, 2010 10:58 AM -
This is a new install and not an upgrade so reporting services have never been created or started. So clarification, this is a bare metal install from the ground up with all new installs. Any other ideas? Any way I can find out what is being installed during ExecuteStandardTimingsWorkflow?
As added information, Web Server Role and .NET 3.51 framework and Windows Process Activation Services Features have been installed and patched. Everything else is Server 2008 R2 Enterprise. Nothing else has been installed.
Thanks,
Jay
- Edited by JayRollins Sunday, June 27, 2010 10:12 PM wronf .net version number
Sunday, June 27, 2010 10:07 PM -
Another update. Just in case it was the ISO i downloaded a new one and I still have the same problem. What is in the ExecuteStandardTimingsWorkflow and where does it get installed? I need help please...Tuesday, June 29, 2010 2:41 AM
-
Can you try this; Directly run the support files msi from the media:
..\1033_ENU_LP\x64\Setup\sqlsupport_msi\SqlSupport.msi
Prashant [MSFT] -- This posting is provided "AS IS" with no warranties, and confers no rights.Tuesday, June 29, 2010 7:06 AM -
I ran it and this is what I got:
Problem signature:
Problem Event Name: APPCRASH
Application Name: msiexec.exe
Application Version: 5.0.7600.16385
Application Timestamp: 4a5bc7bd
Fault Module Name: msi.dll
Fault Module Version: 5.0.7600.16385
Fault Module Timestamp: 4a5bdfdd
Exception Code: c0000005
Exception Offset: 00000000000e87eb
OS Version: 6.1.7600.2.0.0.274.10
Locale ID: 1033
Additional Information 1: 857e
Additional Information 2: 857e7340a9cf368a90b365933cf6805c
Additional Information 3: a5d5
Additional Information 4: a5d5482c1e06d409bf1c597b6802b2feThis would explain why it would crash on all my machines. The same version was installed from the same media on all physical and VMs. After finding this, I tried allowing the service to interact with the desktop and tried (and removed) having the service log on as domain admin just in case, but still crashed.
Any insight would be appreciated
- Edited by JayRollins Tuesday, June 29, 2010 1:55 PM updated troubleshooting steps
Tuesday, June 29, 2010 1:24 PM -
Alright, so seems like msiexec.exe is crashing with an Access denied (c0000005)
Can you check if you are able to install any other software on the same machine. Just to test if msiexec works
Also, are you saying that you used the same media to install ion otehr machines? Are they successful? Instance up and running?
--If this is true, then consider reinstalling windows installer services on the affected server. If this is not true, then worth trying with a different media :)
Prashant [MSFT] -- This posting is provided "AS IS" with no warranties, and confers no rights.Wednesday, June 30, 2010 7:32 AM -
I can only find resitributables for installer service version 4.5. Is there a link you can provide for 5.0?Wednesday, June 30, 2010 3:11 PM
-
Well I am not sure if you can externally download it. WI 5.0 comes with Win7 & Win 2008 R2
You may try to re-register WI services though
Open an elevated command prompt using "RunAs Administrator"
Now type: msiexec /regserver
Prashant [MSFT] -- This posting is provided "AS IS" with no warranties, and confers no rights.- Marked as answer by JayRollins Tuesday, July 20, 2010 4:16 PM
Thursday, July 1, 2010 10:24 AM -
I have the same problem, Any solution?Tuesday, November 23, 2010 7:23 PM
-
I have this same problem, did anyone find the solution?
Smiley HikeFriday, January 28, 2011 9:32 PM -
I just found a solution for me:
after executing ExecuteStandardTimingsWorkflow it looks for the support files.msi
on a german server with an english language interface it looks in the 1033 directory, but on my german cd it is in the 1031 directory.
so I had to copy the CD in c:\install then copy the msi from 1031 directory to 1033 directory.
C:\install\SQL\1033_ENU_LP\x64\Setup
- Proposed as answer by HEC123 Wednesday, July 13, 2011 3:58 AM
Monday, May 30, 2011 2:36 PM -
I just found a solution for me:
after executing ExecuteStandardTimingsWorkflow it looks for the support files.msi
on a german server with an english language interface it looks in the 1033 directory, but on my german cd it is in the 1031 directory.
so I had to copy the CD in c:\install then copy the msi from 1031 directory to 1033 directory.
C:\install\SQL\1033_ENU_LP\x64\Setup
THANKS A LOT! IT WORKS FOR ME, VERY HELPFUL AND EASY
Wednesday, July 13, 2011 4:01 AM -
New media fixed this for me. I love my MSDN Subscription!Friday, January 27, 2012 8:09 PM
-
Hello! I'm having the same problem. I tried the solution described above but had no success.
You must paste the installer within the folder C: \ install?
I'm using Windows 7 32bit. And I already have Visual Studio 2010 installed.
Anyone have any suggestions to help me?
Thank you.Thursday, September 27, 2012 3:37 PM -
Could you try un-installing SQL Support from Add/Remove program before re-trying ?
Regards,
Ahmed Ibrahim
SQL Server Setup Team
My Blog
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you.
This can be beneficial to other community members reading the thread.
Sunday, September 30, 2012 8:29 AM -
I discovered that the problem was in the version display language on my computer: I was using in Portuguese Portugal. After I changed the language for Pt-BR SQL Server was installed successfully.
Thank you!Thursday, September 26, 2013 7:41 PM