cant start the sql server services

Hi all

After i configure the Merge Replication, my sql server services wont start again.

The error show that "The request failed for the service did not respone in time fashion. Consult the event log or other application error logs for detail"

>>The error show that "The request failed for the service did not respone in time fashion. Consult the event log or other application error logs for detail"

Did you?

|||what is that mean actually/|||Did you consult with sql server log?|||

Go to C:\MS SQL Server\MSSQL4 (or 3 something like that)

There find a LOG folder and several log files which should tell you what exactly happend and why the service is not running.

Also check if you have set the services to start automatically or manually.

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:

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...
> > Sudenly my MSSQLServer stop initilizing.
> > Error 1069: Error initializing Session
> > |Any body knows what I can do?
>
>|||> 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...
> 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...
>> > Sudenly my MSSQLServer stop initilizing.
>> > Error 1069: Error initializing Session
>> > |Any body knows what I can do?
>>|||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...
> 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...
>> > Sudenly my MSSQLServer stop initilizing.
>> > Error 1069: Error initializing Session
>> > |Any body knows what I can do?
>>

Can't start SQLServerAgent

All of sudden, getting a Dr. Waston error with illegal
instruction on boot up.
If I tried to start it from the Services menu, get "Could
not start the SQLServerAgent service on \\server_name
Error 1067: The process terminated unexpectedly"
Do I need to reload the software... I have not found any
help in the Knowledge baseTake a closer look at the Dr Watson log to see if the SQLAgent service is
generating the Dr Watson error.
Stop any unnessary services on the machine. Leave the following running:
- Alerter
- Computer Browser
- Event Log
- License Logging Service
- Messenger
- Net Logon
- NTLM Security Support Provider
- Network Connectors
- Plug and Play
- Remote Procedure Call (RPC) Locator
- Remote Procedure Call (RPC) Service
- Server
- Spooler
- TCP/IP NetBIOS Helper
- Time Service
- Workstation
Review the NT application & System logs for hardware failure errors.
Test to see if you can start SQL Server from a command prompt.
If the problem persists and you're on the latest service pack, sp3, then
you should open up a support case.
If the Dr Watson is being caused by a bug in our product you will not be
charged for the incident.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Can't start SQLServerAgent

All of sudden, getting a Dr. Waston error with illegal
instruction on boot up.
If I tried to start it from the Services menu, get "Could
not start the SQLServerAgent service on \\server_name
Error 1067: The process terminated unexpectedly"
Do I need to reload the software... I have not found any
help in the Knowledge base| All of sudden, getting a Dr. Waston error with illegal
| instruction on boot up.
|
| If I tried to start it from the Services menu, get "Could
| not start the SQLServerAgent service on \\server_name
| Error 1067: The process terminated unexpectedly"
|
| Do I need to reload the software... I have not found any
| help in the Knowledge base
--
Folks,
If you can't find references of a SQL exception, please log a case with
Microsoft product support. There is a chance that this a bug so the case
shouldn't cost you.
Hope this helps,
--
Eric Cárdenas
SQL Server support|||Eric,
Thanks for the response... How do I log a case with
Microsoft product support?|||| Eric,
|
| Thanks for the response... How do I log a case with
| Microsoft product support?
|
--
Go to http://support.microsoft.com to get the contact number of Microsoft
product support for your country of residence.
Hope this helps,
--
Eric Cárdenas
SQL Server support

Can't start SQLEXPRESS so that I can't install latest SQLEXPRESS security updates.

I can't start SQLEXPRESS.

The SQL ERRORLOG shows: Error is 3414, Severity 21, State 2 and says: "An error occurred during recovery, preventing the database 'model' (database ID 3) from restarting." Just prior to this, I get a warning: "did not see LP_CKPT_END".

Any thoughts why this might be and how I can fix this?

Seems like something happened to your master database, check out the BOL topic on restoring master for starters.

Mike

|||

Thank you for your thoughts.

Unfortunately, I am not able to restore the database because I can't start SQLEXPRESS. I have even tried the command line sqlservr -s SQLEXPRESS command line command without success.

