Sql Server Agent not starting automatically in failover in a clustered environment.

Hi,
We are running Sql Server 2008 R2 as a 2 node cluster in Windows 2008 R2
server. In the Sql Server Configuration manager we find that service of
the Sql Server(database engine) as got a start mode as manual being
an instance in the 2 node cluster. When the node in which the service is
running fails the the Sql Server service gets started in the other node. However
we find that the Sql Server Agent service(whose start mode is also in manual)
does not get started automatically in the other node along with the Sql Server
service.Why does the cluster service do not start Sql Server agent service as well.
Should we make the Sql Server agent service start mode to be automatic
instead of being manual as it is now? Thanking you in advance
Binny Mathew

Folks - the startup type of all clustered services should be set to manual - when you virtualize SQL Services, they are put in manual startup mode and this should not be changed. It is the cluster manager which starts the SQL and SQLAgent when a
failover happens (SQL does not start SQLAgent). If your SQLAgent doesn't start after a cluster failover, check the SQLAgent logs to see what the root cause of the problem is and rectify it. You should not change the startup type to "Automatic" -
leave it as manual
Satish Kartan www.sqlfood.com
I suspect that your clustered SQLAgent resource is currently NOT dependent on SQL resource. If not, make SQLAgent dependent on SQL resource, which will coerce SQLAgent to wait for the SQL resource to come online before it brings itselft (SQLAgent) resource
online, when a failover happens.
Satish Kartan www.sqlfood.com

Similar Messages

Sql server agent not starting

I installed sql server 2008 r2 sp2
sql server agent is not allowing me to start it.
I run SSCM right click agent but start,stop menus are disabled

i have only one sql instance named SQLEXPRESS
The SQL Server Agent is installed with the Express Edition of SQL Server, but it's not a Feature of the Express Edition, therefore you can't start the Agent.
See
Features Supported by the Editions of SQL Server 2014
Olaf Helper
[ Blog] [ Xing] [ MVP]

Oracle service, Listener and http server does not start automatically

Hello,
I have Oracle 9i release 2 installed on Unix HP box if system restart in case of power failure the Oracle service, Listener and http server does not start automatically, is there any ready reference available to check what's wrong is happening(I don't have knowledge of Unix).
Thanks, Khawar.

Hi Rajesh,
Thanks for reply, I will check this link and will be back if facing problem.
Regards, Khawar.

SQL Server Agent not appearing in Management Studio

Hi there,
I have SQL Server set up on a server and I can't see the Agent in Management Studio.
When I check the services it says it is there and started.
I have the Enterprise edition installed.
Funny thing is it doesn't show when I am on the server itself through Management Studio, however, on my local pc, when I connect to the server through Management Studio, I can see the Agent through there and I have jobs there that run successfully and everything.
Its just when I log directly on the box and load up Management Studio, I don't see it.
Any thoughts?
Thanks!

a) Is there a possibiity that you are using SQL Server Management Studio Express edition, on your server instead of (full or complete edition of management studio that came with SQL enterprise edition media)
one way to tell if you are using sql express studio is under management you will be missing Resouce Governor under management node, Resource governor mangeability feature is only available if you have install management studio that comes with an enterprise
edition only
OR
b) account under which you are logged in your server does not have privileges to view SQL Server Agent (the user need to be member of certain role in msdb database to view sql agent see
http://msdn.microsoft.com/en-us/library/ms188283.aspx )
c) When you installed SQL managment stuido, which option did you choose for management studio (Basic or Complete)..?

Sql server agent not work

hi every one ,
i use sql server agent to make a job which delete some rows from my table at 12:00 AM
this job works on (Mydatabase1) but when i make another job to another database(Mydatabase2)
i get this error from ViewJob HIstory :
Myjob2,Error,1,FATMA\MSSQLSERVER2008,Myjob2,step2,,Executed as user: NT AUTHORITY\SYSTEM. DELETE
failed because the following SET options have incorrect settings: 'QUOTED_IDENTIFIER'. Verify that SET options are
correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query
notifications and/or XML data type methods and/or spatial index operations. [SQLSTATE 42000] (Error 1934). The step
failed
please inform me what is that error means?and how can i fix it?and why this job work to database and not work for another!!!
best wishes
fatma
fatma mohamed

Hi Miloslav Peterka,
i set Quoted Identifiers to true it was false,it woorked in first time after that i get this error(but in my worked job on myDatabase1 the Quoted Identifiers was false.)
Date  24-05-2010 10:44:28 ص
Log  Job History (AttendanceJob)
Step ID  0
Server  FATMA\MSSQLSERVER2008
Job Name  AttendanceJob
Step Name  (Job outcome)
Duration  00:00:01
Sql Severity  0
Sql Message ID  0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted  0
Message
The job failed. The Job was invoked by User sa. The last step to run was step 1 (attStep).
wat is the reason of that error?
best wishes
fatma mohamed

