Tuesday, March 27, 2012

Can't start the MSSQLServer

Sudenly my MSSQLServer stop initilizing.
Error 1069: Error initializing Session
|Any body knows what I can do?
From the command-prompt, NET HELPMSG 1069 returns 'The service did not start
due to a logon failure'. I suggest you validate that the SQL Server service
account and password are correct.
Hope this helps.
Dan Guzman
SQL Server MVP
"Lina Manjarres" <LinaManjarres@.discussions.microsoft.com> wrote in message
news:5F9DB90B-815E-4A35-B277-1FF84E6DF08C@.microsoft.com...
> Sudenly my MSSQLServer stop initilizing.
> Error 1069: Error initializing Session
> |Any body knows what I can do?
|||Thank you Dan.
What I did was to save again the SQL user password and it did work.
Later on, it happend on another machine, so I did the same procedure and it
worked.
Do you know how can I avoid that to happened again?
Thanks a lot!
Lina
"Dan Guzman" wrote:

> From the command-prompt, NET HELPMSG 1069 returns 'The service did not start
> due to a logon failure'. I suggest you validate that the SQL Server service
> account and password are correct.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Lina Manjarres" <LinaManjarres@.discussions.microsoft.com> wrote in message
> news:5F9DB90B-815E-4A35-B277-1FF84E6DF08C@.microsoft.com...
>
>
|||> Do you know how can I avoid that to happened again?
I use an account dedicated for SQL Server services with 'password never
expires'.
Hope this helps.
Dan Guzman
SQL Server MVP
"Lina Manjarres" <Lina Manjarres@.discussions.microsoft.com> wrote in message
news:210D1BCD-BBBA-42B5-8446-5066C8BC1A75@.microsoft.com...[vbcol=seagreen]
> Thank you Dan.
> What I did was to save again the SQL user password and it did work.
> Later on, it happend on another machine, so I did the same procedure and
> it
> worked.
> Do you know how can I avoid that to happened again?
> Thanks a lot!
> Lina
> "Dan Guzman" wrote:
|||Make sure your AD Domain Administrators have designated a seperate SQL
Server OU. From this, you need to block any Group Policies that may be
affecting your service accounts: password resets, complexity rules, lockout
rules, lockout durations, etc. Service Accounts need a different
configuration.
Sincerely,
Anthony Thomas

"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:OVyvQdk5EHA.1404@.TK2MSFTNGP11.phx.gbl...
> Do you know how can I avoid that to happened again?
I use an account dedicated for SQL Server services with 'password never
expires'.
Hope this helps.
Dan Guzman
SQL Server MVP
"Lina Manjarres" <Lina Manjarres@.discussions.microsoft.com> wrote in message
news:210D1BCD-BBBA-42B5-8446-5066C8BC1A75@.microsoft.com...[vbcol=seagreen]
> Thank you Dan.
> What I did was to save again the SQL user password and it did work.
> Later on, it happend on another machine, so I did the same procedure and
> it
> worked.
> Do you know how can I avoid that to happened again?
> Thanks a lot!
> Lina
> "Dan Guzman" wrote:

No comments:

Post a Comment