For some reason, I have been unable to create new SSMS 2008 projects or open existing projects without getting a "Class Not Registered" exception or simply an empty project/solution window. I did see a response from a fellow MVP that suggested I need to apply SQL Server 2008 Customer Update 1 (CU1) but not before I had attempted to "repair" my existing installation. Unfortunately, this triggered a number of other issues as discussed below:
- SQL Server 2008 Setup (don't you love it--we always seem to come back to setup issues) would not install because a reboot was required--even after repeated reboots--dead end.
- Setup would run in Safe Mode but complained of a missing Windows Installer--dead end.
- A search on Google turned up a MSDN Forum response that discussed registry corruption. Note that I found the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager" then deleting the value of "PendingFileRenameOperations" worked where none of the other referenced settings made any difference.
- Once setup ran the behavior of SSMS returned to normal (AFA the New Project and Open Project functionality were concerned). However, Setup throws a number of exceptions--possibly due to the fact I've installed Visual Studio SP1 that (possibly) pooched the bits in the first place. I still can't install the CU1 on one of two systems.
On a side note, have you seen the (seemingly endless) list of stuff fixed in the 174MB CU1? Holy moley, there is a lot of really basic problems here including VIEWS with ORDER BY returning randomly sequenced rows and reports showing glyphs instead of data. How did these get through QC? Oh, sorry, I know the answer. Not enough time taken for testing. The marketing folks had already rented the hotel ballrooms for the launch... Yes, I plan to install CU1, but only after my two User Group talks this week.