SQL 2005 Server Agent not starting job

Apologies if this question has been asked elsewhere on these forums, I've had a search around and have not been able to find something with the same issues.
Last year I took over management of a SQL server (SQL2005 on a Server 2003 R2 O/S), as part of the expansion of operation the DB server is being used for an agent job was created to take customer information from our web site and, where the customer has
selected to be contacted, pass those details to our dialler system, so we can rech our customer ideally within 20 minutes of them interacting with the website.
This job runs daily Monday to Friday from 8am to 4:30pm at 15 minute intervals and once a day at 5pm on Saturday and Sunday(same job with muliple schedules), 3 week ago the Saturday job failed to start, then following week the Sunday job failed to start
then last weekend the job failed to start on both Saturday and Sunday. There have been no updates or changes made to the job or the server and the job has run for 6 months with this multiple scehduling without any issues at all.
I have checked through the server event/system/application logs and the SQL logs (that I know of) and can find no evidence of errors that would have an effect on the SQL or SQL Agent operation, I can also find no evidence that the server made an attempt
to start the job at all, the application log will normally show an event 12288 and 12289 with the source of SQLISPackage for the start and stop of the job. There is no event start notice shown in the application event log on weekend days the job has failed
to start. I've check the Agent service status, as well as all the other SQL services and they are all running as they should be.
Does anyone have any ideas where I should be looking next for the cause of this issue or has anyone ever experienced this before and found a cause?
Many thanks
Stuart.

Hi all,
thank you for your replies, I will try to address the issues/questions you have raised.
@Satish - The job takes on average 40 seconds to complete, so there would no chance of the previous job run still being active and stopping a new attempt. Also on the days that the job has failed it is the only time that day that the job is run.
@Sofiya Li - There are no errors to report, the job simply fails to start at all, this is bourne out
by the 'Job Step Execution History For The Last 7 Days' this shows no that the job ran sucessfully with no fails or retrys, so there are no error messages to post or invesitgate. Running the job manually results in a success (but the job runs every 15 minutes
anyway during the day without fails), the job uses the same credentials during the daily 15 minutes runs on weekdays as it does on the weekends, also if the website had any issues capturing customer information the missing information would not be in the table
that the dialling information is drawn from and the job should still start and run even if the website capture is not working(these are seperate jobs), it would just return no information.
@Shanky_621 There is normal scheduled maintenance that runs on the DB but this occurs at midnight. The
logs show that all services were running and nothing was in a wait/held state.
Thanks again for your suggesions
Stuart

SQL Server service not starting

Hi,
In my environment we have configured SQL server clustering. Currently we are getting the following error and the service is not starting up.
ERROR: TDSSNIClient initialization failed with error 0x2741, status code 0x1.

Hi winoa,
According to your description, you come across the error that TDSSNIClient initialization failed with error 0x2741. Please help to post the full error message from both SQL Server error log and cluster log for further analysis.
Based on my research, this issue could happen due to setting up SQL Server failover cluster over different subnets using these three SQL Server versions(SQL Server 2005, SQL Server 2008, or SQL Server 2008 r2), hardware issue, or that disk and network name
are offline.
Please pay attention to the points below to troubleshoot your issue.
•If you set up SQL Server failover cluster over multiple subnets using the versions of SQL Server 2005, SQL Server 2008 or SQL Server 2008 r2, please make all the nodes in the same subnet, since SQL Server multi-subnet failover cluster is not supported among
those three versions of SQL Server. If possible, you could use the later versions (SQL Server 2012 or 2014) for SQL Server multi-subnet failover cluster.
• Make sure that disk and network name are online.
Regards,
Michelle Li

Sql server will not start - Database 'model' cannot be opened. It is in the middle of a restore.

Sql server service will not start after server reboot:
2009-08-13 14:15:43.94 spid7s      SQL Trace ID 1 was started by login "sa".
2009-08-13 14:15:43.97 spid7s      Starting up database 'mssqlsystemresource'.
2009-08-13 14:15:43.97 spid7s      The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
2009-08-13 14:15:44.30 Server      A self-generated certificate was successfully loaded for encryption.
2009-08-13 14:15:44.30 spid7s      Server name is 'WIN-37R9WFWAJIB\MSDB1'. This is an informational message only. No user action is required.
2009-08-13 14:15:44.32 spid10s     Starting up database 'model'.
2009-08-13 14:15:44.32 Server      Server is listening on [ 'any' <ipv6> 49167].
2009-08-13 14:15:44.33 Server      Server is listening on [ 'any' <ipv4> 49167].
2009-08-13 14:15:44.33 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSDB1 ].
2009-08-13 14:15:44.33 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2009-08-13 14:15:44.35 spid10s     The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
2009-08-13 14:15:44.38 Server      Server is listening on [ ::1 <ipv6> 49168].
2009-08-13 14:15:44.38 Server      Server is listening on [ 127.0.0.1 <ipv4> 49168].
2009-08-13 14:15:44.38 Server      Dedicated admin connection support was established for listening locally on port 49168.
2009-08-13 14:15:44.39 spid10s     Error: 927, Severity: 14, State: 2.
2009-08-13 14:15:44.39 spid10s     Database 'model' cannot be opened. It is in the middle of a restore.
2009-08-13 14:15:44.49 spid10s     Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2009-08-13 14:15:44.50 spid10s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informa
there is plenty of room on the server, so i dont think its a disk space issue. i am able to start the service as such:
C:\Users\Administrator>net start MSSQL$MSDB1 /c /m /T3608
The SQL Server (MSDB1) service is starting.
The SQL Server (MSDB1) service was started successfully
sqlcmd -e
1> select name, status from sysdatabases;
2> go
select name, status from sysdatabases;
name
                                                 status
