You Need Administrator Privileges To Start/stop This Service Sqlsac
Jun 28, 2007
I'm getting this error message when I upgraded the SQL Server to install SSIS and other components.
===================================
The service did not respond to the start or control request in a timely fashion, you need administrator privileges to be able to start/stop this service. (SQLSAC)
------------------------------
Program Location:
at Microsoft.SqlSac.MainPanel.ServiceProgressBar.RefreshService()
A few service stop/start/restart questions on SQL Server 2005 SP2, whichI'll call SQLS.It looks as if there are *potentially* 6 ways to start/stop SQLSServices like the engine itself, integration services, reportingservice, Agent..-SQLS Configuration Manager-SQLS Surface Area Configuration (for Services and Connections)-Mgmt Studio Local (on server)-Mgmt Studio Remote (on client)-Windows Control Panel->Admin Tools->Services-Command Prompt (ala net start MSSQLSERVER)By policy, I am /not/ Administrator on the server. But I am SysAdminrole in SQLS. I have had various levels of success starting/stoppingservices in the ways listed above. In some I get Access denied, and inothers I get no msg and it simply doesn't work.Is there some special non-Admin OS group I need to be in to start/stopservices? Is this handled differently in the different interfaceslisted above?It seems like my best success for starting/stopping the engine and Agentis in /local/ Mgmt Studio, but /not/ remote Mgmt Studio - the optionsare greyed out on a remote client. Is this by design? Is it a SQLSbug?I'm sure I'm not the only SQLS DBA who does not have Admin rights on hisserver who wants to start/stop services. Generally speaking, how isthis intended to work?Any help appreciated.Allen JantzenA freshly minted DQLS DBA
Can any of you tell me how to create a login in SQL Server 6.5 with System Administrator privileges, like we can do with SQL 7 or SQL 2000 ? I don't want to use the sa login.
I have quick question. Ihave a job which consists of 9 steps. 9th step is: Exec xp_cmdshell 'c:mssql.bat'. in this batch file I am stopping and starting SQL services using net stop and net start command. This job is running perfectly but it is not giving the job history when I right click the job and view job history I can't see anything where as if I check the checkbox for Show step details it showing first 8 steps information but it is not showing 9th step information. Even I checked the Sysjobhistory system table in MSDB it shows only 8 steps information. What is the reason....
New here:) and hoping someone might be able to shed a little light on a problem I am having.
I have a job scheduled, which needs to be periodically stopped and then restarted. After looking through various places I think the start method and stop method are the best bets?:rolleyes: But not really sure to be honest.
Can anyone give me some tips/pointers/opinions on what would be the best way to do this. (have tried to setup a job with the said method in each step - but it doesn't like my syntax.
Is there any way to schedule stop and start of NT services at a particular time daily.
For eg: If i have a service by name TemServer and if i need to stop that service each night at 9:00 and restart as soon as it stops.??
And Is there any way to start and stop the services of NT from workstation. Each and every time i am going to the server room for stopping the service and restarting.
how i can do it?Under Xp/2000, i write a application that stop/start this serices, butunder Win98, how i do it?Exists a method via SqlServer or a dos command to stop/start the MSDEprogram?Thanks a lotTomas--Questa è una firma automatica di MesNews.Sito: http://mesnews.no-ip.com
What is impact, if i stop and start Synchronization, for one subscription.
When i start, will it resync all tables by dropping and recreating at subscription.
On Publisher,  from Location Publiction,   right click on subscription,       select View Synchronization Status,  From here, stop and start
Profiler was run against a database looking for "long running" queries. I used the Duration column to filter out the queries that I didn't want. When reviewing the output, I noticed that for some queries the StartTime was equal to the EndTime even though the Duration was set higher. My question is, "What can account for this discrepancy and what inferences should I draw about the difference?" Does the difference represent a resouce being locked or some other type of blocking (Duration) and once the query was allowed to run, it completed quickly? TIA
======================================= If Tyranny and Oppression come to this land, it will be in the guise of fighting a foreign enemy. -James Madison, fourth US president (1751-1836)
I want to create a package which start and stop the SQL server's services... i know i can achive this via NET COMMAND.... but i coudnt find in which task (SSIS) I can place that command?..
I also came across that I can achieve this using Execute Process task but for this I have to define executable file.... actually i dont want ne thing outside from my SSIS package
I want to tell to user about SQL Server Configuration Manager and wants to allow him "START / PAUSE / STOP" for SQL Server Express in system Tray. It is easy for the end user who don't know SQL Server.
Hi I have upgraded my local to sql server 2005, but still need to access the remote instance which is still at version 2008/8.0. Enterprise Manager has been removed (by the SQL server 2005 installation) Does anyone know how I can restart older version of SQL server instance (ie 2000/8.0) using SQL server Management Studio?
I don't have admin access on the server which the sql remote instance is hosted. Can get around it by asking the sys admin guy to do it for now but would prefer to continue to be able to do it myself. SQL Server Configuration Manager can only manage SQL server 2005 versions - a nice little caveat!
Is there a way to stop/start remote services using 'net stop/start'? - without having to write code.... I'll continue to search for a solution, but if someon can point me in the right direction, I'd be most greatful.
Hopefully, someone has a clue about this. We recently upgraded from SQL 6.5 to 7.0. Everything was fine until we changed the administrator password for our NT domain, which has about 26 servers on it. We also changed the local NT domain on the SQL server machine to match the network NT domain password. This seemed to work until a reboot a couple of days later. No we get a "failure to start do to logon failuer" message. Anyone experienced this problem?
For some reason the status lights in my Enterprise manager are no longer working. I am connected to the databases, but because the indicator lights are not working, I can`t get a quick visual status of my servers. Any way to get my lights back on?
We seem to be being plagued by the error below by our SQL Server agent. This happens almost everytime we restart the server that has been running for a day or two.
Our SQL Server Agent uses a none expiring domain credential. I understand that this problem only happens when the profile being used by the SQL Servr Agent has changed (password change). What puzzles me is that the login is A ok and no changes has been made to it's password.
We always resolve this problem by changing the login used in the SQL Server Agent to local and after that, returning it back to it's original domain login. Unfortunately, we cant always do this everytime something goes wrong.
Can anyone please help us shed a light on this? We're using SQL2k with SP3a. Thanks!
Error:
An error 1069 - )The service did not start due to logon failure) occurred while performing this service operation on the SQLServerAgent service.
I have a question about granting enough rights to allow a non admin user to start and stop a sql server service via the SQL Server Management Studio by right clicking on the server node.
I have changed the acl's of the SQL Server service security and gave the user rights to start and stop the service. This does allow them to connect remotly to the server using computer manager and they successifully start and stop the service. But, in SQL Server Management Studio the option still does not show up, unless he is a admin of the server.
Does anyone know what other security settings I need to address for the start and stop to show up when I right click on the server node?
Is there a script that I can run to stop a particular SQL server service onWin2003 server? I'm looking for a similar script to restart that service aswell. Thanks.
I program a batch file for SQL server2000 disarstrer recovery. It just stops sqlserver service and copy data file to a flash drive, then restart service.
I have been getting this message in the event viwer and my SQL server goes down. I have to go and start the service once again. Can somebody throw some light as how to solve this problem?
Installing MSDE (SP3) on a clean updated Win-XP system with all the latest fixes installed unsuccesfully. A clean systems means a fresh installed Win-XP, updated all using webupdate. And Excel 2003 installed. Thats all (not even AntiVirus (yet))
We are trying to set up SQLAgent Proxy account. If the SQLServer service id is a domain admin, do we still have to add it to the local administrators group?
Hello, I have a Question/doubt on SqlDependency.Start/SqlDependency.Stop.
After the implementation of my solution the question sounds "stupid" ... maybe is only the stress due to the fact that I'm going to deploy the application on Test.
Anyway.. I developed this application (windows application) that uses query Notification features to subscribe and get notification from Sql Server 2005 so it use the tipical pattern: SqlDependency.Start, SqlDependency_OnChange,SqlDependency.Stop.
This is application is installed on several client so actually I get have several notifications running on the Server.
When one of the client exit the application and call SqlDependency.Stop the service, queue and procedure are dropped.
Does the command drops all the query notification' service, queue and procedure running on the instance or only the one created by the specific user?
Please help! I am new in SQL Server 2000 Administration. My manager had ask me to manage a SQL Server, but Windows Adminstrator refuse to give me Local Admin rights. I only have sa account to login to databases. I don't know any excuses or reasons to give to Windows Adminstrator so that he can give me the local admin rights. If any one have this answer, please help. Thank you.
Something very weird happened this morning... I booted my computer as usual, but for some reason SQL service stopped by itself. I tried to start it again, but it just doesn't respond. I open up Service Manager, clicked on refresh services, but still no response. The "start service" button is available for me to press, but when I press it it doesn't seem to do anything.
Note that sql service was running last night as I switched off computer. I haven't changed anything since.
i have problem after installing SQLServer 2000 Developer Edition. i try to start the service from Service Manager window, but i can't start it. It says:
"The service did not start due to a logon failure. An error 1069 - (The service did not start due to a logon failure.) occured while performing this service operation on the MSSQLServer service."
please help me to solve this problem. i'm getting a little frustated
I work on a product installed on a CD ROM. I would like, if the costumer installs our product for a SQL Server database, to know how, with a batch, starts the necessary SQL Services if they aren't started yet when we run our Java application.
