Automatic Update is your enemy

As contrary to Microsoft recommendation, turning on Automatic Update
may simply lead to diaster as I and many other people have
experienced.

We migrated one of our application to a new Windows 2000 server last
Dec, and a few days later, user began to complaint more and more
frequently. At first we guess it is the configuration problem of that
server since it was newly setup, but it turned out nothing was wrong
after careful examination and comparism between the old server.

So I turned to IIS log for help, users got weird message like
'Transaction cannot have multiple recordsets with this cursor_type.
Change the cursor type, commit the transaction or close one of the
recordsets.". The reason I said weird is there was no such error ever
before, and we didn't change any code or configuration.

Now went into event viewer, I found three Windows patches were
automatically installed that same day the error appeared. They are
hotfix KB885835, KB885836, KB873339, none of them related to ADO or
database.

However, that server is also used for other purposes, we can't
rollback the hotfixes. Therefore we migrated the application to
another server, by now it has been up for three days in a row, not a
single error reported or found.