master
                                                       65544
tempdb
                                                       65544
model
                                                       65568
msdb
                                                  1073807368
SS_DBA_Dashboard
                                                  1073807368
(5 rows affected)
model is in RESTORING state and I dont know how to fix it. I am running simple backups, so I have a somewhat recent backup of model.bak but when I attempt to restore it I get an error:
1> restore database model
2> go
restore database model
Msg 3112, Level 16, State 1, Server WIN-37R9WFWAJIB\MSDB1, Line 1
Cannot restore any database other than master when the server is in single user
mode.
Msg 3013, Level 16, State 1, Server WIN-37R9WFWAJIB\MSDB1, Line 1
RESTORE DATABASE is terminating abnormally.
other forums suggest manually updating the status column but i dont know if my syntax is wrong or it just cant be done in sql server 2008:
1> begin transaction
2> update sysdatabases set status=16 where name='model'
3> ;
4> go
begin transaction
update sysdatabases set status=16 where name='model'
Msg 4406, Level 16, State 1, Server WIN-37R9WFWAJIB\MSDB1, Line 2
Update or insert of view or function 'sysdatabases' failed because it contains a
derived or constant field.
1>
yet another forum suggested taking a cleanly shut down model.mdf and model.ldf from another sql server 2008 instance and placing those in the data directory while moving the 'restoring' ones to a backup location. this didnt work either. any help is appreciated im new to sql server and this is very frustrating! thanks in advance!

I have the same issue on SQL Server 2008R2, after a server reboot, but none of the NET START commands or command line attempts are successful to start the Service.
NET START command results in "Access Denied" "System Error 5" and the Command line attempts result in
Server      Error: 17058, Severity: 16, State: 1.
Server      initerrlog: Could not open error log file ''.
Any help?
SQL Error log file:
2011-03-29 16:50:49.40 Server      (c) Microsoft Corporation.
2011-03-29 16:50:49.40 Server      All rights reserved.
2011-03-29 16:50:49.40 Server      Server process ID is 7292.
2011-03-29 16:50:49.40 Server      System Manufacturer: 'Dell Inc.', System Model: 'PowerEdge T710'.
2011-03-29 16:50:49.40 Server      Authentication mode is MIXED.
2011-03-29 16:50:49.40 Server      Logging SQL Server messages in file 'E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2011-03-29 16:50:49.40 Server      This instance of SQL Server last reported using a process ID of 7448 at 3/29/2011 4:30:06 PM (local) 3/29/2011 8:30:06 PM (UTC). This is an informational message only; no user action is required.
2011-03-29 16:50:49.40 Server      Registry startup parameters:
-d E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
-T 4616
2011-03-29 16:50:49.42 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-03-29 16:50:49.42 Server      Detected 24 CPUs. This is an informational message; no user action is required.
2011-03-29 16:50:49.84 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.
2011-03-29 16:50:49.84 Server      Lock partitioning is enabled. This is an informational message only. No user action is required.
2011-03-29 16:50:49.86 Server      Node configuration: node 0: CPU mask: 0x0000000000fff000:0 Active CPU mask: 0x0000000000fff000:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2011-03-29 16:50:49.86 Server      Node configuration: node 1: CPU mask: 0x0000000000000fff:0 Active CPU mask: 0x0000000000000fff:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2011-03-29 16:50:49.89 spid9s      Starting up database 'master'.
2011-03-29 16:50:49.95 spid9s      CHECKDB for database 'master' finished without errors on 2011-03-18 08:46:34.257 (local time). This is an informational message only; no user action is required.
2011-03-29 16:50:49.95 spid9s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2011-03-29 16:50:49.97 spid9s      SQL Trace ID 1 was started by login "sa".
2011-03-29 16:50:49.97 spid9s      Starting up database 'mssqlsystemresource'.
2011-03-29 16:50:49.99 spid9s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2011-03-29 16:50:50.20 spid13s     Starting up database 'model'.
2011-03-29 16:50:50.20 spid9s      Server name is 'XXXX'. This is an informational message only. No user action is required.
2011-03-29 16:50:50.21 Server      The certificate [Cert Hash(sha1) "C41DC20703F049763778AC2842C3C8A3A2C6EED4"] was successfully loaded for encryption.
2011-03-29 16:50:50.21 Server      Server is listening on [ 'any' <ipv6> 1433].
2011-03-29 16:50:50.21 Server      Server is listening on [ 'any' <ipv4> 1433].
2011-03-29 16:50:50.21 Server      Server local connection provider is ready to accept connection on [
\\.\pipe\SQLLocal\MSSQLSERVER ].
2011-03-29 16:50:50.21 Server      Server named pipe provider is ready to accept connection on [
\\.\pipe\sql\query ].
2011-03-29 16:50:50.21 Server      Server is listening on [ ::1 <ipv6> 1434].
2011-03-29 16:50:50.21 spid13s     The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
2011-03-29 16:50:50.21 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2011-03-29 16:50:50.21 spid13s     Error: 927, Severity: 14, State: 2.
2011-03-29 16:50:50.21 spid13s     Database 'model' cannot be opened. It is in the middle of a restore.
2011-03-29 16:50:50.21 Server      Dedicated admin connection support was established for listening locally on port 1434.
2011-03-29 16:50:50.22 spid13s     Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in
the event log that may indicate why the tempdb files could not be initialized.
2011-03-29 16:50:50.22 spid13s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Login Server does not start automatically

