16 thoughts on “Crashing OWSTIMER.EXE after SharePoint 2010 SP1 Installation”

  1. Thanks for the link, Todd! I hadn’t played around with any of the service startup parameters (such as delaying the start of the FIM services), but they sound like a great next step. If I find some free time, I may go back and play with the (now) old snapshot to see if those changes do the trick.

  2. Good article Sean. And thank you for the reference Todd. We had the issues of FIM not working at all. And we also had a few errors with regard to Office Web Apps. Did you guys experience anything with regard to office web apps?

  3. Thanks Tony. I haven’t really run into any problems with SP1 following its installation/configuration, but I haven’t had a whole lot of time to play around. I’ll keep my eyes open, though — particularly with the OWAs. If I see anything there, I’ll let you know!

  4. I appreciate the feedback, Bill. I haven’t played with the June CU, but I have a natural aversion to the 2010 CUs primarily due to the lack of extensive regression testing. If I can find the time, I might try playing with the CU on the snapshot I took prior to SP1 install. I’ve gone back once or twice to try some additional tricks since writing this post, but I have yet to find an approach that doesn’t (a) leave me with the timer job issues, or (b) result in an unusable user profile service.

    Thanks again!

  5. Hi I’m having exactly the same problem.

    Prior to installing SP1 – everything was pretty much good. But soon after, I noticed that I was getting debug error messages from Visual Studio complaining about the Timer Services. Also whenever I deployed a Custom Solution Webpart, I had to manually go in to each server in the farm and run the “STSADM -o execadmsvcjobs” command to force the job to run and successfully install the solution.

    unfortunately I didn’t to do a VM snapshot and therefore am rather stuck with SP1. Can anyone out there help?

    Thanks

    Davinder.

  6. Davinder: I’m sorry, but I don’t have any particular suggestions for you. I’m hoping that perhaps someone else will chime in. Best of luck!

  7. This post was very helpful. We were having the same issues after SP1 installation on the DEV farm. The VS 2010 debugger errors were popping up and the farm upgrade was not completing. Noticed the Domain connection was not showing under UPS and UPS was stopped. Stated the UPS under Services on server and the VS 2010 debugger error stopped After I started the UPS service – the FIM also went from Disabled to Automatic Started.
    Ran PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures >> C:\temp\sp1_status3.txt
    The upgrade completed successfully and All Issues were resolved.
    I HATE the User Profile Service application – it is very high maintenance!!!!!

  8. Thanks Sean,

    Actually, I was thinking about the UPS, if it is the main causing of the issue? because TIMER Service is crashing for each time when the synchronize job is started!!
    But after I read your post and follow the steps,the issue resolved :)

    Thanks again for the good troubleshooting and explaining,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s