SQL Server Management Studio 18.11.1 Errors Galore!

-

 While attempting to upgrade SSMS to version 18.11.1, it kept failing with a very odd error I'd never run across before. 

"MainViewModel.OnBundleAction: Bundle action failed: Fatal error during installation (0x80070643)"

After trying many of the tips on the web like updating Visual C++ Redistributable, running a .NET repair, etc., I finally found the solution.

I fired up trusty old Procmon64 and let it capture while I attempted to install SSMS 18.11.1. Once it failed, I went to Tools \ Count Occurrences and chose "Result". 

The count showed 222 "Access Denied" results.











I double-clicked that line which took me to the list of "Access Denied". I found the ones that were the culprit. Evidently, SSMS 18.11.1 needs to install some help files and it couldn't access the HelpLibrary2 folder.



My assumption was the permissions were incorrect, so I addressed that by running the following command from an elevated CMD prompt:

icacls.exe C:\ProgramData\Microsoft\HelpLibrary2\ /inheritance:e /T

Note: I've had issues running certain icacls.exe commands from a PowerShell window, so be sure to use a CMD prompt instead.

This sets the folder, subfolders, and files back to the original permissions.

Note: You may need to do a takeown.exe /F C:\ProgramData\Microsoft\HelpLibrary2\ /R first to take ownership of the folder structure.

I ran the SSMS install and was able to install successfully! But victory was short lived.

When I tried launching my newly installed SSMS 18.11.1, I got a weird error I'd never seen before.

"The application has failed to start because its side-by-side configuration is incorrect."

After a lot of searching, the conventional wisdom was to install an older version of SSMS, uninstall it, then attempt to install SSMS 18.11.1 again. Easy enough, I thought. So, I downloaded SSMS 18.10 and attempted to install it. 

Much to my chagrin, I got another error. 

"A certificate was explicitly revoked by its issuer (0x800B010C)".

What in tarnation? How many hoops am I going to have to jump through?

So, after much research, I came across this solution which did the trick. The steps involve downloading a tool from Kaspersky, extracting it, and running a few commands to import third-party trusted root certificates.

Here is what I did. I downloaded the tool and ran the below command from an elevated CMD prompt.

It expanded rootsupd.exe and several .sst files to the C:\rootsupd folder.
c:\rootsupd.exe /c /t:C:\rootsupd

Next, I ran these commands to import the roots and remove the bad ones.
c: \rootsupd\rootsupd.exe authroots.sst
c: \rootsupd\rootsupd.exe roots.sst
c: \rootsupd\rootsupd.exe -d delroots.sst

Voila! SSMS 18.10 installed. I then updated successfully to 18.11.1.

Note: It is possible I could have just gone straight to 18.11.1 after the last step, but I didn't attempt it.

Another day, another mystery solved!







Comments

Post a Comment

Popular posts from this blog

ConfigMgr Task Sequence Fails Immediately with "The software could not be found on any servers at this time."

-
Image
Happy Monday, fellow ConfigMgr administrators! I ran across a pretty difficult Task Sequence last week that had me scratching my head. It involved a pretty complex Task Sequence that contained over 50 applications. The Task Sequence would fail within 5 seconds upon launch from the Software Center with an message of  “The software could not be found on any servers at this time.” No error code was given. I ended up removing all the apps from the TS and adding them back one at a time. Many of the applications had at least one supersedence, dependencies and dependency chaining. It turned out there was one particular superseded application that  was missing its content!! Yeah, that would do it. Unfortunately, ConfigMgr did not log what application or package ID had its content missing so it was a crap shoot trying to find it.  I really feel like there should have been a log somewhere that gave this information. This is the only log information I coul
Read more

Delivery Optimization in Microsoft Endpoint Configuration Manager (ConfigMgr)

-
Image
Delivery Optimization can be a powerful tool to help manage your content. However, getting things configured can be confusing and daunting. Here I've broken out the steps to get you going. Client Settings 1.     BranchCache and PeerCache. a.    First, create a new Custom Device Settings and check the box for “Client Cache Settings” and “Delivery Optimization”. b.       BranchCache . To enable BranchCache on clients, set “Configure BranchCache” and “Enable BranchCache” to Yes and set the “Maximum BranchCache cache size (percentage of disk)”. (Default is 10). c.        PeerCache . To make the client a SuperPeer (PeerCache Source), set “Enable as peer cache source” to “Yes”. Note: SuperPeers should be clients that are newer (faster), always on devices, that are hard wired, and have plenty of hard drive space. Note: Build a WQL query to create and maintain a collection of SuperPeers. I.E., CPU, memory, free space, etc.   2.     Delivery Optimization and Microsoft Con
Read more
-
News Update Windows Update for Business Reports If you are using Windows Update for Business (WUfB) to manage updates for your devices, you may want to know how well they are performing and what issues they are facing. WUfB Reports can help you with that. WUfB Reports are a set of dashboards and reports that provide insights into the update status, compliance, and health of your devices. You can access them from the Microsoft Endpoint Manager admin center or the Microsoft 365 admin center. Some of the benefits of using WUfB Reports are: You can see the update compliance and deployment progress of your devices across different rings and policies. You can identify devices that are missing updates, have update errors, or are out of support. You can troubleshoot update issues by drilling down into the details of each device and update. You can export the data to Excel or Power BI for further analysis and reporting. To use WUfB Reports, you need to have devices enrolled in Microsoft Intune
Read more