Re: KB954606 security update failed



On Jan 15, 1:40 pm, smokie <smo...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I have had the same problem, the cause I think was that I removed all the
built-in Windows logins from SQL server, so only 'sa' login had permissions.
After I put back my Administrator login and assigned it sysadmin role, the
hotfix installed with no problem.

--
Best regards.



"inungh" wrote:
I have SQL server 2005 express verions install and get KB954606
security update failed since Sep/2008.

What should I do for this?
Does it mean that my computer has virus or contorled by someone to
stop me do the update?
Should I uninstall SQL server 2005 express and reinstalled?

Your information is great appreciated,- Hide quoted text -

- Show quoted text -

Thanks for the message,
I did not remove Windows Login.
Can you please let me know how did you put Windows user back?
Is it from SQL server management Studio express and go to users and
check it?


Thanks again,
.



Relevant Pages

  • Re: Windows permissions to run Jet OLEDB 4.0
    ... in SQL Server or not when you have to go outside of the server to the ... Actually I was talking about Windows logins. ... There is no security whatsoever implemented on the mdb ...
    (microsoft.public.data.oledb)
  • Re: sa password
    ... Seems your SQL Server is configured to only accept windows logins. ... > 1) I login to SQL Server thru the query analyzer using Windows ... > 5) I try login to SQL Server thru query analyzer using SQL Server ...
    (microsoft.public.sqlserver.server)
  • Re: "not a trusted connection", means what EXACTLY?
    ... My guess is that the SQL Server is setup to allow only Windows logins and you try to login using a ... SQL server login. ... Tibor Karaszi, SQL Server MVP ...
    (microsoft.public.sqlserver.server)
  • Re: The process could not connect to Subscriber Server2
    ... normally this means that you are trying to use SQL Server security and the ... server is set up to only allow Windows logins. ... make your agent impersonate the SQL Server agent account or alternatively ...
    (microsoft.public.sqlserver.replication)

Quantcast