Hi Everyone ,
I am facing issue while i am trying to install sql server 2008 R2(Standard Edition) on windows 2008 R2 (We havwe ADmin rights on the box). Below are the error message details .
Error Details :
The following error has occurred:
SQL Server Setup has encountered an error when running a Windows Installer file.
Windows Installer error message: The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
Windows Installer file: H:DBASQL_Server_oldSQL_Server_Standard_Editionx64redistwatsondw20sharedamd64.msi
Windows Installer log file: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20110119_010358WatsonX64_Cpu64_1_ComponentUpdate.log
Error log details :
=== Verbose logging started: 1/19/2011 1:07:21 Build type: SHIP UNICODE 5.00.7600.00 Calling process: H:DBASQL_Server_oldSQL_Server_Standard_Editionx64setup100.exe ===
MSI (c) (9C:3C) [01:07:21:282]: Resetting cached policy values
MSI (c) (9C:3C) [01:07:21:282]: Machine policy value ‘Debug’ is 0
MSI (c) (9C:3C) [01:07:21:282]: ******* RunEngine:
******* Product: H:DBASQL_Server_oldSQL_Server_Standard_Editionx64redistwatsondw20sharedamd64.msi
******* Action:
******* CommandLine: **********
MSI (c) (9C:3C) [01:07:21:282]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (9C:3C) [01:07:21:282]: Grabbed execution mutex.
MSI (c) (9C:3C) [01:07:51:328]: Failed to connect to server. Error: 0x80080005
MSI (c) (9C:3C) [01:07:51:328]: Failed to connect to server.
MSI (c) (9C:3C) [01:07:51:328]: MainEngineThread is returning 1601
=== Verbose logging stopped: 1/19/2011 1:07:51 ===
—————
I have verifed the following MSDn posts but the issue still not resolved .
http://support.microsoft.com/kb/319624
Note : On windows 2008 R2 windows installer 5.0 version is installed is this an issue ?
Srikanth.kls
I am trying to install the above but am getting the following errors when its attempting to install the setup support files,
This is the first error that occurs during installation of the setup support files
TITLE: Microsoft SQL Server 2008 R2 Setup
------------------------------
The following error has occurred:
The installer has encountered an unexpected error. The error code is 2337. Could not close file: Microsoft.SqlServer.GridControl.dll GetLastError: 0.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1&EvtType=0xDF039760%25401201%25401
This is the second error that occurs after clicking continue in the installer after the first error is generated
TITLE: Microsoft SQL Server 2008 R2 Setup
------------------------------
The following error has occurred:
SQL Server Setup has encountered an error when running a Windows Installer file.
Windows Installer error message: The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
Windows Installer file: C:Userswatto_ukDesktopIn-DigitalSoftwareMicrosoftSQL Server 2008 R21033_ENU_LPx64setupsqlsupport_msiSqlSupport.msi
Windows Installer log file: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20110713_205508SqlSupport_Cpu64_1_ComponentUpdate.log
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1&EvtType=0xDC80C325
These errors are generated from an ISO package downloaded from Microsoft. I have also tried using the web platform installer to install the express version instead but the SQL Server Installation fails with that also. The management studio installs fine but not the server. I have checked to make sure that the Windows Installer is started and it is. Cant seem to find an answer for this anywhere as all previous reported issues appear to be related to XP. I did have the express edition installed on the machine previously but uninstalled it to upgrade to the full version, I wish I hadn’t now.
Can anyone kindly offer any advice or point me in the right direction to stop me going insane with this?
Any advice will be appreciated.
Update=======================
After digging a bit deeper ive located details of the error from the setup log file, i can also upload the log file if required.
MSI (s) (E8:28) [23:35:18:705]: Assembly Error:The module '%1' was expected to contain an assembly manifest.
MSI (s) (E8:28) [23:35:18:705]: Note: 1: 1935 2: 3: 0x80131018 4: IStream 5: Commit 6:
MSI (s) (E8:28) [23:35:18:705]: Note: 1: 2337 2: 0 3: Microsoft.SqlServer.GridControl.dll
MSI (s) (E8:28) [23:35:22:869]: Product: Microsoft SQL Server 2008 R2 Setup (English) -- Error 2337. The installer has encountered an unexpected error. The error code is 2337. Could not close file: Microsoft.SqlServer.GridControl.dll GetLastError: 0.
MSI (s) (E8:28) [23:35:22:916]: Internal Exception during install operation: 0xc0000005 at 0x000007FEE908A23E.
MSI (s) (E8:28) [23:35:22:916]: WER report disabled for silent install.
MSI (s) (E8:28) [23:35:22:932]: Internal MSI error. Installer terminated prematurely.
Error 2337. The installer has encountered an unexpected error. The error code is 2337. Could not close file: Microsoft.SqlServer.GridControl.dll GetLastError: 0.
MSI (s) (E8:28) [23:35:22:932]: MainEngineThread is returning 1603
MSI (s) (E8:58) [23:35:22:932]: RESTART MANAGER: Session closed.
Installer stopped prematurely.
MSI (c) (0C:14) [23:35:22:947]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (0C:14) [23:35:22:947]: MainEngineThread is returning 1601
=== Verbose logging stopped: 13/07/2011 23:35:22 ===
Did you try using Google for that error code? I found several different things to try immediately after doing that…
Was this post helpful?
thumb_up
thumb_down
Also review the setup logs Opens a new window Opens a new window for SQL Server. This may provide more information.
Was this post helpful?
thumb_up
thumb_down
yes i tried many things
after i tried editing regedit using as per link below
http://kb.act.com/app/answers/detail/a_id/27663/~/installation-of-microsoft%C2%AE-sql-server%C2%AE-2008-r2-fails-with-error-generating-xml Opens a new window
the above error disappeared but got a new error
SQL Server Setup has encountered the following error:
Invoke or BeginInvoke cannot be called on a control until the window handle has been created..
Was this post helpful?
thumb_up
thumb_down
i tried with the above links but not worked
i tried installing sql2008 sp4 and even
sql2008 sp
1
error the handle is invalid
now i am getting the previous error of used by another process
below r the details from the log folder file wise
hope this can give the exact solution
in SQL log folder
in Detail_LandingPage
i get the below details
2018-06-08 16:38:49 Slp: Running Action: ValidateChainerSetting
2018-06-08 16:38:51 Slp: — PidPublicConfigObject : ValidateSettings is normalizing input pid=[PID value hidden]
2018-06-08 16:38:51 Slp: — PidPrivateConfigObject : NormalizePid found null or empty pid
2018-06-08 16:38:51 Slp: — PidPublicConfigObject : ValidateSettings proceeding with normalized pid=[PID value hidden]
2018-06-08 16:38:51 Slp: — PidPrivateConfigObject : Initialize is initializing using input pid=[PID value hidden]
2018-06-08 16:38:51 Slp: — PidPrivateConfigObject : NormalizePid found null or empty pid
2018-06-08 16:38:51 Slp: — PidPrivateConfigObject : Initialize proceeding with normalized pid=[PID value hidden]
2018-06-08 16:38:51 Slp: — PidPrivateConfigObject : Initialize output editionId=EXPRESS_ADVANCED(0xF807B7DF)
2018-06-08 16:38:52 Slp: — PidPublicConfigObject : ValidateSettings initialized private object, result is initializeResult=Success
2018-06-08 16:38:52 Slp: Completed Action: ValidateChainerSetting, returned True
2018-06-08 16:38:52 Slp: ———————————————————————-
2018-06-08 16:38:52 Slp: Running Action: ProcessFeatureCommandLineArguments
2018-06-08 16:38:52 Slp: —————————————-
2018-06-08 16:38:52 Slp: Completed Action: ProcessFeatureCommandLineArguments, returned True
2018-06-08 16:38:52 Slp: ———————————————————————-
2018-06-08 16:38:52 Slp: Running Action: ProcessMediaFeatureConfigFileArguments
2018-06-08 16:38:52 Slp: Completed Action: ProcessMediaFeatureConfigFileArguments, returned True
2018-06-08 16:38:52 Slp: ———————————————————————-
2018-06-08 16:38:52 Slp: Running Action: ProcessFeatureConfigFileArguments
2018-06-08 16:38:52 Slp: Completed Action: ProcessFeatureConfigFileArguments, returned True
2018-06-08 16:38:52 Slp: ———————————————————————-
2018-06-08 16:38:52 Slp: Running Action: ValidateSettingsAgainstScenario
2018-06-08 16:38:52 Slp: Scenario: LandingPage
2018-06-08 16:38:52 Slp: Completed Action: ValidateSettingsAgainstScenario, returned True
2018-06-08 16:38:52 Slp: ———————————————————————-
2018-06-08 16:38:52 Slp: Running Action: LandingPage
2018-06-08 16:38:52 Slp: Landing page action
2018-06-08 16:38:52 Slp: Starting Landing Page: Path = e:c6fe5772b61a4f9135cf355e249c78x64LandingPage.exe, Arguments = /MEDIASOURCE=»e:c6fe5772b61a4f9135cf355e249c78\»
in Summary_LandingPage
below details
Package properties:
Description: SQL Server Database Services 2008
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 0
Installation location: e:c6fe5772b61a4f9135cf355e249c78x64setup
Installation edition: EXPRESS_ADVANCED
User Input Settings:
ACTION: LandingPage
CONFIGURATIONFILE:
HELP: False
INDICATEPROGRESS: False
MEDIASOURCE: e:c6fe5772b61a4f9135cf355e249c78
QUIET: False
QUIETSIMPLE: False
X86: False
Configuration file: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20180608_163803ConfigurationFile.ini
Detailed results:
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: The rule result report file is not available.
in Detail_GlobalRules log
2018-06-08 16:46:52 Slp: The following exception occurred while preparing status logs during Watson failure processing: Unable to generate a temporary class (result=1).
error CS1567: Error generating Win32 resource: The process cannot access the file because it is being used by another process.
2018-06-08 16:46:52 Slp: Sco: Attempting to write hklm registry key SOFTWAREMicrosoftMicrosoft SQL Server to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20180608_163918Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2018-06-08 16:46:52 Slp: Sco: Unable to write hklm registry key SOFTWAREMicrosoftMicrosoft SQL Server to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20180608_163918Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_, Win32 error 2
2018-06-08 16:46:52 Slp: Sco: Attempting to write hklm registry key SOFTWAREMicrosoftWindowsCurrentVersionUninstall to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20180608_163918Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2018-06-08 16:46:53 Slp: Sco: Attempting to write hklm registry key SOFTWAREMicrosoftMSSQLServer to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20180608_163918Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2018-06-08 16:46:53 Slp: Sco: Attempting to write hklm registry key SOFTWAREWow6432NodeMicrosoftMicrosoft SQL Server to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20180608_163918Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
2018-06-08 16:46:53 Slp: Sco: Unable to write hklm registry key SOFTWAREWow6432NodeMicrosoftMicrosoft SQL Server to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20180608_163918Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_, Win32 error 2
2018-06-08 16:46:53 Slp: Sco: Attempting to write hklm registry key SOFTWAREWow6432NodeMicrosoftWindowsCurrentVersionUninstall to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20180608_163918Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2018-06-08 16:46:53 Slp: Sco: Attempting to write hklm registry key SOFTWAREWow6432NodeMicrosoftMSSQLServer to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20180608_163918Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2018-06-08 16:46:53 Slp: Sco: Unable to write hklm registry key SOFTWAREWow6432NodeMicrosoftMSSQLServer to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20180608_163918Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_, Win32 error 2
2018-06-08 16:46:53 Slp: Unable to generate a temporary class (result=1).
error CS1567: Error generating Win32 resource: The process cannot access the file because it is being used by another process.
2018-06-08 16:46:54 Slp: The following exception occurred during Watson failure processing: Unable to generate a temporary class (result=1).
error CS1567: Error generating Win32 resource: The process cannot access the file because it is being used by another process.
2018-06-08 16:46:54 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2018-06-08 16:46:54 Slp: Sco: Attempting to open registry subkey SoftwareMicrosoftPCHealthErrorReportingDWInstalled
2018-06-08 16:46:54 Slp:
2018-06-08 16:46:54 Slp: ———————————————————————-
2018-06-08 16:46:54 Slp:
2018-06-08 16:46:54 Slp: Error result: 2064843076
2018-06-08 16:46:54 Slp: Result facility code: 787
2018-06-08 16:46:54 Slp: Result error code: 324
Was this post helpful?
thumb_up
thumb_down
Random thought: Have you tried executing the installer using Run As Administrator?
Was this post helpful?
thumb_up
thumb_down
davidr4
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
habanero
Tried restarting? Tried using Process Monitor to see what is actually using the file? Disable Antivirus?
Was this post helpful?
thumb_up
thumb_down
yes it was run as administrator only
Was this post helpful?
thumb_up
thumb_down
1. Make sure Windows 7 has Service Pack 1 installed and let it update.
2. Make sure you are installing SQL Server 2008 R2 SP 3. —> SQL Server 2008 (non R2) is not supported on Windows 7.
Your title says 2008 R2 but everything else you posted says 2008.
Was this post helpful?
thumb_up
thumb_down
Sounds like this guy had the exact same issue Opens a new window Opens a new window
1. Re-extract the contents to an another drive where you have full permission.
– or –
2. To set proper rights for the User on the Temp location. Go to the above Temp location and Right-click on the Temp folder, and select Properties, go to Securities tab. Under the “Groups or user names:” section just check if your user name is there. Select the user name and make sure it should have “Full Control” selected under the “Permissions for Administrators”. If it’s not then click on the Edit button and provide Full rights to the user account.
Boiled down to perms for the temp files… Just be sure whichever version you are installing supports Windows 7. as per Fessors response. I prefer server OS for SQL…
Was this post helpful?
thumb_up
thumb_down
issue resolved
i installed sql 2008 r2 . windows SP1 was reinstalled on the system. after which SQL 2008 r2 got installed
i had got below error when installing agsin
SQL Server Setup has encountered the following error:
Invoke or BeginInvoke cannot be called on a control until the window handle has been created..
but jst closed the error restarted the system and got it working
thanks for all the replies and support
Was this post helpful?
thumb_up
thumb_down
While creating one of many Lync scenario labs, I chose to install SQL Server 2012 instead of my usual install of SQL 2008 on Windows Server 2012. Going about my happy routine after clicking install, I expected install to complete when I returned a few hours later. Murphy never fails though. And here I am looking at install error instead!
The error read:
TITLE: Microsoft SQL Server 2012 Setup
——————————The following error has occurred:
Error while enabling Windows feature : NetFx3, Error Code : -2146498298 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0x681D636F%25401428%25401
So it wants me to install NetFx3. Should be easy. The requirement basically meant it needed .Net Framework 3.5. All I have to do is run the following from PowerShell:
Add-WindowsFeature NET-Framework-Core
Well, what do I know? It gave me an error too!
Add-WindowsFeature : The request to add or remove features on the specified server failed.
Installation of one or more roles, role services, or features failed.
The source files could not be downloaded.
Having seen this error, I knew what I had to do but let me illustrate. When you run the following at PowerShell prompt, you will notice that not only the “Installed” state is set to “False” indicating it’s not installed but “InstallState” states “Removed”:
Get-WindowsFeature Net-Framework-Core | FT name,install*
Name Installed InstallState
—- ——— ————
NET-Framework-Core False Removed
All it means is that the standard install of Windows Server 2012 does not even install binaries required to enable feature. If you want to install this feature, you will need side-by-side assembly source, usually the installation media. If you are curious about what side-by-side means, check out wiki article here.
The solution here sounds simple. Just run:
Add-WindowsFeature NET-Framework-Core -Source D:sourcessxs
This assumes D is your CD drive which has Windows Server 2012 installation media. Now I should warn you, this won’t work if you have run Windows Update and applied patches after installing Windows Server 2012 and before trying to install SQL Server 2012! If you want answer to obvious “why?”, you should read my previous post explaining how to resolve Error: 0x800f0906 adding Windows features.
Don’t you love rabbit holes we deal with in IT? 
Related
- Share: