none
After installing SP3 - Suspended content DB on start of workflows RRS feed

  • Question

  • Dear,

    In advance many thanks for any help given!

    Our problem is that last Saturday we've upgraded our MOSS 2007 Standard environment from SP1 directly to SP3 (first installed WSS 3.0 SP3, than installed MOSS 2007 SP3 and ran the Configuration Wizard). Before the upgrade everything worked great and the installation of SP3 on our testing environment (which is almost equal to our production) didn't gave any problems.

    After the upgrade every time someone starts a workflow, SharePoint gets really slow. At this point we've found that the content DB is changing to status suspended when a workflow is started. The DB gets this status when the stored procedure Portal_Content.dbo.proc_AddWorkflow;1 is started. I can't find anything strange in the SharePoint or server logs.

    We're a bit stuck at the moment and can't find anything on the internet about it. Did anyone experienced or heard about this before?

    The environment exists out of one front-end/application server and one SQL server (which also hosts the SharePoint Search service). The front-end is a Server 2008 Service Pack 2 server and the SQL is running on Server 2003 R2 Service Pack 2 (Both are still 32-bit. I know, it's bad! But we're in the process of upgrading the platform to 64-bit very soon).

    Monday, March 26, 2012 9:14 AM

Answers

  •  

    Hi quincyt,

    I think you can restart your SQL services after installing SP3.

    1. Click start ->Run, Input  “services.msc”
    2. Find the following services and restart them.

    SQL Server (MSSQLSERVER)

    SQL Server (SQLEXPRESS)

    SQL Server Analysis Services (MSSQLSERVER)

    SQL Server Integration Services 10.0

    Thanks,

    Jack


    Thursday, March 29, 2012 2:31 AM
    Moderator

All replies

  •  

    Hi quincyt,

    I think you can restart your SQL services after installing SP3.

    1. Click start ->Run, Input  “services.msc”
    2. Find the following services and restart them.

    SQL Server (MSSQLSERVER)

    SQL Server (SQLEXPRESS)

    SQL Server Analysis Services (MSSQLSERVER)

    SQL Server Integration Services 10.0

    Thanks,

    Jack


    Thursday, March 29, 2012 2:31 AM
    Moderator
  • Hi Jack,

    Sorry it took me some time to reply, but I was to busy with MANY other things.

    Apparently installing SP3 and restarting the server (only the front-end) deleted some sort of cache or so. Because after a week or two the SharePoint did run as it always did and the problems were gone.

    Thanks for your help and solution though! Maybe some other people will get the help they need out of it.

    All the best,
    Quincy
    • Edited by Quincy Thomas Thursday, August 23, 2012 1:51 PM wrote cash instead of cache (seriously, not kidding you!)
    Thursday, August 23, 2012 8:42 AM