I continue to get this warning "did not see LP_CKPT_END" Error:3414, Severity:21, State: 1.

It might help to know that I have never used the SQLEXPRESS database on my box before. (I also have an instance of MSSQLSERVER and that is what I have been using. MSSQLSERVER starts up without issue.)

I'm not sure what it is that I would be restoring as I haven't created any databases in SQLEXPRESS.

The issue began when I update MSSQLSERVER with SP2 (KB 933508) install package. It seemed to take fine. I also did the install after March 5, 2007 -- a critical date for this update.

When the SQL 2005 Express SP2 (KB 921896) came out, it would load because it couldn't start an instance of SQLEXPRESS.

Does this help explain the background better? Your further suggestions would be helpful.

|||

This one is beyond me. Moving to the setup forum to ask the experts.

Mike

can't start SQL Server Analysis Services

Hi I am using SQL 2005 but when I go to the SQL Server Configuration manager
and try to start the SQL Server Analysis Services, I get the error message
Requiest failed or the service did not respond in a timely fashion.
In the event log it looks like there was a problem with login,
The SQL Server Analysis Services (MSSQLSERVER) service failed to start due
to the following error:
The service did not start due to a logon failure.
I currently have the logon as domain\username. Anyhow just wondering how to
fix this?
thanks Paul.
--
Paul G
Software engineer.got it working, for some reason the password was not set correctly, so just
used the properties box to correct it.
--
Paul G
Software engineer.
"Paul" wrote:
> Hi I am using SQL 2005 but when I go to the SQL Server Configuration manager
> and try to start the SQL Server Analysis Services, I get the error message
> Requiest failed or the service did not respond in a timely fashion.
> In the event log it looks like there was a problem with login,
> The SQL Server Analysis Services (MSSQLSERVER) service failed to start due
> to the following error:
> The service did not start due to a logon failure.
> I currently have the logon as domain\username. Anyhow just wondering how to
> fix this?
> thanks Paul.
> --
> Paul G
> Software engineer.sql

can't start SQL Server Analysis Services

Hi I am using SQL 2005 but when I go to the SQL Server Configuration manager
and try to start the SQL Server Analysis Services, I get the error message
Requiest failed or the service did not respond in a timely fashion.
In the event log it looks like there was a problem with login,
The SQL Server Analysis Services (MSSQLSERVER) service failed to start due
to the following error:
The service did not start due to a logon failure.
I currently have the logon as domain\username. Anyhow just wondering how to
fix this?
thanks Paul.
Paul G
Software engineer.
got it working, for some reason the password was not set correctly, so just
used the properties box to correct it.
Paul G
Software engineer.
"Paul" wrote:

> Hi I am using SQL 2005 but when I go to the SQL Server Configuration manager
> and try to start the SQL Server Analysis Services, I get the error message
> Requiest failed or the service did not respond in a timely fashion.
> In the event log it looks like there was a problem with login,
> The SQL Server Analysis Services (MSSQLSERVER) service failed to start due
> to the following error:
> The service did not start due to a logon failure.
> I currently have the logon as domain\username. Anyhow just wondering how to
> fix this?
> thanks Paul.
> --
> Paul G
> Software engineer.

can't start SQL Server Analysis Services

Hi I am using SQL 2005 but when I go to the SQL Server Configuration manager
and try to start the SQL Server Analysis Services, I get the error message
Requiest failed or the service did not respond in a timely fashion.
In the event log it looks like there was a problem with login,
The SQL Server Analysis Services (MSSQLSERVER) service failed to start due
to the following error:
The service did not start due to a logon failure.
I currently have the logon as domain\username. Anyhow just wondering how to
fix this?
thanks Paul.
--
Paul G
Software engineer.got it working, for some reason the password was not set correctly, so just
used the properties box to correct it.
--
Paul G
Software engineer.
"Paul" wrote:

