Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, December 6, 2018 6:10 PM
When attempting to install Office Standard 2019, I immediately receive a popup with Error Code: 30041-1039 (0). I am not seeing anything specific to this error online.
The system currently has volume license installs (MSI) of Office Standard 2016, Visio Standard 2016, Project Professional 2016, Skype for Business 2016:
Any advice?
This is the config.xml. Which was built using https://config.office.com
<Configuration>
<Add OfficeClientEdition="32" Channel="PerpetualVL2019" SourcePath="\XXXXXXX\Office 2019 Standard\Install" AllowCdnFallback="TRUE" ForceUpgrade="TRUE">
<Product ID="Standard2019Volume">
<Language ID="en-us" />
</Product>
</Add>
<Updates Enabled="TRUE" />
<RemoveMSI>
<IgnoreProduct ID="VisPro" />
<IgnoreProduct ID="VisStd" />
<IgnoreProduct ID="PrjPro" />
<IgnoreProduct ID="PrjStd" />
</RemoveMSI>
<AppSettings>
<Setup Name="Company" Value="XXXXXXX" />
</AppSettings>
<Display Level="Full" AcceptEULA="TRUE" />
<Logging Level="Standard" Path="c:\Office 2019\Install_Log\ />
</Configuration>
The install log has the following ERRORS.
12/06/2018 09:26:28.149 SETUP (0x49c8) 0x1864 Click-To-Run Non Task Error ckrgv Unexpected PerformMSITransitions::HandleStateAction {"MachineId": "dd706fdd4a7fc64dXXXXXXXXXXXXXX", "SessionID": "731bbf1a-0982-408e-8b37-XXXXXXXXXX", "GeoID": 244, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ErrorCode": 30041, "ErrorType": "InvalidProductInConfigXml", "AppVErrorSource": "", "ErrorMessage": "InvalidProductInConfigXml (PerformMSITransitions::HandleStateAction MSI C2R SxS prereq is predicted to fail.)", "ErrorDetails": "", "ContextData": "OException has occurred."}
12/06/2018 09:26:28.149 SETUP (0x49c8) 0x1864 Click-To-Run aoh71 Medium BootstrapperState::OnError: Error has occured. Go to ExitBootStateMachine.
12/06/2018 09:26:28.152 SETUP (0x49c8) 0x1864 Click-To-Run General Telemetry aoh9f Medium TryShowUI::HandleStateAction {"MachineId": "dd706fdd4a7fc64d8687ec550cc66c51", "SessionID": "731bbf1a-0982-408e-8b37-4b2ad6deb447", "GeoID": 244, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "Showing failure UI."}
12/06/2018 09:26:28.154 SETUP (0x49c8) 0x1864 Click-To-Run General Telemetry a50py Medium TryShowUI::HandleStateAction {"MachineId": "dd706fdd4a7fc64d8687ec550cc66c51", "SessionID": "731bbf1a-0982-408e-8b37-4b2ad6deb447", "GeoID": 244, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "{'ErrorUrl':'https://officeredir.microsoft.com/r/rlidOfficeWebHelp?p1=OCSAC2RBootstrapper&ver=16&clid=1033&helpid=%2230041-1039-0%22&app=webview','ErrorCode':'30041','ErrorSource':'1039'}"}
All replies (3)
Friday, December 7, 2018 9:25 AM ✅Answered
Hi,
Unfortunately, it’s not a supported scenario for installing Office 2019 with volume license versions (MSI) of Office 2016, Project 2016, and Visio 2016 on the same computer. They use different installation technologies (Click-to-Run and MSI), but they are the same version (16.0). For more information, please refer to Supported scenarios for installing different versions of Office, Project, and Visio on the same computer.
If you want to install Office 2019 to work with Visio 2016 and Project 2016, please remove Office 2016, Visio 2016 and Project 2016, then use the Office Deployment Tool to install volume licensed versions of Project 2016 and Visio 2016.
Best Regards,
Herb
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams
Friday, December 14, 2018 9:46 AM
Hi,
Have you resolved this issue? Do you have any update for it? Anything unclear, feel free to let us know.
Best Regards,
Herb
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams
Thursday, May 23, 2019 11:15 AM
Dear Herb,
Sorry that I raise this thread up again.
Any idea why MS offers the <IgnoreProduct ID> attribute as a RemoveMSI option for the config.xml file?
/en-us/deployoffice/configuration-options-for-the-office-2016-deployment-tool
BR
Daniel