Hello,
I am trying to install SQL server 2008 on windows server 2012 RC (build 8400) build I got below error
Product: Microsoft SQL Server 2008 Setup Support Files -- Error 1935. An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x80073712. assembly interface: IAssemblyCacheItem, function: Commit, component: {837BF1EB-D770-94EB-A01F-C8B3B9A1E18E}
digging into CBS log i got the following related entries
2012-07-19 19:24:14, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]2012-07-19 19:24:14, Info CBS Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2012-07-19 19:24:14, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2012-07-19 19:24:14, Error CSI 0000008c (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #19530# from CCSDirectTransaction::OperateEnding at index 0 of 3 operations, disposition 0[gle=0xd015001a]
2012-07-19 19:24:14, Error CSI 0000008d (F) HRESULT_FROM_WIN32(14098) #19277# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x80073712]
2012-07-19 19:24:14, Info CBS TiWorker: Client requests SxS store object.
2012-07-19 19:24:14, Info SXS Uninstall Assembly: policy.8.0.Microsoft.VC80.MFCLOC,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32-policy"
2012-07-19 19:24:14, Info SXS Submitting uninstall transaction
2012-07-19 19:24:14, Info CSI 0000008e Performing 1 operations; 1 are not lock/unlock and follow:
Any idea what is going on, is this MSI authoring error or OS file corruption issue ?
If it mainfest corruption issue how can i fix it ?
Should i do OS repair ?
I have tried the following workarounds
Installing VC red 2008
Installing VC red 2008 SP1
Running SFC /SCAN command to fix damaged system files.
Rebooting the machine multiple times.
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.