Monthly Archives: April 2013

Solution: The workflow contains errors, but they are not visible in the current view

Posted on by
15

Hi,

Sometimes when you work on workflows in SharePoint Designer you can not publish it, because the Check for Errors fails with the following mesage: “The workflow contains errors, but they are not visible in the current view”

130420_02

Usually in this case you really can’t see the place where the error is and it seems like everything is OK.

I spent some time to understand where the error is when I saw this error the first time. Most likely it is an issue in SPD; however, it is rather simple to overcome it and force SPD to show the place the error is.

The solution: you just have to save your workflow (by pressing Save button in the ribbon), close it and open it again (by selecting it in the Navigation\Workflows and pressing the “Edit workflow” link).

After that you should be able to see what fields are set incorrectly:

130420_03

You can press Check for Errors button to highlight all the errors with the red color:

130420_04

I stumbled into this moment several times after copying-pasting my workflow. It seems like this new feature works well in the most parts of the workflow, except the Transition to stage part. At least, in my cases after pasting I had to repair fields in the Transition to stage part only.

Regards, Michael.

-13

Solution: Workflow cancels (System.ArgumentException: ContentTypeId)

Posted on by
2

Hi,

Yesterday I copied and pasted one of my 2013 SPD workflows to a new one. All passed well, but my workflow failed on the start with the following error:

130419_05

RequestorId: 1a9862c8-3314-4e2a-a3e8-85d79f2cd7c9. Details: System.ArgumentException: ContentTypeId 
at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) 
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) 
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)

The words about ContentTypeId helped me to identify the cause of the issue quickly. In my new workflow task list defered from the one in the old. Hence, it didn’t have my custom task content types and WF failed when tried to create a task.

So, the solution is pretty simple: Make sure whether your task list contains your custom task content types. If you remeber that you have added them, check whether your WF uses that list (maybe your WF uses another one).

Hope it saves somebody some time.

Regards, Michael.

-56

Visual Studio 2012 Update 2 released

Posted on by
Reply

Several hours ago, Microsoft released Visual Studio 2012 Update 2. This update includes several improvements for SharePoint 2013 development.

Some points from the description to this update:

  • Support is now provided for web and load testing for SharePoint applications.
  • Support is now provided for record and playback through Coded UI to perform UI validations on SharePoint 2013 applications.
  • IntelliTrace support is the same as that provided in SharePoint 2010.

It is almost installed on my development environment and I hope, today, I will try these new features 🙂

Regards, Michael.

-6

Solution: Error while publishing workflow or workflow cancels on start. (The requested service could not be activated)

Posted on by
7

Hi,

Today I stumbled into the following error message while was publishing SPD 2013 workflow:

130403_01

Errors were found when compiling the workflow. The workflow files were saved but cannot be run.

Microsoft.Workflow.Client.WorkflowCommunicationException: The request was aborted: The request was canceled. Client ActivityId : 7a290e9c-0917-7088-afc4-e65fd25c5c0b. ---> System.Net.WebException: The request was aborted: The request was canceled. ---> System.ServiceModel.ServiceActivationException: The requested service, 'net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc' could not be activated. See the server's diagnostic trace logs for more information.

Server stack trace:

Another symptom is that workflow cancels on start with the following error message:

Continue reading →

-7

Solution: Errors were found when compiling the workflow. The workflow files were saved but cannot be run. (Cannot set unknown member)

Posted on by
8

Hi,

Several days ago I stumbled into an issue. I could not publish even simple 2013 workflow which contained the only “Start a task process” activity (WF with the only “Log” activity worked well). The check for errors passed well, but I could not publish it. I got the following error message:

130402_02

Continue reading →

-2