Windows 8.1 with office 2013, attempting to install x.86 32 bit version of BC upgrade 2010. each install fails to install this component mssml.biz. Have attempted everything published on this problem i could find, clean install, run fix it, deleted everything SQL in programs, cleaned out registry, reboot, installed SQL express as stand alone then BC, all fail with same error.  Unit is 100% up to date on all patches. 

Hi,

Thanks for posting your question here, I will be assisting you on this issue.

For getting a better understanding of what has got in the way of installation, we may need to collect installation logs during BCM Setup:

      -  For Windows Installer Setup log

            drive:\setup.exe /l*v c:\Setup_log_name

       - The MSDE Setup log

          MSDE Setup log is automatically created during Setup. You can find it under temp folder with

          name like Msde_setup_number.log (Ex. Msde_setup_1108685580.log)

          click Start, point to  Run, type %temp%, and then click OK.

       - The MSDE configuration log

           The MSDE configuration log is named Cnfgsvr.out. the Cnfgsvr.out log located one of the

           following folders, depending on the version of BCM you are using:

               . Business Contact Manager:

                    C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Install

              . Business Contact Manager Update:

                   C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTSMLBIZ\Install

Please send the log through mail to: ibsofc@microsoft.com.

As youve tried a lot trouble shooting steps already, let not repeating those steps till we have the log.

This Article is a detailed reference for log collecting and some trouble shooting steps which you might already tried.

Thanks for your understanding.

• Edited by Chloe WangModerator Wednesday, March 25, 2015 8:51 AM

Hi,

Thanks for posting your question here, I will be assisting you on this issue.

For getting a better understanding of what has got in the way of installation, we may need to collect installation logs during BCM Setup:

      -  For Windows Installer Setup log

            drive:\setup.exe /l*v c:\Setup_log_name

       - The MSDE Setup log

          MSDE Setup log is automatically created during Setup. You can find it under temp folder with

          name like Msde_setup_number.log (Ex. Msde_setup_1108685580.log)

          click Start, point to  Run, type %temp%, and then click OK.

       - The MSDE configuration log

           The MSDE configuration log is named Cnfgsvr.out. the Cnfgsvr.out log located one of the

           following folders, depending on the version of BCM you are using:

               . Business Contact Manager:

                    C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Install

              . Business Contact Manager Update:

                   C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTSMLBIZ\Install

Please send the log through mail to: ibsofc@microsoft.com.

As youve tried a lot trouble shooting steps already, let not repeating those steps till we have the log.

This Article is a detailed reference for log collecting and some trouble shooting steps which you might already tried.

Thanks for your understanding.

• Edited by Chloe WangMicrosoft employee, Moderator Wednesday, March 25, 2015 8:51 AM

Hi,

Thanks for posting your question here, I will be assisting you on this issue.

For getting a better understanding of what has got in the way of installation, we may need to collect installation logs during BCM Setup:

      -  For Windows Installer Setup log

            drive:\setup.exe /l*v c:\Setup_log_name

       - The MSDE Setup log

          MSDE Setup log is automatically created during Setup. You can find it under temp folder with

          name like Msde_setup_number.log (Ex. Msde_setup_1108685580.log)

          click Start, point to  Run, type %temp%, and then click OK.

       - The MSDE configuration log

           The MSDE configuration log is named Cnfgsvr.out. the Cnfgsvr.out log located one of the

           following folders, depending on the version of BCM you are using:

               . Business Contact Manager:

                    C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Install

              . Business Contact Manager Update:

                   C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTSMLBIZ\Install

Please send the log through mail to: ibsofc@microsoft.com.

As youve tried a lot trouble shooting steps already, let not repeating those steps till we have the log.

This Article is a detailed reference for log collecting and some trouble shooting steps which you might already tried.

Thanks for your understanding.

• Edited by Chloe WangMicrosoft employee, Moderator Wednesday, March 25, 2015 8:51 AM

Hi,

Thanks for posting your question here, I will be assisting you on this issue.

For getting a better understanding of what has got in the way of installation, we may need to collect installation logs during BCM Setup:

      -  For Windows Installer Setup log

            drive:\setup.exe /l*v c:\Setup_log_name

       - The MSDE Setup log

          MSDE Setup log is automatically created during Setup. You can find it under temp folder with

          name like Msde_setup_number.log (Ex. Msde_setup_1108685580.log)

          click Start, point to  Run, type %temp%, and then click OK.

       - The MSDE configuration log

           The MSDE configuration log is named Cnfgsvr.out. the Cnfgsvr.out log located one of the

           following folders, depending on the version of BCM you are using:

               . Business Contact Manager:

                    C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\Install

              . Business Contact Manager Update:

                   C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTSMLBIZ\Install

Please send the log through mail to: ibsofc@microsoft.com.

As youve tried a lot trouble shooting steps already, let not repeating those steps till we have the log.

This Article is a detailed reference for log collecting and some trouble shooting steps which you might already tried.

Thanks for your understanding.

• Edited by Chloe WangMicrosoft employee, Moderator Wednesday, March 25, 2015 8:51 AM

Hi Rob:

Sorry for the late response. After go through the logs you sent me, I found Setup closed with exit code: 0x84C40013 in the SQL setup log. And I did some research found this post might be useful for you.

