November 26, 2009 at 5:24 pm
Hi,
We have a situation where, the app server and the database server has to be backdated and not the domain controller. While backdated, the application is able to read, write and update to the database. The job works in the current dated mode. But, while the application tries to trigger a job, the SQL Server Agent logs the below message:
-------------------------------------------------------------------------------------------------
2008-11-27 15:42:57 - ! [298] SQLServer Error: 804, SQL Network Interfaces: The clocks on the client and server machines are skewed. [SQLSTATE HY000]
2008-11-27 15:42:57 - ! [298] SQLServer Error: 804, Cannot generate SSPI context [SQLSTATE HY000]
2008-11-27 15:42:57 - ! [382] Logon to server '(local)' failed (JobManager)
2008-11-27 15:42:57 - ! [298] SQLServer Error: 804, SQL Network Interfaces: The clocks on the client and server machines are skewed. [SQLSTATE HY000]
2008-11-27 15:42:57 - ! [298] SQLServer Error: 804, Cannot generate SSPI context [SQLSTATE HY000]
2008-11-27 15:42:57 - ! [382] Logon to server '(local)' failed (ConnUpdateJobActivity_NextScheduledRunDate)
2008-11-27 15:42:57 - ! [298] SQLServer Error: 804, SQL Network Interfaces: The clocks on the client and server machines are skewed. [SQLSTATE HY000]
2008-11-27 15:42:57 - ! [298] SQLServer Error: 804, Cannot generate SSPI context [SQLSTATE HY000]
2008-11-27 15:42:57 - ! [382] Logon to server '(local)' failed (ConnAttemptCachableOp)
2008-11-27 15:42:57 - ! [298] SQLServer Error: 804, SQL Network Interfaces: The clocks on the client and server machines are skewed. [SQLSTATE HY000]
2008-11-27 15:42:57 - ! [298] SQLServer Error: 804, Cannot generate SSPI context [SQLSTATE HY000]
2008-11-27 15:42:57 - ! [382] Logon to server '(local)' failed (ConnAttemptCachableOp)
-------------------------------------------------------------------------------------------------
SQL Server Version: Microsoft SQL Server 2005 - 9.00.3042.00 (Intel IA-64) Feb 10 2007 01:00:35 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
The SQL Server is clustered.
SQL Server Agent runs on: <<Domain>>\<<MachineName>>_agent
The Job owner has R/W/M access on the database.
Thanks in advance!!!
November 26, 2009 at 6:10 pm
Is your application using SQL Authentication while SQL Agent is using Windows Authentication?
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);November 26, 2009 at 8:43 pm
When you (or SQL Agent) authenticates to Active Directory (when you logon or start a service), a "ticket" is issued that represents you. This ticket is valid for a fixed amount of time.
If your clocks are out of step (which yours are), this effectively means that the ticket that would have been issues is immediately out of date
November 27, 2009 at 6:39 am
Yes, my applicaiton uses SQL Server authentcation. If the difference betweenthe server and the client are different, and the ticket expires, what other options can I have to make it work? Also, can
we make the SQL Server agent work under a local machine account, so that it may not have to authenticate with the domain controller?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply