Please keep in mind that folks reading new questions with the intent to answer are problem-
oriented by nature. They don't look at who is posting, they look at what is posted. Every new
thread gets evaluated on its own merit, which is why I recommend giving clear details about
the entire environment with every new post. You can generate boilerplate to post the details
about your version(s) and service pack(s) so you don't leave anything out, but more
environment and problem details are better than less (though the same is not true about
questions -- multi-question threads tend to get ignored as if they were homework problems).
I've had lots of customers try to revoke all privileges then add them back until the software works,
and not many have been successful. You'll likely need to create a new instance, try following
the instructions again, and if they work the second time, try to determine what went wrong on the
first pass. If they don't work the second time, then the focus will switch to your environment
configuration, since it's not likely that a KB article will have been untested.
I was surprised that there weren't more caveats, like the boilerplate that is provided when a
solution involves a Registry change to a Microsoft host, since revoking privileges incorrectly
can render an instance useless, but the folks who generally insist on such changes aren't likely
to be swayed by the risks of "greater security".
- V