It might got something to do with .NET Framework 4. The user reported this error, solve the issue by installing the full package of .NET Framework 4. You can read the post for details.

Let me know the result, thank you.

I posted last night the msde in your article was the only published fix i did not try, and last night i installed the stand alone with no errors, will check on .net framwork 4 and post back...thanks Bob

Hi Bob,

I did a test from my local environment. OS version: Windows 8.1 64bits, Office 2013:

1. Downloaded BCM from this link
2. First installation failed with Ending a Windows Installer transaction: C:\Users\Administrator\AppData\Local\temp\BcmSetup.en-US\MSSMLBIZ.msi. Client Process Id: 1132. Error logged in Events log.
3. Then I went to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server, renamed Microsoft SQL Server to Microsoft SQL Server.old
4. Reinstalled the BCM, it succeeded.

KB901163 had more detailed troubleshooting steps you can refer to

Let me know the result. Thank you.

• Edited by Chloe WangMicrosoft employee, Moderator 19 minutes ago

Hi Bob,

I did a test from my local environment. OS version: Windows 8.1 64bits, Office 2013:

1. Downloaded BCM from this link
2. First installation failed with Ending a Windows Installer transaction: C:\Users\Administrator\AppData\Local\temp\BcmSetup.en-US\MSSMLBIZ.msi. Client Process Id: 1132. Error logged in Events log.
3. Then I went to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server, renamed Microsoft SQL Server to Microsoft SQL Server.old
4. Reinstalled the BCM, it succeeded.

KB901163 had more detailed troubleshooting steps you can refer to

Let me know the result. Thank you.

• Edited by Chloe WangMicrosoft employee, Moderator Sunday, April 12, 2015 7:07 AM

Hi Bob,

I did a test from my local environment. OS version: Windows 8.1 64bits, Office 2013:

1. Downloaded BCM from this link
2. First installation failed with Ending a Windows Installer transaction: C:\Users\Administrator\AppData\Local\temp\BcmSetup.en-US\MSSMLBIZ.msi. Client Process Id: 1132. Error logged in Events log.
3. Then I went to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server, renamed Microsoft SQL Server to Microsoft SQL Server.old
4. Reinstalled the BCM, it succeeded.

KB901163 had more detailed troubleshooting steps you can refer to

Let me know the result. Thank you.

• Edited by Chloe WangMicrosoft employee, Moderator Sunday, April 12, 2015 7:07 AM

Ok performed, but ended with the same result...will read thru links and see if there is anything else to attempt.

Thanks Bob

Hi,

Sorry for the late response, I tested several times from my side, installation got successful all the time.

Firstly, I will share you the steps I went through:

1. If this is not your first time installation, make sure you removed all the BCM components as well as SQL related feature
2. Downloaded BCM from this link
3. Rename HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server, renamed Microsoft SQL Server to Microsoft SQL Server.old
4. Click the BCM installation

Note: theres no need to install other pre-required features. BCM will download and install all the required applications automatically.

Could you please try above steps, let me know the results.

If it failed, please collect all the BCM related logs under: C:\Users\user name\AppData\Local\Temp(this is the default log path) to me: ibsofc@microsoft.com. (keep the thread url or tittle as the mail subject.

Thanks for your understanding.

Hi,

Sorry for the late response, I tested several times from my side, installation got successful all the time.

Firstly, I will share you the steps I went through:

1. If this is not your first time installation, make sure you removed all the BCM components as well as SQL related feature
2. Downloaded BCM from this link
3. Rename HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server, renamed Microsoft SQL Server to Microsoft SQL Server.old
4. Click the BCM installation

Note: theres no need to install other pre-required features. BCM will download and install all the required applications automatically.

Could you please try above steps, let me know the results.

If it failed, please collect all the BCM related logs under: C:\Users\user name\AppData\Local\Temp(this is the default log path) to me: ibsofc@microsoft.com. (keep the thread url or tittle as the mail subject.

Thanks for your understanding.

• Proposed as answer by Chloe WangMicrosoft employee, Moderator Monday, April 27, 2015 5:28 AM

Hi,

Sorry for the late response, I tested several times from my side, installation got successful all the time.

Firstly, I will share you the steps I went through:

1. If this is not your first time installation, make sure you removed all the BCM components as well as SQL related feature
2. Downloaded BCM from this link
3. Rename HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server, renamed Microsoft SQL Server to Microsoft SQL Server.old
4. Click the BCM installation

Note: theres no need to install other pre-required features. BCM will download and install all the required applications automatically.

Could you please try above steps, let me know the results.

If it failed, please collect all the BCM related logs under: C:\Users\user name\AppData\Local\Temp(this is the default log path) to me: ibsofc@microsoft.com. (keep the thread url or tittle as the mail subject.

Thanks for your understanding.

• Proposed as answer by Chloe WangMicrosoft employee, Moderator Monday, April 27, 2015 5:28 AM
• Unproposed as answer by Chloe WangMicrosoft employee, Moderator 22 hours 38 minutes ago

Hi Bob:

If there no installation logs we couldnt perform further investigation. In this case, Id suggest you contact premier support for further assistance, thanks for your understanding.