Skip to main content
Merged multiple answers; added 31 characters in body
Source Link
Alex Angas
  • 6k
  • 9
  • 50
  • 89

Checked the timerlock table on the content database and it was running on the Inactive SharePoint Server. so, Stopped the Timer service temporarily on that server which moved the timerlock to the active Server.

Issue is fixed now...!Steps to resolve the issue:

  • Make sure you have SharePoint already configured for outgoing emails.
  • Make sure that you have alerts for the document library turned on if you are testing with the document library.
  • Run this command from C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN: stsadm -o updatealerttemplates -filename "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\XML\customalerttemplates.xml" -url
  • Run this command: stsadm -o setproperty -pn job-immediate-alerts -pv "every 1 minutes"
  • Run this command from the command prompt: iisreset
  • Run this command from the command prompt: services.msc
  • From the services window, restart the Windows SharePoint Services Timer.

Checked the timerlock table on the content database and it was running on the Inactive SharePoint Server. so, Stopped the Timer service temporarily on that server which moved the timerlock to the active Server.

Issue is fixed now...!

Checked the timerlock table on the content database and it was running on the Inactive SharePoint Server. so, Stopped the Timer service temporarily on that server which moved the timerlock to the active Server.

Steps to resolve the issue:

  • Make sure you have SharePoint already configured for outgoing emails.
  • Make sure that you have alerts for the document library turned on if you are testing with the document library.
  • Run this command from C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN: stsadm -o updatealerttemplates -filename "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\XML\customalerttemplates.xml" -url
  • Run this command: stsadm -o setproperty -pn job-immediate-alerts -pv "every 1 minutes"
  • Run this command from the command prompt: iisreset
  • Run this command from the command prompt: services.msc
  • From the services window, restart the Windows SharePoint Services Timer.
Source Link
Karthikeyan
  • 2.5k
  • 14
  • 83
  • 142

Checked the timerlock table on the content database and it was running on the Inactive SharePoint Server. so, Stopped the Timer service temporarily on that server which moved the timerlock to the active Server.

Issue is fixed now...!