|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
SQL InstallInstalled SQL server under local system account. Later changed the account
on which sql server & agent run to local user with regular priviledges. SQL agent does not work????? Books Online has some good info on this, for instance:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_overview_6k1f.asp -- Show quoteTibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ "docsql" <docsql@noemail.nospam> wrote in message news:%23dAtLhAUFHA.2124@TK2MSFTNGP14.phx.gbl... > Installed SQL server under local system account. Later changed the account on which sql server & > agent run to local user with regular priviledges. > > SQL agent does not work????? > Hello,
When you initially install Microsoft SQL Server to run under a Microsoft Windows NT account, SQL Server sets for that Windows NT account various Windows user rights and permissions on certain files, folders, and registry keys. If you later change the startup account for SQL Server (the MSSQLServer service) and the SQL Server Agent service by using SQL Server Enterprise Manager (SEM), SEM automatically assigns all the required permissions and Windows user rights to the new startup account for you so that you do not have to do anything else. This is the approach that Microsoft recommends you use to change the service account. However, if you use the Services applet that is in Control Panel or in Administrative Tools to change the startup account information for the MSSQLServer service or the SQL Server Agent service, there are additional permissions and user rights that must be set manually. If so, you can refer to the following article 283811 which discusses the steps you must take when you change the startup account information by using the Services applet. 283811 How to change the SQL Server or SQL Server Agent Service account without using SQL Enterprise Manager in SQL Server 2000 (283811) http://support.microsoft.com/?id=283811 What is the SQL server version and the operating system you use? What is the error message when starting the SQL Server Agent Service? If you receive the error 1053, you can refer to the following article: 322140 Error 1053 when you try to start SQL Server Agent http://support.microsoft.com/?id=322140 I hope the information is helpful. Sophie Guo Microsoft Online Partner Support Get Secure! - www.microsoft.com/security ===================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights. I used Enterprise Manager to change the account.
Once you change the account in EM, it will try to restart the SQL server for the new account to take into action. What I did was created a SQL login for the windows account (one with regular priviledges. The new startup account for SQL Server and SQL Server services) and assigned it SQL admin priviledges. Later I deleted the BUILTIN\Administrators group. That is when SQL Agent stops working. Show quote "Sophie Guo [MSFT]" <v-s***@online.microsoft.com> wrote in message news:3dY0DgHUFHA.388@TK2MSFTNGXA01.phx.gbl... > Hello, > > When you initially install Microsoft SQL Server to run under a Microsoft > Windows NT account, SQL Server sets for that Windows NT account various > Windows user rights and permissions on certain files, folders, and > registry keys. > > If you later change the startup account for SQL Server (the MSSQLServer > service) and the SQL Server Agent service by using SQL Server Enterprise > Manager (SEM), SEM automatically assigns all the required permissions and > Windows user rights to the new startup account for you so that you do not > have to do anything else. This is the approach that Microsoft recommends > you use to change the service account. > > However, if you use the Services applet that is in Control Panel or in > Administrative Tools to change the startup account information for the > MSSQLServer service or the SQL Server Agent service, there are additional > permissions and user rights that must be set manually. If so, you can > refer > to the following article 283811 which discusses the steps you must take > when you change the startup account information by using the Services > applet. > > 283811 How to change the SQL Server or SQL Server Agent Service account > without using SQL Enterprise Manager in SQL Server 2000 (283811) > > http://support.microsoft.com/?id=283811 > > What is the SQL server version and the operating system you use? What is > the error message when starting the SQL Server Agent Service? If you > receive the error 1053, you can refer to the following article: > > 322140 Error 1053 when you try to start SQL Server Agent > http://support.microsoft.com/?id=322140 > > I hope the information is helpful. > > Sophie Guo > Microsoft Online Partner Support > > Get Secure! - www.microsoft.com/security > > ===================================================== > When responding to posts, please "Reply to Group" via your newsreader so > that others may learn and benefit from your issue. > ===================================================== > This posting is provided "AS IS" with no warranties, and confers no > rights. > > > Hello,
You can set the SQL Server Agent service startup account to "System account" or "this account" in SQL Enterprise Manager (SEM). "System account" is the Local System Account. "this account" refer to an domain User Account. If SQL Server Agent service startup account is set to "System account", and the BUILTIN\Administrators account has been removed from SQL Server, you have to add 'nt authority\system' account to SQL server. You can run the following command in the SQL server query analyzer(QA): EXEC sp_grantlogin 'nt authority\system' go EXEC sp_addsrvrolemember 'nt authority\system', 'sysadmin' go If current Windows user has administrative permission, you can start the SQL server agent service. Otherwise, Select the "auto-start service when OS starts" option in the SQL server service manager, then restart the computer. SQL server agent service will be started when starting. If the issue still exists, check SQL Server Agent error log by performing the following steps: 1. Right-click the SQL Server Agent, click "Display error log". Let me know the exact error message. 2. View the Windows Application Log <http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/a d_perfmon_5qnn.asp> For your reference, the following article has addressed the issue: 237604 PRB: SQL Server Agent does not start and displays error 18456 http://support.microsoft.com/?id=237604 I hope the information is helpful. Sophie Guo Microsoft Online Partner Support Get Secure! - www.microsoft.com/security ===================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights. I get th following error
7/13/99 2:07:43 PM - ! [298] SQLServer Error: 18456, Login failed for user 'DomainName\UserName'. [SQLSTATE 28000] 7/13/99 2:07:43 PM - ! [000] Unable to connect to server; SQLServerAgent cannot start Show quote "Sophie Guo [MSFT]" <v-s***@online.microsoft.com> wrote in message news:Mev3FFVUFHA.388@TK2MSFTNGXA01.phx.gbl... > Hello, > > You can set the SQL Server Agent service startup account to "System > account" or "this account" in SQL Enterprise Manager (SEM). > > "System account" is the Local System Account. "this account" refer to an > domain User Account. > > If SQL Server Agent service startup account is set to "System account", > and > the BUILTIN\Administrators account has been removed from SQL Server, you > have to add 'nt authority\system' account to SQL server. > > You can run the following command in the SQL server query analyzer(QA): > > > EXEC sp_grantlogin 'nt authority\system' > go > > EXEC sp_addsrvrolemember 'nt authority\system', 'sysadmin' > go > > If current Windows user has administrative permission, you can start the > SQL server agent service. Otherwise, Select the "auto-start service when > OS > starts" option in the SQL server service manager, then restart the > computer. SQL server agent service will be started when starting. > > If the issue still exists, check SQL Server Agent error log by performing > the following steps: > > 1. Right-click the SQL Server Agent, click "Display error log". Let me > know the exact error message. > > 2. View the Windows Application Log > <http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/a > d_perfmon_5qnn.asp> > > > For your reference, the following article has addressed the issue: > > 237604 PRB: SQL Server Agent does not start and displays error 18456 > http://support.microsoft.com/?id=237604 > > I hope the information is helpful. > > Sophie Guo > Microsoft Online Partner Support > > Get Secure! - www.microsoft.com/security > > ===================================================== > When responding to posts, please "Reply to Group" via your newsreader so > that others may learn and benefit from your issue. > ===================================================== > This posting is provided "AS IS" with no warranties, and confers no > rights. > > > > > > > > The Windows account that Agent uses cannot login to SQL server. You need to add that account as a
SQL Server login and make it sysadmin. -- Show quoteTibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ "docsql" <docsql@noemail.nospam> wrote in message news:%23VAk5MpUFHA.628@tk2msftngp13.phx.gbl... >I get th following error > 7/13/99 2:07:43 PM - ! [298] SQLServer Error: 18456, Login failed for user 'DomainName\UserName'. > [SQLSTATE 28000] > 7/13/99 2:07:43 PM - ! [000] Unable to connect to server; SQLServerAgent cannot start > "Sophie Guo [MSFT]" <v-s***@online.microsoft.com> wrote in message > news:Mev3FFVUFHA.388@TK2MSFTNGXA01.phx.gbl... >> Hello, >> >> You can set the SQL Server Agent service startup account to "System >> account" or "this account" in SQL Enterprise Manager (SEM). >> >> "System account" is the Local System Account. "this account" refer to an >> domain User Account. >> >> If SQL Server Agent service startup account is set to "System account", and >> the BUILTIN\Administrators account has been removed from SQL Server, you >> have to add 'nt authority\system' account to SQL server. >> >> You can run the following command in the SQL server query analyzer(QA): >> >> >> EXEC sp_grantlogin 'nt authority\system' >> go >> >> EXEC sp_addsrvrolemember 'nt authority\system', 'sysadmin' >> go >> >> If current Windows user has administrative permission, you can start the >> SQL server agent service. Otherwise, Select the "auto-start service when OS >> starts" option in the SQL server service manager, then restart the >> computer. SQL server agent service will be started when starting. >> >> If the issue still exists, check SQL Server Agent error log by performing >> the following steps: >> >> 1. Right-click the SQL Server Agent, click "Display error log". Let me >> know the exact error message. >> >> 2. View the Windows Application Log >> <http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/a >> d_perfmon_5qnn.asp> >> >> >> For your reference, the following article has addressed the issue: >> >> 237604 PRB: SQL Server Agent does not start and displays error 18456 >> http://support.microsoft.com/?id=237604 >> >> I hope the information is helpful. >> >> Sophie Guo >> Microsoft Online Partner Support >> >> Get Secure! - www.microsoft.com/security >> >> ===================================================== >> When responding to posts, please "Reply to Group" via your newsreader so >> that others may learn and benefit from your issue. >> ===================================================== >> This posting is provided "AS IS" with no warranties, and confers no rights. >> >> >> >> >> >> >> >> > > Hello,
This issue occur because the BUILTIN\Administrators login does not have access to SQL Server or the BUILTIN\Administrators login has been removed from SQL Server, and the SQLAgent service is starting under the LocalSystem account. You can refer to the following to resolve the issue: 237604 PRB: SQL Server Agent does not start and displays error 18456 http://support.microsoft.com/?id=237604 To put the BUILTIN\Administrators account back into SQL Server, run the following commands in QA: EXEC sp_grantlogin 'BUILTIN\Administrators' go EXEC sp_addsrvrolemember 'BUILTIN\Administrators', 'sysadmin' go or you can run the command in my previous post to add 'nt authority\system' login to SQL Server. I hope the information is helpful. Sophie Guo Microsoft Online Partner Support Get Secure! - www.microsoft.com/security ===================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights.  
Other interesting topics
|
|||||||||||||||||||||||
