Timeline for SQL Server transaction replication agent error
Current License: CC BY-SA 3.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 14, 2019 at 13:36 | comment | added | mlhDev | @PMSawyer thanks for the note about server clock being incorrect. I'm investigating negative job durations and after reading your comment found the server clock appears wonky with sequential EventRecordID values following out of order time entries in the event viewer. | |
| Aug 15, 2017 at 7:33 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 12, 2017 at 0:23 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 10, 2017 at 10:57 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| May 11, 2017 at 8:40 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 10, 2017 at 18:28 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 26, 2017 at 10:38 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 25, 2017 at 18:24 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 21, 2016 at 12:05 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 21, 2016 at 22:22 | history | tweeted | twitter.com/StackDBAs/status/800826737466736641 | ||
| Nov 21, 2016 at 9:35 | answer | added | Santa | timeline score: 1 | |
| Nov 19, 2016 at 10:21 | comment | added | Santa | @PMSawyer, it would be extremely useful if you could add your comment as an answer (with more details if possible). I do of course realize it's been more than a year since this question was active. | |
| Feb 17, 2015 at 21:16 | comment | added | PMSawyer | The problem has been solved. It was caused by some bad job duration values, negative, in the job history table. Deleting the bad data from the table solved the problem. Speculation how it happened points to the server clock being incorrect then corrected causing the bad values. | |
| Jan 7, 2015 at 13:36 | comment | added | PMSawyer | We did that and are reviewing the output. Thanks | |
| Jan 6, 2015 at 16:23 | comment | added | RLF |
For more detailed information, make sure to set your -OutputVerboseLevel 2 as recommended at http://support.microsoft.com/kb/312292/en-us. This will provide you more detailed information on the problem
|
|
| S Jan 6, 2015 at 15:21 | history | suggested | LowlyDBA - John M | CC BY-SA 3.0 |
Formatting, tagging
|
| Jan 6, 2015 at 15:09 | review | Suggested edits | |||
| S Jan 6, 2015 at 15:21 | |||||
| Jan 6, 2015 at 14:54 | review | First posts | |||
| Jan 6, 2015 at 15:09 | |||||
| Jan 6, 2015 at 14:52 | history | asked | PMSawyer | CC BY-SA 3.0 |