Many time during the business hours we receive this type of issue. following steps may help to resolve this issue.
Scenario : Email accounts are setup , alerts was working earlier , suddenly users stop receiving alerts.
This could be caused by Timer service locked the content database and alerts are getting stuck in queue.
Use query to check by which server timer service is locked (Off course if you have multiple server farm environment)
#1
use [Your Content database]
select * from timerlock (nolock)
You can also check what event cache table is holding currently
#2
SELECT * FROM eventcache WITH (nolock) WHERE EventData is not null
If you see large no of items in queue you may go ahead and restart the timer service on the server. (First query will give you server name)
Actual alerts sending can take 20 min of time and can be verified running second query again . If everything goes well you should see no record pending in second query output.
Scenario : Email accounts are setup , alerts was working earlier , suddenly users stop receiving alerts.
This could be caused by Timer service locked the content database and alerts are getting stuck in queue.
Use query to check by which server timer service is locked (Off course if you have multiple server farm environment)
#1
use [Your Content database]
select * from timerlock (nolock)
You can also check what event cache table is holding currently
#2
SELECT * FROM eventcache WITH (nolock) WHERE EventData is not null
If you see large no of items in queue you may go ahead and restart the timer service on the server. (First query will give you server name)
Actual alerts sending can take 20 min of time and can be verified running second query again . If everything goes well you should see no record pending in second query output.
No comments:
Post a Comment