Datapolis Process System SDK

Search:

Contents
:
IndexBookmarkPrint
Home > Activities > Troubleshooting

Troubleshooting

 

 

This section helps to address issues related to custom activity development. See the links below to find information of the following subject areas.

 

When You Are Stuck


It may happen occasionally that the information included in the SDK is insufficient for the problems you encounter. In such cases, Datapolis Process System Team strongly recommends browsing the Datapolis Process System Blog, especially Known Bugs and Solutions section, which contains up-to-date information regarding Datapolis Process System development. If this information proves to be insufficient as well, you may contact us directly using the feedback link at the bottom of each SDK page.

 

When the Translation is Missing


The Multilanguage on Activities section demonstrates how to implement a multilanguage support for your custom activities. If you encounter problems when trying to display the literals you've added, please perform the following steps:

  • Ensure that the resource keys are not misspelled,
  • Ensure that the *.resources file is generated and that it's in a proper place,
  • Check if the proper culture code is postfixed to the *.resources file's name.

When Workflow Cannot Be Associated Because of an Activity or Function


If a workflow cannot be associated and an error regarding a specific activity or function is reported, there could be several reasons of such behavior:

  • If error is similar to:

Validation error: <Error><CompilerError Line="XX" Column="XX" Text="The type or namespace name 'SomeNamespace' does not exist in the namespace 'SomeOtherNamespace' (are you missing an assembly reference?)" /></Error>

Probably the Web Application's configuration file (web.config) does not authorize the activity in the System.Workflow.ComponentModel.WorkflowCompiler section. An example of appropriate record is shown in Creating Activity Tutorial.

  • If error is similar to:

Validation error: <Error><CompilerError Line="XX" Column="XX" Text="CreateInstance failed for type 'SomeType'. Exception has been thrown by the target of an invocation.." /></Error>

there could be two reasons:

  • You have incorrectly named activity parameters (e.g. one parameter is differently named in various locations - please check Activity Code section).
  • You have installed Workbox 2.1 or higher, while the activities were made for previous versions. If this is true, it means that there were problems while installing Datapolis Process System and not all required entries were added to configuration files.

The source of the problem is that in Workbox 2.1 we have changed the version of Datapolis.Workbox.Common assembly to 1.1.0.0.

There are two ways to fix this issue:

Verify that in all your application servers in files:

  • web.config files of Web Applications where Datapolis Process System is installed,
  • C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\OWSTIMER.EXE.CONFIG,

in section <runtime><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> the following entry is present:

<dependentAssembly>

<assemblyIdentity name="Datapolis.WorkBox.Common" publicKeyToken="2c03c3097ac016b8" culture="neutral" />

<bindingRedirect oldVersion="0.0.0.0-1.0.0.0" newVersion="1.1.0.0" />

</dependentAssembly>

Rebuild and redeploy your activity. Remember to update references for Datapolis.WorkBox.Common assembly.

 

When Previously Deployed Workflow with Custom Activities or Functions Crashes


There could be following reasons of such behavior:

  • See if SharePoint logs contain an error similar to:

Unexpected RunWorkflow: Microsoft.SharePoint.SPException: <Error><CompilerError Line="XX" Column="XX" Text="CreateInstance failed for type 'SomeType'. Exception has been thrown by the target of an invocation.." /></Error>

If so, this is a problem with Datapolis.Workbox.Common assembly version. Please see the in previous section: When Workflow Cannot Be Associated Because of an Activity or Function.