Microsoft Knowledge Base Email Alertz

KBAlertz.com: A declarative workflow does not start automatically after you install Windows SharePoint Services 3.0 Service Pack 1

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **


Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.


Community Site



We Send hundreds of thousands of emails using ASP.NET Email



Expert Web Design & Graphic Design
Design44.com

ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 947284 - Last Review: February 1, 2008 - Revision: 1.1

A declarative workflow does not start automatically after you install Windows SharePoint Services 3.0 Service Pack 1

SYMPTOMS

After you install Windows SharePoint Services 3.0 Service Pack 1 (SP1), a declarative workflow does not start automatically in the following products:
  • Windows SharePoint Services 3.0
  • Microsoft Office SharePoint Server 2007
  • Microsoft Office SharePoint Designer 2007
For example, if you configure a declarative workflow to start when a new item is created or when a new item is changed, the declarative workflow does not start as expected. The Unified Logging Service (ULS) log files contain no information about why this behavior occurs.

CAUSE

This behavior occurs because a security fix in Windows SharePoint Services 3.0 SP1 prevents declarative workflows from starting automatically under the system account. After you install Windows SharePoint Services 3.0 SP1, declarative workflows do not start automatically if the following conditions are true:
  • The Windows SharePoint Services Web application runs under a user's domain account.
  • The user logs in by using this domain account.
  • The site displays the user name as System Account.

RESOLUTION

To resolve this behavior, set the application pool account to use a different user account. You may want to create a new user account specifically for this purpose.

To set the application pool account to use a different user account, follow these steps:
  1. On the server that is running one of the products that is listed in the "Applies to" section, click Start, point to All Programs, point to Microsoft Office Server, and then click SharePoint 3.0 Central Administration.
  2. Click the Operations tab.
  3. Under Security Configuration, click Service Accounts.
  4. Click Web application pool, and then click Windows SharePoint Services Web Application in the Web service box.
  5. In the Application pool box, click the application pool that you want to change.
  6. Under Select an account for this component, click Configurable, and then type the user name and the password for the different user account.

STATUS

This behavior is by design.

APPLIES TO
  • Microsoft Windows SharePoint Services 3.0
  • Microsoft Office SharePoint Designer 2007
  • Microsoft Office SharePoint Server 2007
Keywords: 
kbtshoot kbexpertiseadvanced kbnofix kbprb KB947284
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

KrishnaPrasad Hande Report As Irrelevant  
Written: 3/29/2008 3:01 AM
Thanks a lot. you resolved my nightmares.

Mike Report As Irrelevant  
Written: 5/2/2008 12:53 PM
Thanks, I was looking for this issue and this helps. Question: What permissions do the account that you replace the Application pool need? Does this cause issues with MOSS if you now change this account?

PVVK Report As Irrelevant  
Written: 6/30/2008 5:07 AM
Great info ,thanks a lot

E Report As Irrelevant  
Written: 7/24/2008 1:21 PM
Even after changing my application pool account and SP services to run as a different user, my original account still shows uploads as "System Account" and workflows won't automatically start. does anyone know what needs to be changed to stop showing the original account as "System Account". thx

Anff Report As Irrelevant  
Written: 7/31/2008 4:21 AM
It appears that this KB implies that if you are running a workflow dll and that workflow updates an item, any declarative (ie. SPD) workflows set to run on update, simply won't.

Laander - http://laander.com Report As Irrelevant  
Written: 10/28/2008 2:52 AM
Hi everyone, although this fix might work in some cases, we've found that applying the following hotfix resolved all issues related to incoming e-mails and automatic start of workflows: http://support.microsoft.com/default.aspx/kb/956057

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please