How can we help you today? How can we help you today?
Miriamka
Finding this post gave me the direction where to look for the solution, almost 7 years later and more advanced versions of red-gate products and MS SQL Server.  I got the same issue when applying latest update for SQL Doc 5 (from SQL Doc 5.2 to SQL Doc 5.2.16). It resulted in the crash of SSMS 17 and SSMS 18, with an error message in the log: "Failed to resolve source for file: C:\Program Files\BMC Software\Client Management\Client\data\PatchManagementPremium\Patches\Jobs\1389\Base\Patches\SSMS-Setup-ENU-Upgrade.exe, error: 0x80070002. Error 0x80070002: Failed while prompting for source (original path 'C:\Program Files\BMC Software\Client Management\Client\data\PatchManagementPremium\Patches\Jobs\1389\Base\Patches\SSMS-Setup-ENU-Upgrade.exe'). Error 0x80070002: Failed while caching, aborting execution."  The situation was that after applying the latest SQL Doc 5 update (version 5.2.16) - the SSMS will come up, but crashed right away when I will try to open Text Editor or try to open Query Explorer. Also, in the end of that update of SQL Doc 5 to latest update (version 5.2.16) the message popped up, requesting to restart the computer, the situation which NEVER happened to me before with any of red-gate products latest updates.  I had to un-install all of red-gate products from our SQL Toolbelt Essential subscription 2022, reinstall SQL Server Management Studio 2017, and re-install again red-gate products back one-by-one, testing every time that SSMS is still working. I updated all of red-gate products to the latest updates, making sure that SQL Doc 5 update was the last. I know that the crash-culprit was the latest update for SQL Doc 5, because the crash of SSMS happened again right away. I discarded the latest update for SQL Doc 5, keeping my working version 5.2.   I am running on: Windows 10 Enterprise, 64-bit operating system, x64-based processor SQL Server Management Studio 2017 (version 17.8.1)  I think it might be something really wrong with the SQL Doc 5 latest update, and red-gate development team should be notified about it. / comments
Finding this post gave me the direction where to look for the solution, almost 7 years later and more advanced versions of red-gate products and MS SQL Server.  I got the same issue when applying ...
0 votes