Udostępnij za pośrednictwem

Surgical removal of Q890175

  • Artykuł

In January we released the Beta version of a new QFE format (Q889402). This format was basically a rollup of all previous SP1 security QFEs. For the same month we also released the security QFEs in their previous format (Q890175), with the idea that if customers had problems with the rollup QFE they could uninstall the package and install the “standalone” versions of the fixes without delay.
However, a problem is encountered if you import Q890175 and Q889402 the same time- CMI throws an error if you try to view the “Packages” tab in Database Manager. To fix the problem you need to install all database entries associated with these two QFE packages:

1. Stop SQL Server service, then backup the .MDF and .LDF database files (typically located in the \Windows Embedded Data folder). This way you can recover your database in case you accidentally delete imported components that you want to keep.
2. Copy this zip file and expand it to a folder of your choice.
3. For MSDE users, launch a command prompt and browse to the location where saved the file Delete_890175.sql.
4. Run the following osql command –“osql -E -S <servername> -i Delete_890175.sql”.
5. For SQL Server users, execute the SQL query contained in Delete_890175.sql.
6. Verify that no errors are reported.
7. Run Database Manager, to confirm that you can inspect Packages without getting CMI errors.
8. Re-import the SP1 rollup 889402.
9. Run Database Manager, to confirm the rollup installed correctly.

- Lynda

Comments

  • Anonymous
    May 10, 2005
    I don't have SQL Server running so I guess I'm an MSDE user. I stopped the service to make the backups. I then tried running the command but it wouldn't work until I restarted the service. How was I to know? I hope this is ok and I didn't do further damage.

    In any case it didn't solve my problem with the CMI errors. I still get an error: A utilities method referenced a non-existent registry key or value. utilitiesc-1259

    Any other possibilities what is causing this?
  • Anonymous
    May 11, 2005
    The comment has been removed
  • Anonymous
    May 13, 2005
    Thank you for your response.

    I believe I had installed Q889402 since it is in my list of installed QFEs together with Q890175. I tried your suggestion. There were no errors when running the script again (there were none before) but there is no change as far as the DBM. I now installed 893086. Is this the latest rollup? Since I ran your script I can now open my slx file in TD which before I used your Delete_890175.sql file was not opening anymore. Thanks for that.
    Dan
  • Anonymous
    May 14, 2005
    Dan,

    Shoot your e-mail address to wecrt@microsoft.com so we can take this offline (and track it)and I will investigate this further and get back to you as soon as possible.

    Lynda
  • Anonymous
    June 16, 2009
    PingBack from http://fixmycrediteasily.info/story.php?id=15288