Dear friends hi,
I read the articles you mentioned, and as I understood,
the resolution is:
(To resolve the problem, use these steps:
Change the startup account of both the MSSQLSERVER and
SQLServerAgent to use the Local System account.
Restart the computer. )
As I told you before, the problem is that I can not start
the 'SqlServer' and 'SqlServer agent', so I cann't go and
change the startup account. I don't know, I may be
confused, but I just encountered this Error (Error 1068)
while starting up the SQLServer.
Thanks for any suggestion in advance,
Mattew
>--Original Message--
Mattew,
Hmmm. Probably means that something changed. Here is
one KB article. Does
it apply?
http://support.microsoft.com/default.aspx?scid=kb;en-
us;307288
A more general article (non-SQL Server) on the topic:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;827328
Russell Fields
"Mattew" <anonymous@.discussions.microsoft.com> wrote in
message
news:19d5001c44d8c$610cb740$a401280a@.phx.gbl...
Hi,
I'm getting the following error message:
(
Could not start the SQLServerAgent Serviceon local
computer
Error 1068 : The dependency service or group failed to
start
)
This server is a subscriber in a transactional
replication and it was working until yesterday.
Does anybody have a solution.
Thanks in advance.Hi,
Steps to change the service startup account:-
1. Go to control panel -- Administrative - tools
2. Double click in services icon
3. Select and double click the MSSQL Server Service
4. In the "Log on " tab, Check the this account
5. There you verify the OS user name
6. If the user name is correct , re- enter the password and confrim password
once again
7. CLick OK
8. Start the Service
Do the above steps for SQL Agent Service as well.
Note:
ON each password change you have to do the above steps. The best
recommendation to have a user name for MSSQL server Service startup which do
not chage password frequently or no password expiry is set.
Thanks
Hari
MCDBA
"Mattew" <anonymous@.discussions.microsoft.com> wrote in message
news:1a4a701c44e42$10919180$a401280a@.phx.gbl...
> Dear friends hi,
> I read the articles you mentioned, and as I understood,
> the resolution is:
> (To resolve the problem, use these steps:
> Change the startup account of both the MSSQLSERVER and
> SQLServerAgent to use the Local System account.
> Restart the computer. )
> As I told you before, the problem is that I can not start
> the 'SqlServer' and 'SqlServer agent', so I cann't go and
> change the startup account. I don't know, I may be
> confused, but I just encountered this Error (Error 1068)
> while starting up the SQLServer.
> Thanks for any suggestion in advance,
> Mattew
> >--Original Message--
> Mattew,
> Hmmm. Probably means that something changed. Here is
> one KB article. Does
> it apply?
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;307288
> A more general article (non-SQL Server) on the topic:
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;827328
> Russell Fields
> "Mattew" <anonymous@.discussions.microsoft.com> wrote in
> message
> news:19d5001c44d8c$610cb740$a401280a@.phx.gbl...
> Hi,
> I'm getting the following error message:
> (
> Could not start the SQLServerAgent Serviceon local
> computer
> Error 1068 : The dependency service or group failed to
> start
> )
> This server is a subscriber in a transactional
> replication and it was working until yesterday.
> Does anybody have a solution.
> Thanks in advance.|||OMG. What a horrible message to come in to work to!
I just read about changing the startup account in CPanel.
The only thing I would want to toss in is that if you
make login changes at the CPanel level, rather then
Enterprise Mgr, you will have a ton o' problems related
to reg entries and internal stuff.
To sidestep that, if you ARE able to get the server
started using a CPanel change, can you then go into EM
and change it in there under your server's
properties/security page? Kind of a "redundant change?"
ML
>--Original Message--
>Hi,
>Steps to change the service startup account:-
>1. Go to control panel -- Administrative - tools
>2. Double click in services icon
>3. Select and double click the MSSQL Server Service
>4. In the "Log on " tab, Check the this account
>5. There you verify the OS user name
>6. If the user name is correct , re- enter the password
and confrim password
>once again
>7. CLick OK
>8. Start the Service
>Do the above steps for SQL Agent Service as well.
>Note:
>ON each password change you have to do the above steps.
The best
>recommendation to have a user name for MSSQL server
Service startup which do
>not chage password frequently or no password expiry is
set.
>Thanks
>Hari
>MCDBA
>
>
>"Mattew" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1a4a701c44e42$10919180$a401280a@.phx.gbl...
>> Dear friends hi,
>> I read the articles you mentioned, and as I understood,
>> the resolution is:
>> (To resolve the problem, use these steps:
>> Change the startup account of both the MSSQLSERVER and
>> SQLServerAgent to use the Local System account.
>> Restart the computer. )
>> As I told you before, the problem is that I can not
start
>> the 'SqlServer' and 'SqlServer agent', so I cann't go
and
>> change the startup account. I don't know, I may be
>> confused, but I just encountered this Error (Error
1068)
>> while starting up the SQLServer.
>> Thanks for any suggestion in advance,
>> Mattew
>> >--Original Message--
>> Mattew,
>> Hmmm. Probably means that something changed. Here is
>> one KB article. Does
>> it apply?
>> http://support.microsoft.com/default.aspx?scid=kb;en-
>> us;307288
>> A more general article (non-SQL Server) on the topic:
>> http://support.microsoft.com/default.aspx?scid=kb;en-
>> us;827328
>> Russell Fields
>> "Mattew" <anonymous@.discussions.microsoft.com> wrote in
>> message
>> news:19d5001c44d8c$610cb740$a401280a@.phx.gbl...
>> Hi,
>> I'm getting the following error message:
>> (
>> Could not start the SQLServerAgent Serviceon local
>> computer
>> Error 1068 : The dependency service or group failed to
>> start
>> )
>> This server is a subscriber in a transactional
>> replication and it was working until yesterday.
>> Does anybody have a solution.
>> Thanks in advance.
>
>.
>
No comments:
Post a Comment