Dear all,
When the machine is started, i cannot get desktop login automatically. Everytime i have to start with this command /usr/dt/bin/dtlogin -daemon; exit.
Even i have used this command /usr/dt/bin/dtlogin -e and i get the message that automatic login is enabled but even then it is not enabled.
Can anyone guide me.
Thanks
Imran Hasware

i checked with svcs gdm2-login, it was disabled. Then i executed svcadm enable gdm2-login, it didn't give me any message and executed.
When i checked again svcs gdm2-login, the state was changed from disable to offline.
I tried svcadm enable -r gdm2-login and svcadm restart gdm2-login, but no message and the state remain offline.
I restarted the machine but the state is offline.

SQL Server Agent Jobs- Not running

Team,
We have a production database hosted on SQL Server 2008R2 SP2(10.50.4000). We have application jobs which are scheduled and basically have packages called from this job. These jobs were running all good till yesterday and it has stopped working since yesterday
even though its enabled. Manual runs are successful. Other jobs are running fine.
Checked the Owner of these jobs and the account is SQL Server account which is a proxy account. It had enforce password policy. I have removed that and reset the password to original. However it didnt work.
The last change on this server was windows patching which was performed last week. Apart from that the SQL Server agent service was changed. This is a clustered environment.
The last resort is restart the agent, however would like to get some inputs before I perform this action.
Please let me know your valuable inputs.
Regards,
Sharath

If job is not executed at all, that is, there are no entries in the job history, check:
1) The job is enabled.
2) The schedule(s) is enabled.
3) The scdedule does not have an end date has has passed.
4) And that all other conditions on the schedule says that the job should run.
Erland Sommarskog, SQL Server MVP, [email protected]

SQL Server Agent - Job History not being recorded (SQL Server 2005)

