Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

WSS 3.0 Alerts - Time job status not even trying to send jobs.

WSS 3.0 Alerts - Time job status not even trying to send jobs.

WSS 3.0 Alerts - Time job status not even trying to send jobs.

Hello all. It has been a very looong time since I've had any WSS 3.0 issues and I hope there are some out there still using WSS 3.0 that can offer some assistance.

The issue in general is a common issue... alerts are not sending.
This began roughly after we had to move our content database because it was on the default MSEE SQL instance and also on the same web app server.
Users didnt report an issue until 2 weeks or so after the migration so it's hard to tell if that caused this issue.
MS Security updates etc have also been run during the period of alerts stopping.

SharePoint performance became very poor and we needed a quick solution.
The migration was done by detaching from the MSEE instance and copying the file to the new server, attaching it there, then pointing the SharePoint admin settings to the new content DB. The content DB works fine as does the front end web application.

I've gone through many forums running many recommended sts commands that have not been successful such as enabling and disabling alerts, making sure immediate alerts are every 5 minutes and 0 to 59 seconds etc.

The timer service is running. It is using the same domain account as the other sharepoint services are using.
The SharePoint search service crawls the content db on the new sql server without issue. My point is it doesn't seem to be a DB server permission issue.
Email notification settings have not changed. When i create new alerts I'm informed of the new alert creation. So email is configured properly.

Attached is a screenshot showing my timer job status page. You will see most jobs last succeeded on 11/2 or 11/3 (about the db migration I believe but as said not sure exactly).

Another curious thing I noticed when troubleshooting the alert issue...
SP Central Admin > Operations > Services on Server...
Windows SharePoint Services Web Application is listed as STOPPED however the web front end appears to function normally (other than alerts).
If I try to start it I get this error:

"Failed to apply a web.config modification to the file '/configuration/system.web/pages'. The specified node "C:\inetpub\wwwroot\wss\VirtualDirectories\80\web.config" was not found in the web.config file."

I suspect this may be related to the alert issue.

I've searched\googled for this as well and haven't been able to make headway on it. Any clues to the alert issue and service issue on this legacy system would greatly be appreciated

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close