> Hi I am using SQL 2005 but when I go to the SQL Server Configuration manag
er
> and try to start the SQL Server Analysis Services, I get the error message
> Requiest failed or the service did not respond in a timely fashion.
> In the event log it looks like there was a problem with login,
> The SQL Server Analysis Services (MSSQLSERVER) service failed to start due
> to the following error:
> The service did not start due to a logon failure.
> I currently have the logon as domain\username. Anyhow just wondering how
to
> fix this?
> thanks Paul.
> --
> Paul G
> Software engineer.

Can't start SQL Server Agent - wants MSSQLServerADHelper

When I try to start the SQL Server Agent service, it gives an error about
starting MSSQLServerADHelper.
When I look in the event log, it says:
The MSSQLServerADHelper service terminated with service-specific error
3221225572.
How can I get SQL Server Agent started? I had maintenance tasks scheduled
(backup, etc.) that now will not run.Are you sure that it is Agent who writes this error?
Check the Agent errorlog for error messages.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"JJ" <jjjj@.nospam.com> wrote in message news:eBOIaBurDHA.2244@.TK2MSFTNGP09.phx.gbl...
> When I try to start the SQL Server Agent service, it gives an error about
> starting MSSQLServerADHelper.
> When I look in the event log, it says:
> The MSSQLServerADHelper service terminated with service-specific error
> 3221225572.
> How can I get SQL Server Agent started? I had maintenance tasks scheduled
> (backup, etc.) that now will not run.
>|||I am positive that this is what occurs:
In the Services Control Panel applet, the SQL Server Agent service is
stopped. (It had been running on this system up until a few weeks ago -
this is a customer system, so I didn't know it stopped until now.)
When I right-click on SQL Server Agent and choose Start, that's when I get
the error on the screen that MSSQLServerADHelper could not be started.
But I think I have found the problem - it looks like someone there changed
SQL Server Agent to run in a specific account. I changed it to run as Local
System and then I could start it.
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:%23dILAtzrDHA.1764@.TK2MSFTNGP10.phx.gbl...
> Are you sure that it is Agent who writes this error?
> Check the Agent errorlog for error messages.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "JJ" <jjjj@.nospam.com> wrote in message
news:eBOIaBurDHA.2244@.TK2MSFTNGP09.phx.gbl...
> > When I try to start the SQL Server Agent service, it gives an error
about
> > starting MSSQLServerADHelper.
> >
> > When I look in the event log, it says:
> >
> > The MSSQLServerADHelper service terminated with service-specific error
> > 3221225572.
> >
> > How can I get SQL Server Agent started? I had maintenance tasks
scheduled
> > (backup, etc.) that now will not run.
> >
> >
>|||The startup account that they changed it to most likely
didn't have permissions to start the MSSQLServerADHelper
service.
-Sue
On Thu, 20 Nov 2003 09:19:49 -0500, "JJ" <jjjj@.nospam.com>
wrote:
>I am positive that this is what occurs:
>In the Services Control Panel applet, the SQL Server Agent service is
>stopped. (It had been running on this system up until a few weeks ago -
>this is a customer system, so I didn't know it stopped until now.)
>When I right-click on SQL Server Agent and choose Start, that's when I get
>the error on the screen that MSSQLServerADHelper could not be started.
>But I think I have found the problem - it looks like someone there changed
>SQL Server Agent to run in a specific account. I changed it to run as Local
>System and then I could start it.
>
>"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
>wrote in message news:%23dILAtzrDHA.1764@.TK2MSFTNGP10.phx.gbl...
>> Are you sure that it is Agent who writes this error?
>> Check the Agent errorlog for error messages.
>> --
>> Tibor Karaszi, SQL Server MVP
>> Archive at:
>http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>>
>> "JJ" <jjjj@.nospam.com> wrote in message
>news:eBOIaBurDHA.2244@.TK2MSFTNGP09.phx.gbl...
>> > When I try to start the SQL Server Agent service, it gives an error
>about
>> > starting MSSQLServerADHelper.
>> >
>> > When I look in the event log, it says:
>> >
>> > The MSSQLServerADHelper service terminated with service-specific error
>> > 3221225572.
>> >
>> > How can I get SQL Server Agent started? I had maintenance tasks
>scheduled
>> > (backup, etc.) that now will not run.
>> >
>> >
>>
>|||Hi JJ,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
MSSQLServerADHelper is a service installed by the SQL Server Setup program
that handles the Active Directory objects for all instances of the SQL
Server relational database engine and all Analysis Manager applications
that are running on the computer. There is only one MSSQLServerADHelper
service on a computer for all of the instances of Microsoft SQL Server
2000. This service is set to use the Local System Account by default.
This error only happens only if someone or some service tried to start the
service manually. It's possible that some "monitoring service" would
attempt to start a service if it identified that the service was not
started/running. If you check for such a service and make sure to remove
MSSQLServerADHelper service from it list of service to watch.
To avoid seeing this message again, you should not set the service to start
automatically. You can change this service to manually by
Start->Programs->Administrative tools->Services", find the
"MSSQLServerADHelper" in the list of services and change the property of
it. You right click the "MSSQLServerADHelper" and choose the "properties"
from the menu. Please check and see if the service MSSQLServerADHelper has
"Interact with the desktop" checked in the properties, if yes, then please
uncheck that. Also set the service to manual.
After the above steps are complete let me know if the event logs still get
the error.
I hope my information will help you to solve your problem. Please feel free
to post new information here and I am ready to provide further support.
Sincerely Yours
Baisong, Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
--
| From: "JJ" <jjjj@.nospam.com>
| Subject: Can't start SQL Server Agent - wants MSSQLServerADHelper
| Date: Wed, 19 Nov 2003 16:01:48 -0500
| Lines: 12
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <eBOIaBurDHA.2244@.TK2MSFTNGP09.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: 146.145.51.166
| Path:
cpmsftngxa07.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08|||I am unable to start the service after following the steps mentioned and it is showing the same error in the event log
From http://www.developmentnow.com/g/118_2003_11_0_0_465849/Cant-start-SQL-Server-Agent--wants-MSSQLServerADHelper.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||Hi
Have tou tried to use the local system account and/or start the service from
SQL Server Service Manager or through enterprise manager? What does the SQL
Agent log file contain?
John
"prashanthi" wrote:
> I am unable to start the service after following the steps mentioned and it is showing the same error in the event log.
> From http://www.developmentnow.com/g/118_2003_11_0_0_465849/Cant-start-SQL-Server-Agent--wants-MSSQLServerADHelper.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
>

can't start sql server agent

Using SS2000 SP4. We rebooted our box this morning and the sql server agent
wouldn't start. I found this error in the event viewer in the system errorlog
- " The SQLSERVERAGENT service failed to start due to the following error:
The account name is invalid or does not exist, or the password is invalid
for the account name specified. "
The agent is using the same login and password as the SQL Server service and
the SQL Server service started fine. I trying putting in the password again
from the services app but the hourglass kept going and going until we finally
killed it. I tried changing the startup account to the local system from
within EM but I got this message - "The new service startup account name you
have supplied is invalid or does not exist." I tried using my domain account
and got the same message. I tried going back to the original login and
password and got the same message.
Our sysadmin said he had some problems with our domain controller over the
weekend. Since it can't seem to verify the accounts I thought that might be
related but if so, why does the SQL Server account work ok with the same
login and password?
Any ideas?
Thanks,
--
Dan D.Did you try log in on Windows on the same box? Sometimes it is a profile
problem.
--
Regards,
Robson Siqueira
Enterprise Architect
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
> Using SS2000 SP4. We rebooted our box this morning and the sql server
> agent
> wouldn't start. I found this error in the event viewer in the system
> errorlog
> - " The SQLSERVERAGENT service failed to start due to the following error:
> The account name is invalid or does not exist, or the password is invalid
> for the account name specified. "
> The agent is using the same login and password as the SQL Server service
> and
> the SQL Server service started fine. I trying putting in the password
> again
> from the services app but the hourglass kept going and going until we
> finally
> killed it. I tried changing the startup account to the local system from
> within EM but I got this message - "The new service startup account name
> you
> have supplied is invalid or does not exist." I tried using my domain
> account
> and got the same message. I tried going back to the original login and
> password and got the same message.
> Our sysadmin said he had some problems with our domain controller over the
> weekend. Since it can't seem to verify the accounts I thought that might
> be
> related but if so, why does the SQL Server account work ok with the same
> login and password?
> Any ideas?
> Thanks,
> --
> Dan D.|||They were changing the monitor in the computer room and this server hasn't
been hooked up yet.
I came in this morning and the agent service had started overnight. So,
we're okay for now. Thanks,
--
Dan D.
"Robson Siqueira" wrote:
> Did you try log in on Windows on the same box? Sometimes it is a profile
> problem.
> --
> Regards,
> Robson Siqueira
> Enterprise Architect
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
> > Using SS2000 SP4. We rebooted our box this morning and the sql server
> > agent
> > wouldn't start. I found this error in the event viewer in the system
> > errorlog
> > - " The SQLSERVERAGENT service failed to start due to the following error:
> > The account name is invalid or does not exist, or the password is invalid
> > for the account name specified. "
> >
> > The agent is using the same login and password as the SQL Server service
> > and
> > the SQL Server service started fine. I trying putting in the password
> > again
> > from the services app but the hourglass kept going and going until we
> > finally
> > killed it. I tried changing the startup account to the local system from
> > within EM but I got this message - "The new service startup account name
> > you
> > have supplied is invalid or does not exist." I tried using my domain
> > account
> > and got the same message. I tried going back to the original login and
> > password and got the same message.
> >
> > Our sysadmin said he had some problems with our domain controller over the
> > weekend. Since it can't seem to verify the accounts I thought that might
> > be
> > related but if so, why does the SQL Server account work ok with the same
> > login and password?
> >
> > Any ideas?
> >
> > Thanks,
> > --
> > Dan D.
>
>

Can't start SQL Server Agent

Hello,
When I try to start SQL Server Agent I get a message "An error 1049 - (The
service did not start due to a logon failure) while performing this service
operation on the SQLServerAgent service."
I am logged on to the machine as Administrator and SQL Server has a login
for Servername\Administrator.
I can perform data manipulation operations with no problems. I have not had
this problem on other servers before.
Any help would be appreciated.
RagnarHello,
Go to the COntrol Panel, Services, SQL Server Agent -- Go to Logon option
and chnage it to Local System Account and try restarting.
If it works fine then use a domain account and specify the password and
restrt the service.
I recommend you to start SQL Server and SQL Server Agent using the same
login account.
Thanks
Hari
"Ragnar Midtskogen" <ragnar_ng@.newsgroups.com> wrote in message
news:%23EzZ4wQYHHA.588@.TK2MSFTNGP06.phx.gbl...
> Hello,
> When I try to start SQL Server Agent I get a message "An error 1049 - (The
> service did not start due to a logon failure) while performing this
> service operation on the SQLServerAgent service."
> I am logged on to the machine as Administrator and SQL Server has a login
> for Servername\Administrator.
> I can perform data manipulation operations with no problems. I have not
> had this problem on other servers before.
> Any help would be appreciated.
> Ragnar
>|||Thank you Hari,
The logon was set as Administrator, so I just reset the password and that
solved the problem.
By the way, the SQL Server Agent properties shows startup account as being
Administrator and it also shows that the connection should use Windows
authentication.
I am a little confused as to what the difference is between the startup and
the connect properties, but as long as it works I am happy.
Ragnarsql

Can't start SQL Server Agent

Hello,
When I try to start SQL Server Agent I get a message "An error 1049 - (The
service did not start due to a logon failure) while performing this service
operation on the SQLServerAgent service."
I am logged on to the machine as Administrator and SQL Server has a login
for Servername\Administrator.
I can perform data manipulation operations with no problems. I have not had
this problem on other servers before.
Any help would be appreciated.
Ragnar
Hello,
Go to the COntrol Panel, Services, SQL Server Agent -- Go to Logon option
and chnage it to Local System Account and try restarting.
If it works fine then use a domain account and specify the password and
restrt the service.
I recommend you to start SQL Server and SQL Server Agent using the same
login account.
Thanks
Hari
"Ragnar Midtskogen" <ragnar_ng@.newsgroups.com> wrote in message
news:%23EzZ4wQYHHA.588@.TK2MSFTNGP06.phx.gbl...
> Hello,
> When I try to start SQL Server Agent I get a message "An error 1049 - (The
> service did not start due to a logon failure) while performing this
> service operation on the SQLServerAgent service."
> I am logged on to the machine as Administrator and SQL Server has a login
> for Servername\Administrator.
> I can perform data manipulation operations with no problems. I have not
> had this problem on other servers before.
> Any help would be appreciated.
> Ragnar
>
|||Thank you Hari,
The logon was set as Administrator, so I just reset the password and that
solved the problem.
By the way, the SQL Server Agent properties shows startup account as being
Administrator and it also shows that the connection should use Windows
authentication.
I am a little confused as to what the difference is between the startup and
the connect properties, but as long as it works I am happy.
Ragnar

