I'm not sure i was clear the first time. When the MSSQLServer Service is stopped and started, it stops the SQLServerAgent Service also. But when the MSSQLServer Service is started, it DOES NOT start the SQLServerAgent Service. I don't think this is configurable, so I was wondering if someone had a workaround (.bat file, service dependency, etc.).
TIA,
Mike
When my system re-boots SQLServerAgent will no longer start. The following message is sent to the NT Event Log:
(Event ID 103) "SQLServerAgent could not be started (reason: Unable to connect to server; SQLServerAgent cannot start)."
Following this message are two messages from MSSQLServer that read:
(Event ID 19020) "RPC Net-Library listening on: ncalrpc:USBGRSYSTST1[WMSG0000009A.00000001]."
So is this a timing issues? Is MSSQLServer taking too long to completely start before SQLServerAgent is started? If so, is there a way (without hacking through the registry) to make the SQLServerAgent service dependant on the MSSQLServer service?
This startup issue did not exist until an application was installed on the machine that also has several services that auto-start. I noticed that many of these new services are starting at the same time the MSSQLServer service is starting.
Any asssistance would be most appreciated.
wanted to start the sql server agent and i got this error :
An Error 1069 - (The service did not start due to logon faliure ) occured wile performing this service operation on SQLServerAgent servcice.
What could be the solution for the above error.
Thanks in advance
Hi all,
I have a maintenance plan on SQL2000, that is backing up the database.
It is under Management/SQL Server Agent. When I try to start the job, I got an error, saying: Error 22022 SQLServerAgent is not currently running so it cannot be notified of this action.
But, when I try to start the SQL Server Agent (in Services), it stops directly with the following information: The
SQLAgent$Sharepoint service on Local Computer started and then stopped.
Some services stop automatically if they have no work to do, for
example, the Performance Logs and Alerts service.
When I try to start it from the SQL Server Service Manager: no reaction at all!
For some weeks now, SQLServeragent hangs after I restart the computer. Whatcould be a reason for this? I don't think I changed anything.The system protocol only says "SQLServeragent hung during start" (orsimilar - I have a German speaking system here).The application protocol says something like: "SQLServerAgent can not bestarted (reason: Connection to server can not be established. SQLServerAgentcan not start.)"MSSQL runs without problems, and when I start SQLServeragent manually, itruns without problems too.System: Microsoft SQL Server 7.00 - 7.00.1077 (Intel X86)Sep 6 2002 15:10:15Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)-mpe
View 2 Replies View RelatedHi All,
I need a help here please.
I have a sql server 2000 running on windows server 2003. I run the services (MSSQLSERVER,SQLSERVERAGENT) under a local user which has no admin right. This local user named "sqlsvr".
The configuration that i used to make the "sqlsvr" able to run the services is in this web address :
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q283811
After im able to run the services under "sqlsvr". I added also permission "Impersonate client after authentication" on security policy for "sqlsvr" in order to make the clients able to connect to sqlserver through ODBC with "windows authentication" mode.
But the problem is, after i finished these configuration, i cannot make the SQLSVRAGENT run. And it shows an error message :
"SQLServerAgent started then stopped. Some services stop automatically if they have no work to do for example Performance Logs and Alert Service" and stops there. Then what we have to do is use the start to startup the service....€?
Please help
note : I must run the services under "sqlsvr" in order to comply with the security standard on my office.
Thank you very much
Best Regards
Felix Adhitya
Hello,
I had created a windows service using C#. I set its Startup Type as Automatic but it is not getting started automatically when my System Starts.
Hi,
I am trying to install MS Sql Server 2000 on my machine. The OS on my machine is Windows XP SP2. During the installation i keep getting an error message, "Setup failed to configure the server. Refer to the server error logs and C:WINDOWSsqlstp.log for more information." I have copied an extract from the sqlstp.log file below:
10:05:28 Process Exit Code: (-1)
10:05:31 Setup failed to configure the server. Refer to the server error logs and C:WINDOWSsqlstp.log for more information.
10:05:31 Action CleanUpInstall:
10:05:31 C:WINDOWSTEMPSqlSetupBinscm.exe -Silent 1 -Action 4 -Service SQLSERVERAGENT
10:05:31 Process Exit Code: (1060) The specified service does not exist as an installed service.
10:05:31 C:WINDOWSTEMPSqlSetupBinscm.exe -Silent 1 -Action 4 -Service MSSQLSERVER
10:05:31 Process Exit Code: (0)
10:05:31 StatsGenerate returned: 2
10:05:31 StatsGenerate (0x0,0x1,0xf000000,0x200,1033,303,0x0,0x1,0,0,0
10:05:31 StatsGenerate -1,531793)
10:05:31 Installation Failed.
Can someone please help me solve this problem?
Cheers...
When our rep distribution services time-out (several times a day) some dba's just restart the service while others restart the rep job which starts the service. Are there any differences between these two methods? Does restarting the service inherit any changes made to the job's attributes?
Thanks!
This may be more of an IT question, but I hope someone here will have the answer.
I am trying to change the "Log on as" for SQLSERVERAGENT NT Service through Windows Registry. I am able to find HKLMSYSTEMCurrentControlSetServicesSQLSERVERAGENTObjectName and change it but I dont know how to specify a password to go with it. If I simply change it to .Administrator (from Local System) it errors out.
Ideally I would like to script this so I can change the logon without having to go though the Services Control Panel or SQL Management Studio.
Thanks.
Mark
I restarted the MSSQLSERVER service and SQLSERVERAGENT will not restart.
I get the following error.
Could not start the SQLSERVERAGENT service on Local Computer.
The service did not return an error. This could be an internal Windows erroror an internal service error.
If the problem persists, contact you system administrator.
Well the system administrator has no idea.
I am new at this.
please give me a hand.
I have a ABC service on a server1 that is dependent on MSSQLSERVER service running on server2. Does anyone know how to setup the service ABC on server1 to have a dependancy on MSSQLSERVER running on server2?
Thanks,
jgs
hi all
i'm using a domain accout to setup a sql 2005 cluster in a win2003 cluster.when the installation ended,the SqlServerAgent service can't be started.the event in event viewer
is "SQLServerAgent could not be started (reason: Unable to connect to server "(local)"; LServerAgent
cannot start). " (event id 103 ,source sqlserveragent).I try to use local system and network service account to start it,but it's all the same.
And i found i can connect to the sql cluster vitrual ip 10.73.2.224,but can't connect to the node A.So i enable all the network protocols for the instance MSSQLSERVER,and also enable every ip in the TCP/IP protocol,then restart the sqlserver service,but it still doesn't work.
Any advise?Thanks a lot.
When we try to connect the Sql server from our client, the MSSQLServer service stops and when we try to restart the service it goes back to the stop state after few seconds.
Server Configuration in order of installation,
1.WINNT 4.
2.SP4
3.SQL SERVER 6.5
4.Service PAck 5a for Sql Server 6.5
5.SP6a for NT
Workstation setup.
1.Member of the domain inwhich the SQL SERVER 6.5 is present
2.Sql client 6.5
3.SP4(for NT)
4.SP6a(for NT)
No Service packs were installed in the workstation.
When we try to connect the server from the server the MSSQLServer service stops.We even tried reinstalling the entire setup from scratch.
Kindly help us in this regard.
Thanks and Regards,
Gokul G
I am experiencing an issue with the MSSQLSERVER shutting down automically at 6:00 every 3 days. I do have 2 jobs that run at this time, but they run everyday. We did not install anything additional on the server and we are running SP3a. This just started on April 15, 2006. The Windows Event log displays the following message:
4/21/20066:00:08 PMMSSQLSERVERError(2)17052N/A<server name>The MSSQLSERVER service terminated unexpectedly.
The service stops and does not restart. It required me to restart the service manually.
Any help would be appreciated.
Hi
For 15 days now my SQL server service is terminating with the following error
MSSQLSERVER service terminated unexpectedly. It has done this 2 Time(s).
This service terminates and restarts automatically and sometimes doesnt restart we have to mannuly start it again.
Event ID: 7034.
Version Details
Version: MSSQL Server 2000
Service Pack: 3a
Build: 8.0.0.760
I have checked many forums most of them suggest to apply the latest service pack. But the same error has been reported by sites having SP4 also.
Kindly help.
Thank you
wasim
Hi
I am creating Alerts for MSSQLServer service shutdown. Could you please let me know the error of this.
Urgent please.
Thanks
Raj.
HII have server MSDE 2000 SP3frequently server stopped, and print in log file information:1)17310 :SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.2)17311 :SQL Server is aborting. Fatal exception c0000005 caught.3)The MSSQLSERVER service terminated unexpectedly.
View 2 Replies View RelatedHi
I am in weired move kindly help me out..I created report using sql server 2005 Reporting services..At one stage it is working fine with proper parameter but due to bad input parameter my report goes in hang mode..so i went to my DB server and restart my reporting service and then MSSQLSERVER I dont remember sequence (may be vice versa) now I am not able to get report when i am passing right parameter..I went to google and only I came to know that due to sequence of restart of services will cause this error..
error like..Application error:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Syste error:
The SQL Server Integration Services service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Kindly help me out.
T.I.A
Hello,I hope you guys can help me with a problem that I am facing...I have started the MSSqlServer service and SQLServerAgent serviceswith a domain username and password.There are periodic password resets to this user. Security policieswithin the company dictate that the password for this domain accountcannot be permenant.Would there be any way to automatically reset the pwd in theseservices instead of manually changing them each time?Thanks
View 1 Replies View RelatedHi,I changed the login for MSSQLSERVER service for 6.5 box to "Thisaccount" from "system account" and then again changed back to "systemaccount". Now I cann't connect thru Enterprize Manager to my server.All my services r running and I can connect to my database thru anapplication as before. I cannot re-boot the machine as it is inproduction. Any thoughts?Thanks in advance.Subodh
View 1 Replies View RelatedThis error is being displayed in the eventlog every minute. Any ideas on what it is referring too? I reviewed some posts but most point to specific problems of report server not running, or receiving this error during a run. We are receiving no errors at all. However this is jamming up the event viewer to make troubleshooting other issues very diffucult.
Event Type: Error
Event Source: Report Server Windows Service (MSSQLSERVER)
Event Category: Management
Event ID: 107
Date: 3/23/2007
Time: 8:20:16 AM
User: N/A
Computer: SPECTRUM_DB2B
Description:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
MSSQLServer service terminated unexpectedly
We are running SQL Server 2000 with SP4. This server has been running for the past six months with no SQL server problems. A Max of 10 users have access to the application running on this server.
The Event Viewer Log shows the
Source: MSSQLServer
Category: (2)
Type: Error
EventID: 17052
Description: The MSSQLSERVER service terminated unexpectedly.
No other error messages were seen in the SQL server log or windows event viewer.
The time when it terminated was not during peak load/activity.
The server is Windows 2003 with SP1. Any help would be appreciated.
Hi All,
I need a hand here, referring to this knowledge base on Microsoft (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q283811) i applied this knowledge base, and it worked, the MSSQL and SQLSERVERAGENT have run under local non admin account.
But after i installed SP1, MSSQL service is ok, but SQLSERVERAGENT wont run. The warning message is : "Some service run and then stop if they have no work to do."
Is there any way i can install SP1 but in the same time run SQLSERVERAGENT under local non admin account?
Your assistance will be much appreciated
thank you very much in advance.
Felix Adhitya
I tried to apply the SP2 on a newly installed SQL Server 2005 Developer edition. The installation failed and the MSSQLSERVER service does not start. I work on 32 bits Windows Server 2003 Standard Edition SP1 with all the patches up to date. I downloaded SQL Server 2005 SP2 on March 15, 2007.
Here are the error messages from 2 of the log files:
Summary.txt:
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) :
Status : Failure
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29534
Error Description : MSP Error: 29534 Service 'MSSQLSERVER' could not be started. Verify that you have sufficient privileges to start system services. The error code is (-2146885628) Cannot find object or property.
SQL9_Hotfix_KB921896_sqlrun_sql.msp.log:
Doing Action: ComponentUpgradeInstall
PerfTime Start: ComponentUpgradeInstall : Sun Mar 18 17:37:33 2007
<Func Name='ComponentUpgradeInstall'>
<Func Name='ComponentUpgrade'>
Failed to add file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG' to datastore in AddFileToFailureHandling
Service MSSQLSERVER with parameters '-r' is being started at Sun Mar 18 17:37:33 2007
Failed to start service MSSQLSERVER. Error code 2148081668
Service failed unexpectedly (2148081668)
Error Code: -2146885628
Windows Error Text: Cannot find object or property.
Source File Name: sqlsetuplibservice.cpp
Compiler Timestamp: Wed Jun 14 16:29:04 2006
Function Name: sqls::Service::Start
Source Line Number: 301
And below you can see the content of the SQL error log:
2007-03-18 19:46:11.51 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2007-03-18 19:46:11.51 Server (c) 2005 Microsoft Corporation.
2007-03-18 19:46:11.51 Server All rights reserved.
2007-03-18 19:46:11.53 Server Server process ID is 796.
2007-03-18 19:46:11.53 Server Authentication mode is WINDOWS-ONLY.
2007-03-18 19:46:11.53 Server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'.
2007-03-18 19:46:11.53 Server This instance of SQL Server last reported using a process ID of 712 at 3/18/2007 5:39:48 PM (local) 3/18/2007 3:39:48 PM (UTC). This is an informational message only; no user action is required.
2007-03-18 19:46:11.53 Server Registry startup parameters:
2007-03-18 19:46:11.53 Server -d C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf
2007-03-18 19:46:11.53 Server -e C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG
2007-03-18 19:46:11.53 Server -l C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf
2007-03-18 19:46:11.56 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-03-18 19:46:11.56 Server Detected 2 CPUs. This is an informational message; no user action is required.
2007-03-18 19:46:11.87 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2007-03-18 19:46:11.98 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-03-18 19:46:14.06 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-03-18 19:46:14.06 Server Database mirroring has been enabled on this instance of SQL Server.
2007-03-18 19:46:14.07 spid5s Starting up database 'master'.
2007-03-18 19:46:14.15 spid5s 1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2007-03-18 19:46:14.17 spid5s 0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2007-03-18 19:46:14.17 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2007-03-18 19:46:14.37 spid5s SQL Trace ID 1 was started by login "sa".
2007-03-18 19:46:14.42 spid5s Starting up database 'mssqlsystemresource'.
2007-03-18 19:46:14.50 spid5s The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2007-03-18 19:46:14.89 spid5s Server name is 'YODA'. This is an informational message only. No user action is required.
2007-03-18 19:46:14.89 spid9s Starting up database 'model'.
2007-03-18 19:46:15.06 spid9s Clearing tempdb database.
2007-03-18 19:46:15.67 spid9s Starting up database 'tempdb'.
2007-03-18 19:46:15.79 spid12s The Service Broker protocol transport is disabled or not configured.
2007-03-18 19:46:15.79 spid12s The Database Mirroring protocol transport is disabled or not configured.
2007-03-18 19:46:15.82 spid12s Service Broker manager has started.
2007-03-18 19:46:21.62 Server The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: 0x8009030d. Check certificates to make sure they are valid.
2007-03-18 19:46:21.62 Server Error: 17190, Severity: 16, State: 1.
2007-03-18 19:46:21.62 Server FallBack certificate initialization failed with error code: 1.
2007-03-18 19:46:21.62 Server Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2007-03-18 19:46:21.64 Server Error: 17182, Severity: 16, State: 1.
2007-03-18 19:46:21.64 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x80.
2007-03-18 19:46:21.64 Server Error: 17182, Severity: 16, State: 1.
2007-03-18 19:46:21.64 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x1.
2007-03-18 19:46:21.64 Server Error: 17826, Severity: 18, State: 3.
2007-03-18 19:46:21.64 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2007-03-18 19:46:21.64 Server Error: 17120, Severity: 16, State: 1.
2007-03-18 19:46:21.64 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Any advice???
How to prevent the hang on the initator service broker if the target service broker is not started?
Our case has two service brokers (two databases), sometime, the target is need to turn off. But the sitation is the initator service broker (in fact, the message is sent from triggers) become hang, I want to prevent this case and continue to operation, and the messages should queue and will continue to send to target service broker when it startup. How should I do?
I have connected to the SQL Server 2005 instance usign the SQL Server Management Studio; I have changed the default locations for the database and log files. I have also rebooted the machine. When I look in the SQL Server Configuration Manager in the properties for the SQL Server (MSSQLSERVER) I see that the data path is still set to the old value and this field is read-only. How can this can changed without going through the registry?
View 10 Replies View RelatedSql server service has been started with a normal user who do not have any permission but he is a domain user.
The sql server service can be started successfuly in cluster
But if the Same user is used to start the SQL Server Agent service there is an error.What is the mininumum priviledge to
start a sql server agent in cluster. Why it cannot the domain user cannot be used to start the sql agent service.
View 2 Replies View Related
I have installed SQL Server 2005 Standard Edition for our Team Foundation Server install. I have verified the installation and all seems well, except that the Analysis Services service does not remain started. I get a message like "Some services stop if there is nothing to do." The Analysis service needs to be running in order for the TFS install to succeed. How can I get the Analysis Services service to remain started?
Thanks in Advance
Hi,
My SQLEXPRESS service suddenly gives me this error.
ERROR: The SQL Server(SQLEXPRESS) service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.
My OS is Microsoft Windows Server 2003, Enterprise Edition, SP2.
It all started when I restarted the system prompted by the Windows updates.
Please help. Its urgent as this is one of the important servers to be managed.
Thanks and Regards
Madhu
I have configured Alwayson HA setup as following environment and versions, and working fine to client side by connected with AG Listener.
Two Node WSFC setup. Node1 (Primary), Node 2(Secondary Replica). Normal quorum(Not shared disk)
Server Platform: HyperV
OS: Windows server 2008 R2 64 bit with SP1
RDBMS: MS SQLSERVER 2012 64 bit with SP2
when I am doing testing Failover method between two nodes. automatic failover not happened.
Just shutdown Node1 and try to connect at client side by using AG Listener name but not succeeded, also Cluster name and AG Listener name are not pinging, Second node2 cluster service is not started by automatically due to as below errors. So how will connect client and overcome this issues? Any modification need to be done on both side WSFC and AlwaysOn SQL? for achieving and automatic failover.
Cluster network 'Cluster Network 1' is partitioned. Some attached failover cluster nodes cannot communicate with each other over the network. The failover cluster was not able to determine the location of the failure. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Client side got connected once Node1 get started again also cluster services started.
All,
I have installed sqlserver 2005 using the standard msdn universal installation discs on my laptop running vista business.
The mssqlserver service will not start automatically as the setup configures it
and I cannot start the service manually because I get the 'Access Denied' error message
I am logged on the the computer with adminstration privileges
Thank for all help received in advance,
Dave.....