I have been trying to get to the bottom of an issue with SQL Server Agent not recording any job history. I am using SQL Server 2005 on a single Windows Server 2008 machine (i.e. no other domain controllers/active directory servers).
The SQL Server Agent service is configured to 'Log On As' NT user account 'sqlagent'. The jobs themselves are executed successfully (all 'Transact-SQL' type steps actually use the 'sa' account) however the there is no actual job history to be found for any
of the jobs -- in the SQL Activity monitor, the 'Last Run Outcome' is always 'Unknown' and the 'Last Run' date is always 'Never' for all jobs; in the SQL Job History Viewer there are no entries for any instances of a job being executed.
The 'sqlagent' NT user account ia a member of the 'Administrators' NT group; the 'Administrators' group appears under Security > Logins on the database server. I have another server that also uses the same setup with a 'sqlagent' NT user account, on that
database server the 'sqlagent' user account appears under Security > Logins and the SQL job history works correctly. I have attempted to add the 'sqlagent' to the Logins on the affected server using the SQL Server Surface Area configuration but this operation
returns an error, detailed below.
Additionally, I have attempted to use the built-in NT system account 'NETWORKSEVICES' to run the SQL Agent Service but this also results in exceptions in the error log and no job history being recorded. The entries in the error logs are very similar to those
from the 'sqlagent' NT user account but instead the user is referred to as 'NT AUTHORITY\ANONYMOUS LOGON' in the error logs, again these are detailed below.
Many thanks in advance for anyone's time and help with this issue!
Arthur
The following errors are raised in SQL Server Agent > Error Logs each time a job is executed:
Date 11/11/2012 18:30:01
Log SQL Agent (Current - 11/11/2012 18:30:00)
Message
[298] SQLServer Error: 18452, Login failed for user ''. The user is not associated with a trusted SQL Server connection. [SQLSTATE 28000]
Date 11/11/2012 18:30:01
Log SQL Agent (Current - 11/11/2012 18:30:00)
Message
[382] Logon to server 'XXXXXXXX' failed (ConnAttemptCachableOp)
If the SQLAgent service is configured to use the NT system account 'NETWORKSERVICE' then the following errors are returned instead:
Date 29/10/2012 18:30:15
Log SQL Agent (Archive #1 - 29/10/2012 18:38:00)
Message
[298] SQLServer Error: 18456, Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [SQLSTATE 28000]
Date 29/10/2012 18:30:15
Log SQL Agent (Archive #1 - 29/10/2012 18:38:00)
Message
[382] Logon to server 'XXXXXXXX' failed (ConnAttemptCachableOp)
I have tried granting the 'sqlagent' NT user account with SysAdmin Server Role privaledges using the SQL Server User Provisioning tool in SQL Server Surface Area Configuration, but this always throws the following, similar error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Error: 18452)
===================================
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18452&LinkId=20476
Server Name: 127.0.0.1,1344
Error Number: 18452
Severity: 14
State: 1
Line Number: 65536
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at sqlprov.SysAdminServerRole.ProvisionInstance(Instance instance, String userName)
at sqlprov.ProvisionTask.Provision(Instance instance, String userName)
at sqlprov.MainForm.ProvisionTasks()

Hi Rama,
Thanks for your reply. I have run the query you specified and can see only one entry with "NTLM" in the auth_scheme column, all of the rest have "SQL". It figures that the entry with "NTLM" is relating to the one NT user account that can successfully log
in to the service (as mentioned in my reply to Nag above, this is the NT user account that installed the service on the machine). I have also executed the same query on the other machine that I mentioned in my original post and this contains two "NTLM" entries,
I'd assume that these relate to the NT user that installed the software and the correctly working "sqlagent" NT user account that is correctly logging the job history on that machine.
I think the problem is very much to do with granting access to new NT user accounts, as per the KB article that you have quoted above. In this case, it is not relating to scenarios 1 or 2 as these relate to SQL Server logins and this issue is about a Windows
Authentication login. As I mentioned to Nag above, I am unable to grant any NT user accounts with access to the service however the NT accounts are all defined locally on the same machine as the SQL server is installed (i.e. there is no domain controller,
active directory controller, etc) so I don't understand how the Windows login cannot be verified.
Any further advice on the issue would be greatly appreciated, please let me know if there is any more information I can provide to help diagnose the problem.
Many thanks!
Arthur

Unable to get SQL Server Agent to run after installing SQL 2012 Standard with SP1

I am unable to get SQL Server Agent to run after installing SQL 2012 Standard with SP1. Log message is as follows:
Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\xplog70.dll'.
Error: 17750, Severity: 16, State: 0.
Could not load the DLL xplog70.dll, or one of the DLLs it references. Reason: (null).

Hi JFriedley,
According to your error message, there might three reasons for this issue.
xplog70.dll is corrupt, you need to check if you have any SQL Server running on same file version and same production
edition. If xplog70.dll is corrupt, you can copy it from the new server where agent is running fine to your problematic server.
Native client not installed properly. If you try applying any latest Service Pack or Cumulative Update then check if the SQL Server Agent can start, if that also doesn’t solve issue then try to reinstalling SQL Server Native client from SQL Server setup
files.
There is a similar issue about error 17750, you can review the following article.
http://blogs.lostincreativity.com/sqldba/sqlserver-error-17750-could-not-load-the-dll-xpstar90-dll/
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

11.1.1.5 Presentation Server won't start automatically

Hi, gurus. Interesting problem with 11.1.1.5. 4 of 5 OBIEE services start automatically. Presentation Server doesn't. An excerpt from sawlog0.log is shown below. What's odd is that even though it fails when starting automatically, we can go into Fusion Middleware and start it manually - no problems there. So it can start, and from that point everything works great, it just won't start along with all of the other services.
Any ideas?
[2012-08-22T14:29:47.000-05:00] [OBIPS] [ERROR:16] [] [saw.dms.conext.unwrap] [ecid: 004lvOK0SKHCwkYzLoePOA00014t000001,0:29] [tid: 1107712320] Failed to restore ctx from reference[[
File:executioncontext.cpp
Line:286
Location:
saw.dms.conext.unwrap
saw.threadpool
saw.threads
ecid: 004lvOK0SKHCwkYzLoePOA00014t000001,0:29
ThreadID: 1107712320
[2012-08-22T14:29:47.000-05:00] [OBIPS] [NOTIFICATION:1] [] [saw.rpc.server.listen] [ecid: 004lvOK0SKHCwkYzLoePOA00014t000001,0] [tid: ] Server shutdown initiated by OPMN.[[
File:socketrpcserver.cpp
Line:818
Location:
saw.rpc.server.listen
saw.sawserver
ecid: 004lvOK0SKHCwkYzLoePOA00014t000001,0
[2012-08-22T14:29:47.000-05:00] [OBIPS] [NOTIFICATION:1] [] [saw.sawserver] [ecid: 004lvOK0SKHCwkYzLoePOA00014t000001,0] [tid: ] Oracle BI Presentation Services are shutting down.[[
File:sawserver.cpp
Line:712
Location:
saw.sawserver
ecid: 004lvOK0SKHCwkYzLoePOA00014t000001,0
[2012-08-22T14:30:33.000-05:00] [OBIPS] [NOTIFICATION:1] [] [saw.sawserver] [ecid: ] [tid: ] Oracle BI Presentation Services (OBIPS) 11.1.1.5.0 (Build 120325.0800 BP2 64-bit) are starting up.[[
File:sawserver.cpp
Line:465
Location:
saw.sawserver
ecid:
[2012-08-22T14:30:35.000-05:00] [OBIPS] [NOTIFICATION:1] [] [saw.sawserver] [ecid: ] [tid: ] Oracle BI Presentation Services are shutting down.[[
File:sawserver.cpp
Line:712
Location:
saw.sawserver
ecid:
[2012-08-22T14:30:41.000-05:00] [OBIPS] [NOTIFICATION:1] [] [saw.sawserver] [ecid: ] [tid: ] Oracle BI Presentation Services (OBIPS) 11.1.1.5.0 (Build 120325.0800 BP2 64-bit) are starting up.[[
File:sawserver.cpp
Line:465
Location:
saw.sawserver
ecid:
[2012-08-22T14:30:41.000-05:00] [OBIPS] [NOTIFICATION:1] [] [saw.sawserver] [ecid: ] [tid: ] Oracle BI Presentation Services are shutting down.[[
File:sawserver.cpp
Line:712
Location:
saw.sawserver
ecid:
]]

Alas, although out-of-sync GUIDs fit all of the clues, that wasn't the answer.
The problem still exists. Here's the relevant portion of the opmn.log file.
These first five sections represent an attempted start of all services in Fusion Middleware by clicking Start All
Request 1fa starts the BI Server successfully.
Request 1fb starts the BI Scheduler successfully.
Request 1fc attempts to start the Presentation Server but fails.
Request 1fd starts the Java Host successfully.
Request 1fe starts the Cluster Controller successfully.
So the Presentation Server will not start automatically as a part of Start All.
However, manually clicking 'Start Selected' for the Presentation Server (request 236 below) starts the service. So the short version is that we can start it manually, but not as a part of Start All.
[2012-08-23T16:03:58][opmn][TRACE:1][667][OPMN]Request 1fa Started. Command: /start?ias-component=coreapplication_obis1
[2012-08-23T16:03:58][opmn][TRACE:1][662][OPMN][code:pm-process]Starting Process: coreapplication_obis1~OracleBIServerComponent~coreapplication_obis1~1 (1181693061:0)
[2012-08-23T16:03:59][opmn][TRACE:1][][OPMN][code:libopmncustom]Process Ping Failed: coreapplication_obis1~OracleBIServerComponent~coreapplication_obis1~1 (1181693061:8643) [No addresses for the request.]
[2012-08-23T16:03:59][opmn][TRACE:1][][OPMN][code:libopmncustom]Process Ping Failed: coreapplication_obis1~OracleBIServerComponent~coreapplication_obis1~1 (1181693061:8643)
[2012-08-23T16:03:59][opmn][TRACE:1][][OPMN][code:libopmncustom]Ping failed in Ready callback for proc:1181693061
[2012-08-23T16:04:01][opmn][TRACE:1][665][OPMN][code:pm-process]Process Alive: coreapplication_obis1~OracleBIServerComponent~coreapplication_obis1~1 (1181693061:8643)
[2012-08-23T16:04:01][opmn][TRACE:1][668][OPMN][code:pm-requests]Request 1fa Completed. Command: /start?ias-component=coreapplication_obis1
[2012-08-23T16:04:01][opmn][TRACE:1][667][OPMN][code:pm-requests]Request 1fb Started. Command: /start?ias-component=coreapplication_obisch1
[2012-08-23T16:04:01][opmn][TRACE:1][662][OPMN][code:pm-process]Starting Process: coreapplication_obisch1~OracleBISchedulerComponent~coreapplication_obisch1~1 (1181693062:0)
[2012-08-23T16:04:03][opmn][TRACE:1][665][OPMN][code:pm-process]Process Alive: coreapplication_obisch1~OracleBISchedulerComponent~coreapplication_obisch1~1 (1181693062:8995)
[2012-08-23T16:04:03][opmn][TRACE:1][668][OPMN][code:pm-requests]Request 1fb Completed. Command: /start?ias-component=coreapplication_obisch1
[2012-08-23T16:04:03][opmn][TRACE:1][667][OPMN][code:pm-requests]Request 1fc Started. Command: /start?ias-component=coreapplication_obips1
[2012-08-23T16:04:03][opmn][TRACE:1][662][OPMN][code:pm-process]Starting Process: coreapplication_obips1~OracleBIPresentationServicesComponent~coreapplication_obips1~1 (1181693063:0)
[2012-08-23T16:04:05][opmn][TRACE:1][][OPMN][code:libopmncustom]Process Ping Failed: coreapplication_obips1~OracleBIPresentationServicesComponent~coreapplication_obips1~1 (1181693063:9021) [No addresses matched the properties for the request.]
[2012-08-23T16:04:05][opmn][TRACE:1][][OPMN][code:libopmncustom]Process Ping Failed: coreapplication_obips1~OracleBIPresentationServicesComponent~coreapplication_obips1~1 (1181693063:9021)
[2012-08-23T16:04:05][opmn][TRACE:1][][OPMN][code:libopmncustom]Ping failed in Ready callback for proc:1181693063
[2012-08-23T16:04:07][opmn][TRACE:1][][OPMN][code:libopmncustom]Process Ping Failed: coreapplication_obips1~OracleBIPresentationServicesComponent~coreapplication_obips1~1 (1181693063:9021) [No addresses matched the properties for the request.]
[2012-08-23T16:04:07][opmn][TRACE:1][][OPMN][code:libopmncustom]Process Ping Failed: coreapplication_obips1~OracleBIPresentationServicesComponent~coreapplication_obips1~1 (1181693063:9021)
[2012-08-23T16:04:07][opmn][TRACE:1][][OPMN][code:libopmncustom]Ping failed in Ready callback for proc:1181693063
[2012-08-23T16:04:09][opmn][TRACE:1][662][OPMN][code:pm-process]Starting Process: coreapplication_obips1~OracleBIPresentationServicesComponent~coreapplication_obips1~1 (1181693063:0)
[2012-08-23T16:04:11][opmn][TRACE:1][][OPMN][code:libopmncustom]Process Ping Failed: coreapplication_obips1~OracleBIPresentationServicesComponent~coreapplication_obips1~1 (1181693063:9043) [No addresses matched the properties for the request.]
[2012-08-23T16:04:11][opmn][TRACE:1][][OPMN][code:libopmncustom]Process Ping Failed: coreapplication_obips1~OracleBIPresentationServicesComponent~coreapplication_obips1~1 (1181693063:9043)
[2012-08-23T16:04:11][opmn][TRACE:1][][OPMN][code:libopmncustom]Ping failed in Ready callback for proc:1181693063
[2012-08-23T16:04:13][opmn][TRACE:1][668][OPMN][code:pm-requests]Request 1fc Completed. Command: /start?ias-component=coreapplication_obips1
[2012-08-23T16:04:13][opmn][TRACE:1][][OPMN][code:libopmncustom]Process Ping Failed: coreapplication_obips1~OracleBIPresentationServicesComponent~coreapplication_obips1~1 (1181693063:9043) [No addresses matched the properties for the request.]
[2012-08-23T16:04:13][opmn][TRACE:1][][OPMN][code:libopmncustom]Process Ping Failed: coreapplication_obips1~OracleBIPresentationServicesComponent~coreapplication_obips1~1 (1181693063:9043)
[2012-08-23T16:04:13][opmn][TRACE:1][][OPMN][code:libopmncustom]Ping failed in Ready callback for proc:1181693063
[2012-08-23T16:04:14][opmn][TRACE:1][667][OPMN][code:pm-requests]Request 1fd Started. Command: /start?ias-component=coreapplication_obijh1
[2012-08-23T16:04:14][opmn][TRACE:1][662][OPMN][code:pm-process]Starting Process: coreapplication_obijh1~OracleBIJavaHostComponent~coreapplication_obijh1~1 (1181693064:0)
[2012-08-23T16:04:16][opmn][TRACE:1][665][OPMN][code:pm-process]Process Alive: coreapplication_obijh1~OracleBIJavaHostComponent~coreapplication_obijh1~1 (1181693064:9053)
[2012-08-23T16:04:16][opmn][TRACE:1][668][OPMN][code:pm-requests]Request 1fd Completed. Command: /start?ias-component=coreapplication_obijh1
[2012-08-23T16:04:16][opmn][TRACE:1][667][OPMN][code:pm-requests]Request 1fe Started. Command: /start?ias-component=coreapplication_obiccs1
[2012-08-23T16:04:16][opmn][TRACE:1][662][OPMN][code:pm-process]Starting Process: coreapplication_obiccs1~OracleBIClusterControllerComponent~BIClusterController~1 (1181693065:0)
[2012-08-23T16:04:18][opmn][TRACE:1][665][OPMN][code:pm-process]Process Alive: coreapplication_obiccs1~OracleBIClusterControllerComponent~BIClusterController~1 (1181693065:9079)
[2012-08-23T16:04:18][opmn][TRACE:1][668][OPMN][code:pm-requests]Request 1fe Completed. Command: /start?ias-component=coreapplication_obiccs1
[2012-08-23T16:04:53][opmn][TRACE:1][667][OPMN][code:pm-requests]Request 236 Started. Command: /start?ias-component=coreapplication_obips1
[2012-08-23T16:04:53][opmn][TRACE:1][662][OPMN][code:pm-process]Starting Process: coreapplication_obips1~OracleBIPresentationServicesComponent~coreapplication_obips1~1 (1181693066:0)
[2012-08-23T16:04:54][opmn][TRACE:1][][OPMN][code:libopmncustom]Process Ping Failed: coreapplication_obips1~OracleBIPresentationServicesComponent~coreapplication_obips1~1 (1181693066:9537) [No addresses matched the properties for the request.]
[2012-08-23T16:04:54][opmn][TRACE:1][][OPMN][code:libopmncustom]Process Ping Failed: coreapplication_obips1~OracleBIPresentationServicesComponent~coreapplication_obips1~1 (1181693066:9537)
[2012-08-23T16:04:54][opmn][TRACE:1][][OPMN][code:libopmncustom]Ping failed in Ready callback for proc:1181693066
[2012-08-23T16:04:56][opmn][TRACE:1][665][OPMN][code:pm-process]Process Alive: coreapplication_obips1~OracleBIPresentationServicesComponent~coreapplication_obips1~1 (1181693066:9537)
[2012-08-23T16:04:56][opmn][TRACE:1][668][OPMN][code:pm-requests]Request 236 Completed. Command: /start?ias-component=coreapplication_obips1

Sql 2012 server for SCCM 2012 - Agent not starting

Hi ,
In our environment we have a Sql 2012, and it was working fine till now. but after installation of RDP role and subsequent installation of certificates for remote desktop in the SCCM server ( SQL 2012 is
installed in it)
we are facing the issue - Sql server management studio not connecting ( windows authenticaltion)
1) A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)A
2) I tried starting the sql agent service in services.msc and the below error came
The SQL Server Agent (MSSQLSERVER) service on Local Computer started and then stopped.
Some services stop automatically if they are not in use by other services or programs.
3) In the Sql Server configuration manager also tried starting the sql agent but
The request failed or the service did not respond in a timely fashion.
Consult the event log or other applicable error logs for details.
The widows event logs show this error
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection.
The TLS protocol defined fatal error code is 20. The Windows SChannel error state is 960.
We have removed the certificate and the RDP role in that .
Can anyone please help on this
Anand M

I would check for error messages in the SQL Server ERROLOG file and also Agent's SQLAGENT.OUT file.
Tibor Karaszi, SQL Server MVP |
web | blog

SQL Server service not automatically starting (logon failure)

I just installed SQL Server 2012 on a machine. To run "SQL Server" as well as "SQL Server Agent" service I have created a domain account called SQLADMIN. This account is a service account and has no other rights like logon locally or
local administrator.
When the machine restarts, "SQL Server" service doesn't start automatically. When I click Start then it says "Logon Failure". Now if I simply enter the password again under tab "Log On" and then start service then it starts. Why
doesn't it start automatically?

Hello,
Please read the following article about permissions required by service accounts.
http://msdn.microsoft.com/en-us/library/ms143504(v=sql.110).aspx#Serv_Perm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
I do not see any special permission that is needed as per the article. For e.g. as per below:
SQL Server Service
Permissions granted by SQL Server Setup
SQL Server Database Engine:
(All rights are granted to the per-service SID. Default instance: NT SERVICE\MSSQLSERVER. Named instance: NT SERVICE\MSSQL$InstanceName.)
Log on as a service (SeServiceLogonRight)
Replace a process-level token(SeAssignPrimaryTokenPrivilege)
Bypass traverse checking (SeChangeNotifyPrivilege)
Adjust memory quotas for a process(SeIncreaseQuotaPrivilege)
Permission to start SQL Writer
Permission to read the Event Log service
Permission to read the Remote Procedure Call service
I am running Database Engine service as DOMAIN\SQLADMIN account which can Log On As A Service. Other 3 permissions mentioned in article are not given so let me assign it and then see how it goes.
Could this issue be due to some domain policy? Because there is another SQL Server machine which shows same behaviour.

Sql Server Agent not starting automatically in failover in a clustered environment.

Similar Messages

Maybe you are looking for