can't start sql server agent

Using SS2000 SP4. We rebooted our box this morning and the sql server agent
wouldn't start. I found this error in the event viewer in the system errorlog
- " The SQLSERVERAGENT service failed to start due to the following error:
The account name is invalid or does not exist, or the password is invalid
for the account name specified. "
The agent is using the same login and password as the SQL Server service and
the SQL Server service started fine. I trying putting in the password again
from the services app but the hourglass kept going and going until we finally
killed it. I tried changing the startup account to the local system from
within EM but I got this message - "The new service startup account name you
have supplied is invalid or does not exist." I tried using my domain account
and got the same message. I tried going back to the original login and
password and got the same message.
Our sysadmin said he had some problems with our domain controller over the
weekend. Since it can't seem to verify the accounts I thought that might be
related but if so, why does the SQL Server account work ok with the same
login and password?
Any ideas?
Thanks,
Dan D.
Did you try log in on Windows on the same box? Sometimes it is a profile
problem.
Regards,
Robson Siqueira
Enterprise Architect
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
> Using SS2000 SP4. We rebooted our box this morning and the sql server
> agent
> wouldn't start. I found this error in the event viewer in the system
> errorlog
> - " The SQLSERVERAGENT service failed to start due to the following error:
> The account name is invalid or does not exist, or the password is invalid
> for the account name specified. "
> The agent is using the same login and password as the SQL Server service
> and
> the SQL Server service started fine. I trying putting in the password
> again
> from the services app but the hourglass kept going and going until we
> finally
> killed it. I tried changing the startup account to the local system from
> within EM but I got this message - "The new service startup account name
> you
> have supplied is invalid or does not exist." I tried using my domain
> account
> and got the same message. I tried going back to the original login and
> password and got the same message.
> Our sysadmin said he had some problems with our domain controller over the
> weekend. Since it can't seem to verify the accounts I thought that might
> be
> related but if so, why does the SQL Server account work ok with the same
> login and password?
> Any ideas?
> Thanks,
> --
> Dan D.
|||They were changing the monitor in the computer room and this server hasn't
been hooked up yet.
I came in this morning and the agent service had started overnight. So,
we're okay for now. Thanks,
Dan D.
"Robson Siqueira" wrote:

