MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Odd Workflow / Task endless loop problem

  Asked By: Larissa    Date: Mar 16    Category: MOSS    Views: 19118

We're testing out Sharepoint 2007 to evaluate our transition from our
current calendar system to that when you get it running and I'm having
a strange problem. It's running in standalone mode, with an express
mssql database running on it. I have workflow enabled on a list which
is set to start when an event is created and when it is modified. The
workflow is the standard built-in workflow, and versioning is set to
control content. Additionally the workflow is set to update the item
when the workflow is approved (control content as well). The problem is
that when a workflow task is approved for a new event it completes that
task and then creates a new one, now assigned by the System Account
(SHAREPOINT\system) , not the originating member who posted the event.
I believe it's because the task has been "altered" through the attempt
to approve it but it just gets stuck in a loop if you just try to
approve the workflow task. Anyone have any ideas? I've searched

Does anyone have any idea where to start on this? I've poured over
every log file I can find but haven't found anything useful.



5 Answers Found

Answer #1    Answered By: Kerri Steele     Answered On: Mar 16

Are you using different correlation tokens for each task?

Answer #2    Answered By: Alisha Itagi     Answered On: Mar 16

My initial thought is that you're trying to use the same account to test
this functionality that you used to install and secure the Central Admin
app pool. Is this the case?

Answer #3    Answered By: Octavio Dotson     Answered On: Mar 16

That's probably the case. Currently the identity in of the Central
Administration pool is set to Network Service. From what I've read
after seeing your comment that's probably not correct. I see it's
supposed to be a domain account, but I can't seem to find any
specifics. Does anyone have some guidance on what it should be?
Also, are there any other places where the default service account
should be changed?

Answer #4    Answered By: Judy Pittman     Answered On: Mar 16

Make sure the app pool account is not the same account as the one that
was used to install SharePoint. Ensure this account has db_security and
db_creator permissions in SQL and is a member of the local admin group
on the WFE server.

And then ensure that you're logging in with a different account that is
a member of the farm administrator's group.

Answer #5    Answered By: Tricia Mullins     Answered On: Mar 16

Ok, I re-built our installation from scratch, with the below
suggestions. The Central Admin pool is unique, has db_sec and
db_creator permissions set in the db and is a local admin on the wfe.
The SharedServices app pool identity and the main site app pool
(sharepoint - 80), however, are sharing the same identity (I don't
know if that's a problem).

Anyway, the problem  is the same as before: Approving a task  in a
workflow where task approval controls content approval results in a
new, identical, task being created by the sharepoint  "system" account.

Someone mentioned something about using unique tokens but I'm not sure
where that even applies. I'm not designing a workflow  just using the
built-in approval.

Didn't find what you were looking for? Find more on Odd Workflow / Task endless loop problem Or get search suggestion and latest updates.