Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server Agent Fails while the server is backdated Expand / Collapse
Author
Message
Posted Thursday, November 26, 2009 5:24 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, July 2, 2014 5:32 AM
Points: 19, Visits: 118
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!!!
Post #825388
Posted Thursday, November 26, 2009 6:10 PM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 12:52 PM
Points: 1,805, Visits: 5,869
Is your application using SQL Authentication while SQL Agent is using Windows Authentication?



MM


  • MMGrid Addin
  • MMNose Addin


  • Forum Etiquette: How to post Reporting Services problems
  • Forum Etiquette: How to post data/code on a forum to get the best help - by Jeff Moden
  • How to Post Performance Problems - by Gail Shaw

  • Post #825394
    Posted Thursday, November 26, 2009 8:43 PM
    Hall of Fame

    Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

    Group: General Forum Members
    Last Login: Yesterday @ 7:21 PM
    Points: 3,064, Visits: 2,675
    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



    Post #825411
    Posted Friday, November 27, 2009 6:39 AM
    Grasshopper

    GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

    Group: General Forum Members
    Last Login: Wednesday, July 2, 2014 5:32 AM
    Points: 19, Visits: 118
    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?
    Post #825595
    « Prev Topic | Next Topic »

    Add to briefcase

    Permissions Expand / Collapse