Account Lockout on SQL2005

Hi Champs,
Is there a way to recover from a account lockout in SQL2005?
I cannot connect to "Database Engine" in "SQL Server Management Studio",
error: login failed...18456.
And I also cannot start the "SQL Server agent service"
Any possebility to recover without reinstall?
/Many thanksKurlan wrote:
> Hi Champs,
> Is there a way to recover from a account lockout in SQL2005?
> I cannot connect to "Database Engine" in "SQL Server Management Studio",
> error: login failed...18456.
> And I also cannot start the "SQL Server agent service"
> Any possebility to recover without reinstall?
>
> /Many thanks
Start from here
http://blogs.msdn.com/sql_protocols.../21/536201.aspx
Regards
Amish Shah|||Hi
If your issue is that a windows account has been locked contact the system
administrator to unlock it through the active directory user management
tools. If this is a SQL login then you can uncheck the account locked box on
the status screen under the account details of the security branch in SQL
Management Studio.
You don't give any error messages that come up when you try and start SQL
agent! If you are using a domain account as the service account, then try
switching to local system and see if it will start, you can then switch back
once you have validated that the account you are using is ok.
If this does not work check out the SQL Agent Log File to see if there are
any information there.
John
"Kurlan" wrote:

> Hi Champs,
> Is there a way to recover from a account lockout in SQL2005?
> I cannot connect to "Database Engine" in "SQL Server Management Studio",
> error: login failed...18456.
> And I also cannot start the "SQL Server agent service"
> Any possebility to recover without reinstall?
>
> /Many thanks|||Yes it is the SQL account.
I cannot access SQL Management Studio, so I cannot access the SQL accounts.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> If your issue is that a windows account has been locked contact the system
> administrator to unlock it through the active directory user management
> tools. If this is a SQL login then you can uncheck the account locked box
on
> the status screen under the account details of the security branch in SQL
> Management Studio.
> You don't give any error messages that come up when you try and start SQL
> agent! If you are using a domain account as the service account, then try
> switching to local system and see if it will start, you can then switch ba
ck
> once you have validated that the account you are using is ok.
> If this does not work check out the SQL Agent Log File to see if there are
> any information there.
> John
> "Kurlan" wrote:
>|||Hi
You can also use the T-SQL command ALTER LOGIN with the UNLOCK option when
setting the password.
John
"Kurlan" wrote:
[vbcol=seagreen]
> Yes it is the SQL account.
> I cannot access SQL Management Studio, so I cannot access the SQL accounts
.
>
> "John Bell" wrote:
>|||in order to run a t-sql, I have to have connection to either the management
consol or via sqlcmd, and I get access denied in both cases.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You can also use the T-SQL command ALTER LOGIN with the UNLOCK option when
> setting the password.
> John
> "Kurlan" wrote:
>|||Kurlan wrote:[vbcol=seagreen]
> Yes it is the SQL account.
> I cannot access SQL Management Studio, so I cannot access the SQL accounts.[/vbcol
]
Why do you need Management Studio to change the service account?
Start -> Administrative Tools -> Services, go to the properties for the
MSSQLSERVICE, configure it to run as the Local System account.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi
If you log in on the same machine as SQL Server is running as an
administrator you should be able to log in with a trusted connection (-E
option for SQLCMD or OSQL). You should also be able to log into management
studio this way. If not type in NET START at a command prompt to make sure
the SQL Server is running.
John
"Kurlan" wrote:
[vbcol=seagreen]
> in order to run a t-sql, I have to have connection to either the managemen
t
> consol or via sqlcmd, and I get access denied in both cases.
> "John Bell" wrote:
>