> Did you try log in on Windows on the same box? Sometimes it is a profile
> problem.
> --
> Regards,
> Robson Siqueira
> Enterprise Architect
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
>
>

can't start sql server agent

Using SS2000 SP4. We rebooted our box this morning and the sql server agent
wouldn't start. I found this error in the event viewer in the system errorlo
g
- " The SQLSERVERAGENT service failed to start due to the following error:
The account name is invalid or does not exist, or the password is invalid
for the account name specified. "
The agent is using the same login and password as the SQL Server service and
the SQL Server service started fine. I trying putting in the password again
from the services app but the hourglass kept going and going until we finall
y
killed it. I tried changing the startup account to the local system from
within EM but I got this message - "The new service startup account name you
have supplied is invalid or does not exist." I tried using my domain account
and got the same message. I tried going back to the original login and
password and got the same message.
Our sysadmin said he had some problems with our domain controller over the
weekend. Since it can't seem to verify the accounts I thought that might be
related but if so, why does the SQL Server account work ok with the same
login and password?
Any ideas?
Thanks,
--
Dan D.Did you try log in on Windows on the same box? Sometimes it is a profile
problem.
Regards,
Robson Siqueira
Enterprise Architect
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
> Using SS2000 SP4. We rebooted our box this morning and the sql server
> agent
> wouldn't start. I found this error in the event viewer in the system
> errorlog
> - " The SQLSERVERAGENT service failed to start due to the following error:
> The account name is invalid or does not exist, or the password is invalid
> for the account name specified. "
> The agent is using the same login and password as the SQL Server service
> and
> the SQL Server service started fine. I trying putting in the password
> again
> from the services app but the hourglass kept going and going until we
> finally
> killed it. I tried changing the startup account to the local system from
> within EM but I got this message - "The new service startup account name
> you
> have supplied is invalid or does not exist." I tried using my domain
> account
> and got the same message. I tried going back to the original login and
> password and got the same message.
> Our sysadmin said he had some problems with our domain controller over the
> weekend. Since it can't seem to verify the accounts I thought that might
> be
> related but if so, why does the SQL Server account work ok with the same
> login and password?
> Any ideas?
> Thanks,
> --
> Dan D.|||They were changing the monitor in the computer room and this server hasn't
been hooked up yet.
I came in this morning and the agent service had started overnight. So,
we're okay for now. Thanks,
--
Dan D.
"Robson Siqueira" wrote:

