<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 7,2000
»
SQL Server Agent
»
SQL Server Agent Fails while the server is...
SQL Server Agent Fails while the server is backdated
Rate Topic
Display Mode
Topic Options
Author
Message
saravanaraj.dhamodarran
saravanaraj.dhamodarran
Posted Thursday, November 26, 2009 5:24 PM
Grasshopper
Group: General Forum Members
Last Login: Monday, December 03, 2012 5:54 AM
Points: 19,
Visits: 117
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
mister.magoo
mister.magoo
Posted Thursday, November 26, 2009 6:10 PM
Ten Centuries
Group: General Forum Members
Last Login: Yesterday @ 5:50 PM
Points: 1,308,
Visits: 3,899
Is your application using SQL Authentication while SQL Agent is using Windows Authentication?
MM
Post #825394
happycat59
happycat59
Posted Thursday, November 26, 2009 8:43 PM
SSCrazy
Group: General Forum Members
Last Login: Wednesday, May 22, 2013 9:55 PM
Points: 2,471,
Visits: 2,066
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
saravanaraj.dhamodarran
saravanaraj.dhamodarran
Posted Friday, November 27, 2009 6:39 AM
Grasshopper
Group: General Forum Members
Last Login: Monday, December 03, 2012 5:54 AM
Points: 19,
Visits: 117
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 »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
