Workflow module not functioning after upgrade to 4.50

Vote:
 
A customer has reported a problem with the workflow module after having updated from 4.41 to 4.50: editors cannot access their tasks anymore (they receive an "Object reference not set to an instance of an object" error) and administrators cannot access the individual workflows neither. Is this a known issue for 4.50? To mention as well is that the data related to the existing workflows are still in the database, but are not querable/removable through EPiServer. /Magnus
#17428
Mar 25, 2008 19:33
Vote:
 
This may be the same problem as described in http://www.episerver.com/devforum/showtopic.aspx?id=5119 If the Exception occur in the UserName webcontrol it probably is.
#18188
Mar 25, 2008 19:43
Vote:
 
Thanks Per for checking up this issue; it is very likely that workflow problems stem from the UserName webcontrol. Since the workflow is an important feature of our customer's EPiServer installation, would it be possible to receive a hotfix for this bug prior to the release of v. 4.51? Regards, Magnus
#18189
Mar 25, 2008 19:43
Vote:
 
Hello Magnus! Forry for the delayed response but we are now in the final stages for the release of EPiServer 4.51 so I hope you can wait a couple of more days for this.
#18190
Mar 25, 2008 19:43