SSDT 2017 Setup Failed The configuration registry key could not be opened

  • A+
Category:Languages

We have been using VS 2017 Shell version for BI development for a few months without problems but today it stopped unexpectedly and restarted on its own. After the restart, we got an error:

Could not load file or assembly 'Microsoft.DataTransformationServices.Wizards' or one of its dependencies. The system cannot find the file specified.

After some googling, one of our developers decided to uninstall and re-install SSDT for VS 2017 from the Microsoft site, but the setup fails:

The configuration registry key could not be opened(0x800703F3)

I googled some more and found that a force uninstall could help but it did not.

Here is the part of the setup log when errors started:

[1F4C:3708][2018-05-08T17:40:36]e000: Error 0x800703f3: Process returned error: 0x3f3 [1F4C:3708][2018-05-08T17:40:36]e000: Error 0x800703f3: Failed to execute EXE package. [2EBC:3250][2018-05-08T17:40:36]e000: Error 0x800703f3: Failed to configure per-machine EXE package. [2EBC:3250][2018-05-08T17:40:36]i000: MainViewModel.OnPackageAction: Install Completed for package SQL Server Analysis Services (id: Microsoft.DataTools.AnalysisServices) [2EBC:3250][2018-05-08T17:40:36]i319: Applied execute package: Microsoft.DataTools.AnalysisServices, result: 0x800703f3, restart: None [2EBC:3250][2018-05-08T17:40:36]e000: Error 0x800703f3: Failed to execute EXE package. [1F4C:3708][2018-05-08T17:40:36]i329: Removed package dependency provider: Microsoft.DataTools.AnalysisServices, package: Microsoft.DataTools.AnalysisServices [1F4C:3708][2018-05-08T17:40:36]i351: Removing cached package: Microsoft.DataTools.AnalysisServices, from path: C:/ProgramData/Package Cache/9864EE5369359DB622D0234B6C6B7640B949140C/ [2EBC:3250][2018-05-08T17:40:36]i000: MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 100 [1F4C:3708][2018-05-08T17:40:36]i372: Session end, registration key: SOFTWARE/Microsoft/Windows/CurrentVersion/Uninstall/{f55a890f-6c82-4455-9bb5-2a902cdb7d87}, resume: None, restart: None, disable resume: No [1F4C:3708][2018-05-08T17:40:36]i330: Removed bundle dependency provider: {f55a890f-6c82-4455-9bb5-2a902cdb7d87} [1F4C:3708][2018-05-08T17:40:36]i352: Removing cached bundle: {f55a890f-6c82-4455-9bb5-2a902cdb7d87}, from path: C:/ProgramData/Package Cache/{f55a890f-6c82-4455-9bb5-2a902cdb7d87}/ [1F4C:3708][2018-05-08T17:40:36]i371: Updating session, registration key: SOFTWARE/Microsoft/Windows/CurrentVersion/Uninstall/{f55a890f-6c82-4455-9bb5-2a902cdb7d87}, resume: None, restart initiated: No, disable resume: No [2EBC:3250][2018-05-08T17:40:36]e000: MainViewModel.OnBundleAction: Bundle action failed: The configuration registry key could not be opened (0x800703F3) [2EBC:3250][2018-05-08T17:40:36]i399: Apply complete, result: 0x800703f3, restart: None, ba requested restart:  No 

Any help would be highly appreciated.

 


Looks like Microsoft is working on a fix.

See:

Comment

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen: