Local DB's refuse to start

Last week my local DB's got hosed, so over the weekend, I reinstalled them
(2000 & 2005). However, I was away and connected to a different network (IP
change) when I reinstalled the servers (yes, I know it was screwy, but thats
what I did).
Now, back at work, everythin is fine remotly, however, my local instances of
SQL Server refuse to start, the message is:
The service did not start due to a logon failure.
-and-
An error 1069 - (The service did not start due to a logon failure.)
occured while performing this service operation on the MSSQLServer service.
I use the same DOMAIN\Login whether connected internally, or not.
--
Am I going to have to reinstall while connected to the domain?
Thanks,
JayCheck if the user account that runs the SQL Server service has a changed
password or an expired password.
Linchi
"Jay" wrote:
> Last week my local DB's got hosed, so over the weekend, I reinstalled them
> (2000 & 2005). However, I was away and connected to a different network (IP
> change) when I reinstalled the servers (yes, I know it was screwy, but thats
> what I did).
> Now, back at work, everythin is fine remotly, however, my local instances of
> SQL Server refuse to start, the message is:
> The service did not start due to a logon failure.
> -and-
> An error 1069 - (The service did not start due to a logon failure.)
> occured while performing this service operation on the MSSQLServer service.
>
> I use the same DOMAIN\Login whether connected internally, or not.
> --
> Am I going to have to reinstall while connected to the domain?
> Thanks,
> Jay
>
>|||Nope, I installed the servers under my domain account.
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:B53CBAAC-1C38-450D-8623-61CC7BA9273A@.microsoft.com...
> Check if the user account that runs the SQL Server service has a changed
> password or an expired password.
> Linchi
> "Jay" wrote:
>> Last week my local DB's got hosed, so over the weekend, I reinstalled
>> them
>> (2000 & 2005). However, I was away and connected to a different network
>> (IP
>> change) when I reinstalled the servers (yes, I know it was screwy, but
>> thats
>> what I did).
>> Now, back at work, everythin is fine remotly, however, my local instances
>> of
>> SQL Server refuse to start, the message is:
>> The service did not start due to a logon failure.
>> -and-
>> An error 1069 - (The service did not start due to a logon failure.)
>> occured while performing this service operation on the MSSQLServer
>> service.
>>
>> I use the same DOMAIN\Login whether connected internally, or not.
>> --
>> Am I going to have to reinstall while connected to the domain?
>> Thanks,
>> Jay
>>|||Just because the error message says so, I'd still go to the services.msc, and
re-enter the password for the service account. Until you try, you can't be
sure.
Linchi
"Jay" wrote:
> Nope, I installed the servers under my domain account.
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
> news:B53CBAAC-1C38-450D-8623-61CC7BA9273A@.microsoft.com...
> > Check if the user account that runs the SQL Server service has a changed
> > password or an expired password.
> >
> > Linchi
> >
> > "Jay" wrote:
> >
> >> Last week my local DB's got hosed, so over the weekend, I reinstalled
> >> them
> >> (2000 & 2005). However, I was away and connected to a different network
> >> (IP
> >> change) when I reinstalled the servers (yes, I know it was screwy, but
> >> thats
> >> what I did).
> >>
> >> Now, back at work, everythin is fine remotly, however, my local instances
> >> of
> >> SQL Server refuse to start, the message is:
> >>
> >> The service did not start due to a logon failure.
> >>
> >> -and-
> >>
> >> An error 1069 - (The service did not start due to a logon failure.)
> >> occured while performing this service operation on the MSSQLServer
> >> service.
> >>
> >>
> >> I use the same DOMAIN\Login whether connected internally, or not.
> >>
> >> --
> >>
> >> Am I going to have to reinstall while connected to the domain?
> >>
> >> Thanks,
> >> Jay
> >>
> >>
> >>
>
>|||That worked, though why is a mystery to me. I was not completely aware that
the Windows services contained the login/password, I expected it in SQL
Server itself. Kinda silly of me I know, but I just never thought it through
properly.
Thanks,
Jay
PS. It took me a bit to get to it as there have been several things going
on.
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:66452707-C62C-42E3-981E-BBEDC3CA6D4D@.microsoft.com...
> Just because the error message says so, I'd still go to the services.msc,
> and
> re-enter the password for the service account. Until you try, you can't be
> sure.
> Linchi
> "Jay" wrote:
>> Nope, I installed the servers under my domain account.
>> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
>> news:B53CBAAC-1C38-450D-8623-61CC7BA9273A@.microsoft.com...
>> > Check if the user account that runs the SQL Server service has a
>> > changed
>> > password or an expired password.
>> >
>> > Linchi
>> >
>> > "Jay" wrote:
>> >
>> >> Last week my local DB's got hosed, so over the weekend, I reinstalled
>> >> them
>> >> (2000 & 2005). However, I was away and connected to a different
>> >> network
>> >> (IP
>> >> change) when I reinstalled the servers (yes, I know it was screwy, but
>> >> thats
>> >> what I did).
>> >>
>> >> Now, back at work, everythin is fine remotly, however, my local
>> >> instances
>> >> of
>> >> SQL Server refuse to start, the message is:
>> >>
>> >> The service did not start due to a logon failure.
>> >>
>> >> -and-
>> >>
>> >> An error 1069 - (The service did not start due to a logon
>> >> failure.)
>> >> occured while performing this service operation on the MSSQLServer
>> >> service.
>> >>
>> >>
>> >> I use the same DOMAIN\Login whether connected internally, or not.
>> >>
>> >> --
>> >>
>> >> Am I going to have to reinstall while connected to the domain?
>> >>
>> >> Thanks,
>> >> Jay
>> >>
>> >>
>> >>
>>|||OK, I now have the problem again.
I was, however, able to trace the problem to the following command being run
(which updates domain policies?)
gpupdate /force
Am I going to have to deal with the network/AD guys, or can I just get the
servers to run by myself?
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:66452707-C62C-42E3-981E-BBEDC3CA6D4D@.microsoft.com...
> Just because the error message says so, I'd still go to the services.msc,
> and
> re-enter the password for the service account. Until you try, you can't be
> sure.
> Linchi
> "Jay" wrote:
>> Nope, I installed the servers under my domain account.
>> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
>> news:B53CBAAC-1C38-450D-8623-61CC7BA9273A@.microsoft.com...
>> > Check if the user account that runs the SQL Server service has a
>> > changed
>> > password or an expired password.
>> >
>> > Linchi
>> >
>> > "Jay" wrote:
>> >
>> >> Last week my local DB's got hosed, so over the weekend, I reinstalled
>> >> them
>> >> (2000 & 2005). However, I was away and connected to a different
>> >> network
>> >> (IP
>> >> change) when I reinstalled the servers (yes, I know it was screwy, but
>> >> thats
>> >> what I did).
>> >>
>> >> Now, back at work, everythin is fine remotly, however, my local
>> >> instances
>> >> of
>> >> SQL Server refuse to start, the message is:
>> >>
>> >> The service did not start due to a logon failure.
>> >>
>> >> -and-
>> >>
>> >> An error 1069 - (The service did not start due to a logon
>> >> failure.)
>> >> occured while performing this service operation on the MSSQLServer
>> >> service.
>> >>
>> >>
>> >> I use the same DOMAIN\Login whether connected internally, or not.
>> >>
>> >> --
>> >>
>> >> Am I going to have to reinstall while connected to the domain?
>> >>
>> >> Thanks,
>> >> Jay
>> >>
>> >>
>> >>
>>|||Problem resolved.
I changed the services entry for my instances of SQL Server to use the
"Local System Account" and now, changes in the domain policy no longer
affect my local servers from starting (and having to open services and
retype my password all the time).
Hope this is useful to someone.
"Jay" <nospan@.nospam.org> wrote in message
news:%23FfJDNoGIHA.4272@.TK2MSFTNGP06.phx.gbl...
> Last week my local DB's got hosed, so over the weekend, I reinstalled them
> (2000 & 2005). However, I was away and connected to a different network
> (IP change) when I reinstalled the servers (yes, I know it was screwy, but
> thats what I did).
> Now, back at work, everythin is fine remotly, however, my local instances
> of SQL Server refuse to start, the message is:
> The service did not start due to a logon failure.
> -and-
> An error 1069 - (The service did not start due to a logon failure.)
> occured while performing this service operation on the MSSQLServer
> service.
>
> I use the same DOMAIN\Login whether connected internally, or not.
> --
> Am I going to have to reinstall while connected to the domain?
> Thanks,
> Jay
>