Search
Closed
as Not Reproducible Help for as Not Reproducible

0
Sign in to vote
0
Sign in to vote
Sign in
 to vote
Type: Bug
ID: 484202
Opened: 8/20/2009 10:43:02 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
Hi, I am having exactly the same problem as described in this issue:
https://connect.microsoft.com/wf/feedback/ViewFeedback.aspx?FeedbackID=433518

Could you please let me know how it was resovled by microsoft in the end? It is very urgent and our project cannot go live with this bug happening randomly.

Thanks
Details (expand)

Product Version

.NET Framework 3.5 SP1
Product Language
English

Operating System
Windows Server 2008 RTM/SP1/SP2
Operating System Language
English

Architecture
x64

Priority
(1=blocking, 2=important, 3=nice to have)
1

Severity
(1=major functionality issue, 2=important functionality issue, 3=nice to have)
1

Steps to Reproduce
This happens randomly. Similar to issue https://connect.microsoft.com/wf/feedback/ViewFeedback.aspx?FeedbackID=433518
Actual Results
again similar to issue in
https://connect.microsoft.com/wf/feedback/ViewFeedback.aspx?FeedbackID=433518
Expected Results
again similar to issue in
https://connect.microsoft.com/wf/feedback/ViewFeedback.aspx?FeedbackID=433518
Component Usage
(any information on your scenario that may help in investigating your issue)
 

How often does this happen?
Always Happens

Have you seen this problem in other versions?
I don't know if this issue existed previously

File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 8/31/2009 at 4:30 PM
Hello Alvinsue,

Thank you for summiting this bug! I believe that for your case, removing the OnTaskCreated Activity will fix your problem. 95% of the time, there is a workaround to achieve your scenario without using OnTaskCreated. For example, if you need to set permissions on the item, there is a SpecialPermissions property on the CreateTask activity that will do that, or if you need to generate a URL, you can generate one based on information that is available through existing objects. You can also create an activity that uses a PersistOnClose attribute to force the commit and continue.

To be able to investigate this bug we would need a solid repro. I'm going to go ahead and resolve this bug as no-repro. Please fell free to reactivate this bug with more information.

Thank you

Sergio
PM, WF Runtime.

© 2009 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement