Whenever I restart the Server , SQL server service is starting properly, but the agent is showing the green sign in EM ,agent Log also its showing its started. But in EM the jobs are not showing the next run time its showing ( Date and time not available). When I double click the jobs its showing the following error message
Micorsoft SQL - DMO ( ODBC Sql state 42000)
Error 14258 : can not perform this operation while SQL server agent is starting)
FYI :This server contain the databases of SMS too .
SQL agent is using NT login with all permission & agent and sqlserver using the same NT username . SA password has not been changed for more than one year.
The SQL Server agent log is showing "waiting to recover database". What could be the reason ?
------------ Ray Miao at 6/5/2002 8:13:38 AM
Double check with sql service manager. Did you change sa pwd?
------------ Shaji at 6/5/2002 4:36:16 AM
Hi ,
Whenever I restart the Server , SQL server service is starting properly, but the agent is showing the green sign in EM ,agent Log also its showing its started. But in EM the jobs are not showing the next run time its showing ( Date and time not available). When I double click the jobs its showing the following error message Micorsoft SQL - DMO ( ODBC Sql state 42000) Error 14258 : can not perform this operation while SQL server agent is starting) FYI :This server contain the databases of SMS too .
We have SQL 2000 (SP2) , Our SQL server agent showing green light as started from EM , It is succussfully restarting from NT Services too . But When I open the properties of the jobs from EM its gives error message SQL DMO error " SQl Agent is starting , try later " . And in EM Next run Date & Time not available .
MDDB database is accessable & in Log file its recovered fully
The SQLAgent service was modified to login as a domain account. SQLAgent would not start. I made sure that the account was in the Admin group on the server, I setup the account as a System Administrator in SQL. I made sure that the network protocols in Client Network Utiliity and Server Network Utility where the same as other servers using the domain account. The message I'm getting is...
SQLServerAgent could not be started (reason: Unable to connect to server; SQLServerAgent cannot start).
I modified the properties for SQLAgent back to login as local account and I still get the same problem.
For three months I have be starting the SQL Agent using the following bat file
EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'.
Starting this week the agent is not starting. This is the error message
10/26/00 6:25:36 PM - ! [000] Password verification of the 'SQLAgentCmdExec' proxy account failed (reason: A required privilege is not held by the client)
I am unable to get SQL Agent service to run under the same domain name that my SQL Server service is running under. It will start and continue to run when Server and Agent are both ran under the Local Account. But once the services are switched over to the domain account, the Server starts, but the Agent fails. The domain user has administrative rights on the server, along with admin rights to the SQL instance.
Here is the event log.
Event Type: Error Event Source: SQLSERVERAGENT Event Category: Service Control Event ID: 103 Date: 3/28/2007 User: N/A Computer: SQL2 Description: SQLServerAgent could not be started (reason: SQLServerAgent must be able to connect to the SQL Server as SysAdmin, but '(Unknown)' is not a member of the SysAdmin role).
Any help would be greatly appreciated or links to threads with answers.
Hi, we have a SQL server 7.0 on windows 2000 m/c,from yesterday onwards suddenly sqlserver agent is not starting,till then it was working fine. I tried to start SQL server agent manually and i got following message
"[241] Startup error: Unable to initialize error reporting system (reason: The specified module could not be found) "
Then i tried to start from services in controll panel,but i could't.
Then i checked event log ,found following error messages
Application log:
1) "The description for event ID(105) in soure(SQL Server Agent) can not be found. The Localcomputer may not havethe nessary registry information or message DLL files to display messagees from a remote computer.The following information is part of the event: The handle is invalid."
Event ID: 105 Source : SQLServerAgent Category: Disk
system log:
1)The Sql server agent service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Hi Folks, Can anyone amongst u solve my problem..When i try to start the Sql Server Agent..i'm given the following error meassage.. Could not start Sql Server Agent.Error 2140.An Internal Windows NT error. Please help me if anybody can.
We have SQL Server 7.0 running on an NT 4.0 sp5 box. Whenever we stop the SQL Server Service, we get the message that SQL Agent will also be stopped. If we do this, all the services seem to stop fine, but when we try to start the SQL Server Agent Service back up, it won't let us. In order for it to restart, we have to reboot the server so that it starts 'automatically'. Does anyone have any ideas as to why this is?
How do you start SQL Agent? MS states not to start thru Service Manager as it may corrupt registry. There is no Resource for SQL Agent in 7.0 cluster. The service is down, need to start to get jobs to run. I've just checked (enabled) the properties so Agent will start on O/S reboot or start after Unexpected stop. How do I get it start in the meantime? Thanks!
Hi have you guys seen this error when trying to start the sql agent?
SQLServerAgent could not be started (reason: sqlserveragent must be able to connect to sqlserver as sysadmin, but '(unkown)' is not a member of the sysadmin rol.
What is this all about I can start the sql server service with the same account i'm trying to start the agent.
How can we start the SQL Server Agent without having physical acess to the server, I mean i have access to the EM which is installed on another server. How to start the SQL Server Agent , the login i use has sa rights ,
Hi, Running SQL 7.0 on NT4. When server boots the SQL Server Agent appears to start normally. NT Service starts, Event Viewer shows service is started, Service Control Manager shows service started.
However when I try to view a job or create a lob I get the following error:
Error 14258: Cannot perform this operation while SQLServerAgent is starting. Please try again later.
I am running windows 2003 and sql server 2005. i am following the directions in books online:
On the Start menu, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.
In SQL Server Configuration Manager, expand Services, and then click SQL Agent.
In the results pane, right-click any instance, and then click Start.
A green arrow on the icon next to the SQL Server Agent and on the toolbar indicates that SQL Server Agent started successfully.
Click OK.
the problem is i have nothing in Services. there is nothing to expand. is it installed wrong?? or is there another step before this that i have to do??
I've been struggling to figure out how to set the "Log on as" login for a SQL Server agent that isn't a member of the Administrators group.
Is this even possible? No matter what policy settings I assign the the user, I get an access denied error when I try to start the SQL Server Agent service. If that user is part of the administrators group, there are no errors.
I have no problems with other services and "log on as" logins...
All my SSIS packages consistently take 1 minute to start when they are scheduled via the SQL Agent.
For example, a package runs in 20 seconds in the BI Studio. I transfer it to the SQL server and store it in MSDB. I then run it manually from SSMS - Integration Services and it takes 20 seconds. I then schedule it via a job in the SQL Agent and it takes 1 minute 20 seconds.
I can see from some simple logging that there is consistently a delay of 1 minute between the job starting and the package starting.
I have also switched every occurrence possible of DelayValidation to TRUE in all my packages and tasks. All this did was reduce the package run time from 27 seconds to 20 - the 1 minute delay still exists.
This happens on all my packages on all my servers. Any ideas.....?
I wonder if anybody can shed any light on this problem. I have a SQL Agent job which has three steps, each step runs an SSIS package.
The job is scheduled to start at 11.00 pm, which is does successfully. However, it has been taking between 2 and 3 hours to run, which is way longer than it should.
When I've looked at the logging, I've found that the although the job starts at 11.00 pm, the first package (in job step 1) does not start executing until about 11.30. It finishes in about 5 minutes, there is then about an hour delay before the second package (in job step 2) starts. This finishes in about 10 minutes, then there is another hour delay before the third package (in job step 3) starts.
I've tried configuring the steps as SSIS jobs, and also as cmd jobs using dtexec, both exhibit the same behaviour.
Any ideas about what could be causing this delay? The packages are stored in msdb on the same server as the SQL Agent job, if that makes any difference.
I have a Win 2003 server running 3 instances of SQL 2000 Enterprise. The problem is I can only start 2 of the 3 Job Agents at a time, as the 3rd gets stuck in a starting state. Has anyone struck this problem before?
When I start SQL Server Agent it's shutting down minute after starting. I tried to set Alerts to send email. After I configured Database Mail ,I was able to send test email , however after that SQL Server Agent started to misbehave.
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?
i get this error below my test box what does it mean ,and my server doesnt start and gives error when i restart services 00/12/08 13:31:37.83 kernel SQL Server is starting at priority class 'normal' with dataserver semaphore = 1 (1 CPU detected, SMPStat=0). 00/12/08 13:31:37.84 server LogLRU buffers: 0 00/12/08 13:31:37.84 kernel initdata: no memory for kernel locks
I installed SQL Server 2005 a while back and just tried to use the ReportServer recently and ran into a problem.
I tried accessing using http://babby/ReportServer (my report server and db server are both on 'babby') and got an ASP.NET runtime error (which wasn't displayed to me). So next I accessed locally at the server (babby) and got this error:
The current identity (NT AUTHORITYNETWORK SERVICE) does not have write access to 'C:WINDOWSMicrosoft.NETFrameworkv2.0.50727Temporary ASP.NET Files'.
I have done some searching on the Internet and there doesn't seem to be much info at all about SSRS 2005. I did found some MSDN info that suggested that NT AUTHORITYNETWORK SERVICE is the correct account to use when running SSRS under Win Server 2003 which I am.
'babby' is a Windows Server 2003 machine running IIS 6.0.
I've Configured the Mirroring using the two machines, I've checked up everything,creation of end points successfully on both the machines, databases are in full recovery mode as well.
while Start Mirroring i'm facing following error :
TITLE: Database Properties ------------------------------ An error occurred while starting mirroring. ------------------------------ ADDITIONAL INFORMATION: Alter failed for Database 'MIS'. (Microsoft.SqlServer.Smo) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Alter+Database&LinkId=20476 ------------------------------ An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) ------------------------------ The server network address "TCP://DBD-P3-01047.macmill.com:5023" can not be reached or does not exist. Check the network address name and reissue the command. (Microsoft SQL Server, Error: 1418) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=1418&LinkId=20476 ------------------------------ BUTTONS: OK ------------------------------ and when i'm using the following command :
ALTER DATABASE [mis] SET PARTNER =N'TCP://DBD-P3-01063.macmill.com:5022' to start mirroring the following error has come up :
The partner server instance name must be distinct from the server instance that manages the database.
The ALTER DATABASE SET PARTNER command failed.
How can i resolve this issue?Help is greatly appreciated!!!! - Hitesh
I am having a problem in the Business Intelligence Development Studio. When I add and try to edit a Script Task or a Script Component, I click on the Design Script button and get one of two errors. For the Script task I get an error that states:
Cannot show the editor for this task. (Microsoft Visual Studio)
For the Script component I get:
Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)
For some reason or another it just will not start Visual Studio for Applications. I have uninstalled an re-installed several times. I have also researched and discovered that there is a bug when C# tasks are include in the project. However, this is not the case. Please help!
I installed SQL Server 2005 Integration services on Windows XP machine. Then I went to the SQL Server Configuration Manager and tried to Start the SSIS service. The "Log On As" value is "NT AUTHORITYNetworkService". But I get the follwoing error:
The request failed or the service did not respond in a timely fashion. COnsult the event log or other applicable error logs for details.
Event Log details: ------------------ 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.
I tried running the service using the "Local Service" and the "Local System" accounts also, but am still encountering the same error. What do I do...
Client found response content type of 'text/html', but expected 'text/xml'. The request failed with the error message: -- <html><head><title>Server Application Error</title></head> <body> <h1>Server Application Error</h1>The server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detail information. Please contact the server administrator for assistance.</body></html> --. (Microsoft.SqlServer.Management.UI.RSClient)