> Did you try log in on Windows on the same box? Sometimes it is a profile
> problem.
> --
> Regards,
> Robson Siqueira
> Enterprise Architect
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
>
>

Can't start SQL Server Agent

Hello,
When I try to start SQL Server Agent I get a message "An error 1049 - (The
service did not start due to a logon failure) while performing this service
operation on the SQLServerAgent service."
I am logged on to the machine as Administrator and SQL Server has a login
for Servername\Administrator.
I can perform data manipulation operations with no problems. I have not had
this problem on other servers before.
Any help would be appreciated.
RagnarHello,
Go to the COntrol Panel, Services, SQL Server Agent -- Go to Logon option
and chnage it to Local System Account and try restarting.
If it works fine then use a domain account and specify the password and
restrt the service.
I recommend you to start SQL Server and SQL Server Agent using the same
login account.
Thanks
Hari
"Ragnar Midtskogen" <ragnar_ng@.newsgroups.com> wrote in message
news:%23EzZ4wQYHHA.588@.TK2MSFTNGP06.phx.gbl...
> Hello,
> When I try to start SQL Server Agent I get a message "An error 1049 - (The
> service did not start due to a logon failure) while performing this
> service operation on the SQLServerAgent service."
> I am logged on to the machine as Administrator and SQL Server has a login
> for Servername\Administrator.
> I can perform data manipulation operations with no problems. I have not
> had this problem on other servers before.
> Any help would be appreciated.
> Ragnar
>|||Thank you Hari,
The logon was set as Administrator, so I just reset the password and that
solved the problem.
By the way, the SQL Server Agent properties shows startup account as being
Administrator and it also shows that the connection should use Windows
authentication.
I am a little confused as to what the difference is between the startup and
the connect properties, but as long as it works I am happy.
Ragnar

Can't start sql server 2000, error: "use sql 2005 management tools" !!!!

hi .everyone !

i have ms visual studio 2005 with sql sever 2005 management tools

anyway .. i want to use and install sql server 2000 in this machine .. i tried to install it, but when i tried to connect to the server .. it gives me this error:

"you must use sql server 2005 management tools to connect to this server"

can you help me ? plz !?

no one can help me ?

any suggestion ? help ? :(

Can't start SQL on 2005 Cluster

The SQL Server (MSSQLSERVER) service terminated with service-specific error
3417 (0xD59).
This is what I get on my 2005 Cluster when I try to start SQL on one of the
nodes. Another node is running fine, no problems what so ever.
Please help...Check out:
http://msdn2.microsoft.com/en-us/library/aa337262.aspx
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:185F94E0-9E8E-4048-A25B-7311CCDC9D96@.microsoft.com...
The SQL Server (MSSQLSERVER) service terminated with service-specific error
3417 (0xD59).
This is what I get on my 2005 Cluster when I try to start SQL on one of the
nodes. Another node is running fine, no problems what so ever.
Please help...|||I've found that a good way to inadvertently generate this error is to compress the files on the drive that your instance is running on - not to be recommended as a rule.
When you attempt to start the instance the System event log gives the service specific error 3417 as you've seen.
The Application event log was a bit more useful for me - "The file "D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed."
I decompressed the files and the service started fine - something to consider.
Mar
From http://www.developmentnow.com/g/118_2006_10_0_0_840331/Cant-start-SQL-on-2005-Cluster.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||thanks for upstai
From http://www.developmentnow.com/g/118_2006_10_0_0_840331/Cant-start-SQL-on-2005-Cluster.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com

Can't start ReportServer service

Hello

I having problem to start ReportServer service after our Network administrator reboot the reporting server. Getting an error: "Error 1075: The dependency service does not exist or has been marked for deletion."

This is an error message from Event Viewer: "The ReportServer service depends on the following nonexistent service: mssqlserver"

First there are no explicit dependencies, second we have sql server installed on different machine. Any ideas how to fix it? Would appriciate any help.

Is this RS 2005? Early versions of RS2000 had a dependency on SQL Server, but this has not been the case for sometime and never in a released version. Is it possible this was an upgrade from an early 2000 beta?

The best option might be to uninstall RS then reinstall, hooking up to the old DB. Make sure you back up your symmetric key first or you will have to reenter all credentials.

Can't start a cloned connection while in manual transaction mode.

I got this error recently using SQL Server, and I found a microsoft site
which gives a solution by setting the SelectMethod property to Cursor but I
don't understand why. We've run this app before with no problems, yet now all
of a sudden we need to customize the URL string of the driver connection.
Can anyone explain what this means exactly and why this might have become a
problem now but was not before?
Most appreciated,
ol,
add "SelectMethod=cursor" your URL connection
ex:
Connection conn =
DriverManager.getConnection("jdbc:microsoft:sqlser ver://localhost:1433;SelectMethod=cursor");
newton
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message1022266.html
|||| Thread-Topic: Can't start a cloned connection while in manual transaction
mode.
| thread-index: AcVBMGMZaFbT7Q3cQUeyebz5WmA8JQ==
| X-WBNR-Posting-Host: 66.114.64.114
| From: "=?Utf-8?B?TXJOb2JvZHk=?=" <MrNobody@.discussions.microsoft.com>
| Subject: Can't start a cloned connection while in manual transaction mode.
| Date: Thu, 14 Apr 2005 13:27:32 -0700
| Lines: 11
| Message-ID: <120F0C3C-9AAD-4B6A-B7F4-3F966E95E4DD@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSF TNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.jdbcdriver:6826
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| I got this error recently using SQL Server, and I found a microsoft site
| which gives a solution by setting the SelectMethod property to Cursor but
I
| don't understand why. We've run this app before with no problems, yet now
all
| of a sudden we need to customize the URL string of the driver connection.
|
| Can anyone explain what this means exactly and why this might have become
a
| problem now but was not before?
|
| Most appreciated,
|
|
|
Hello,
You will definitely need to use cursor mode to allow cloned connections to
be spawned on your behalf in a transaction. The behavior of SelectMethod
has been the same for the last several years.
If your code always used SelectMethod=direct, then the only thing I can
think of is that your app never entered the codepath that required a new
connection to be spawned.
Carb Simien, MCSE MCDBA MCAD
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.